View Settings
The settings button in the View editor’s toolbar switches the inspector to View settings. These settings belong to the whole View rather than to one layout.
General
- Name names the View in the Views list, on admin pages and in the editor’s tab.
- Data source chooses where the rows come from: a post type, a database table, a remote URL, a file on the server, a file from the media library, or a preset. The fields below it change with the choice; see Data Sources.
- Post type, for a post type source, chooses the post type the View reads and whose list it replaces. On that list the View shows as its card alone, its layouts as tabs, on WordPress’s own page.
Changing the data source, the post type or the file clears what depended on the old columns in every layout: hidden and visible table columns, the initial sort, custom filters, the Kanban and Feedback taxonomies and Kanban column settings, the chart cards’ columns, and the layouts’ Data filters.
Enable View
Enable View, on by default, lets this View replace the post list of its post type. Turned off, WordPress’s standard list, or the next most recent View of that post type, takes its place. Admin pages and shortcodes still show a disabled View, and the Views list marks it Disabled.
Public embed
Public embed, offered for post type sources only, lets visitors who are not logged in read this View where a shortcode embeds it. A public embed is read-only and shows only the View’s published posts that have no password. Filters and sorting on custom fields are left out for those visitors, and the layout’s own Data filters still apply. A layout the View’s or its own conditions hide from a visitor stays unavailable to them. Rows carry no edit links, and an item’s upvotes show the count and the visitor’s own vote only. Everyone who can edit posts sees the embed as before. A public embed loads only when a visitor scrolls within 400 pixels of it, so a View far down a page costs nothing until then. Every embed holds its height while it loads, so the content below it does not move.
Field mapping and column labels
Sources other than a post type have a Field mapping section, which says which source columns act as the row’s ID, title, content and date. Every source with columns has Column labels, which renames columns for display. A preset may fix either and hide its section. Data Sources explains both.
Shortcode
Shortcode shows the View’s embed code with a Copy button:
Place it in a post, a page or any other place that renders shortcodes. The View renders inside an isolated frame, so the theme’s styles do not reach it, and its layouts appear as tabs; Default post screen layouts are left out.
An individual embed can choose a fixed theme and omit the surrounding workspace canvas while keeping its field card, tabs and controls:
theme accepts light, dark or system; when omitted, the host’s normal
theme applies. presentation accepts workspace (the default padded canvas)
or card. These options affect this embed only, leaving the saved View and
administration screens unchanged.
The page markup is the same for every visitor, so full-page caching keeps working. The View itself loads when the page opens, for users who can edit posts (Contributor and above), and for everyone when Public embed is on. Other visitors see nothing.
Conditions
Conditions limits who sees the View. On the post list, a View whose conditions do not match leaves WordPress’s standard list in place; on admin pages and in embeds the View is left out. See Conditions.
Delete
Delete View, in the editor’s toolbar, removes the View and every layout in it after you confirm. Deleting is permanent; remove the View from any admin page that shows it.
Where a View shows
| Place | Who sees it | What applies |
|---|---|---|
| The post type’s list screen in wp-admin | Users who can edit posts and open that screen | The View unless it is disabled; its conditions, its layouts’ conditions |
| An admin page | Administrators | The View’s and its layouts’ conditions; no Default post screen tab |
| A shortcode embed | Users who can edit posts, or everyone for a public embed | The View’s and its layouts’ conditions, decided for the visitor on that page; no Default post screen tab |
Data for any of them is read through SleekView’s REST API with the same checks, so a condition never shows a View to someone who could not read it otherwise.