Read which browse layouts this install offers

GET

/admin/system/browse-views

• Local development behind nginx (port 8088 by default)

The browse layouts (grid, masonry, thumbnail, list, feed) enabled for every user on this install, in the switcher’s canonical order.

An install that has never configured this reads back all five — the shipped default is the ABSENCE of a stored value, not a seeded row, so an install upgraded into this feature keeps exactly the behaviour it already had.

This is the admin read. The public counterpart every client actually renders from is GET /browse-views.

Authorizations

• cookieAuth
• bearerAuth

Responses

200

The enabled layouts

object

enabled

required

The browse layouts this install offers, in the switcher’s canonical order. The server reorders whatever it is sent into that order and drops duplicates, so layout order stays a frontend decision and only availability is the operator’s.

MUST NOT BE EMPTY. A write enabling nothing is refused with a 400 and nothing is persisted — an install offering no layout has an unreachable browse page, and the recovery path would be a database shell.

An install that has never configured this reads back all five. That is the shipped default expressed as the absence of a stored value, not as a seeded row.

Array<string>

>= 1 items

Allowed values: grid masonry thumbnail list feed

Example

[
  "grid",
  "list",
  "feed"
]

401

Authentication required, missing, or invalid

object

error

required

Human-readable error summary

string

Example

the request could not be completed

Example

{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Authenticated but missing required capabilities

object

error

required

Human-readable error summary

string

Example

the request could not be completed