Post type settings

A managed post type's settings are split across tabs: General, Permalinks, Editor, Visibility, REST API, Labels, Fieldsets and Source. Most switches have three states: Auto (WordPress's or the original plugin's default), Enabled or Disabled. Change only what you need, and leave the rest on Auto.

General

Singular and plural names, an SVG Icon for the admin menu, and three behaviors:

• Hierarchical: entries can have parents, like Pages. Turn it on for things like a "Series → Book" structure.
• Allow export: include this post type in Tools → Export in wp-admin.
• Delete with user: delete a user's entries of this type when you delete the user.

Permalinks

By default, entries live under the post type key: /book/the-glass-library/. Turn on Custom permalink base and set Permalink base to change that segment, for example to books or a nested catalog/books.

• The base is turned into a URL slug: lowercase, spaces and punctuation become hyphens, and accented Latin letters are simplified (Café becomes cafe). Other alphabets are kept as typed.
• Leave the base empty to use the key.
• Enable archive page gives the post type a listing page. Archive page slug uses the permalink base by default, or a segment of its own.
• Prepend front base, Feed URLs and Pagination URLs control the extra URLs WordPress generates.

VX rebuilds WordPress's URL rules when you save, so new URLs work straight away. If one still returns a 404, usually because another plugin caches rules, open Settings → Permalinks in wp-admin and save it once.

Warning

Changing the permalink base moves every entry of that post type. WordPress doesn't redirect the old URLs, so existing links and bookmarks break unless you add redirects yourself.

VX doesn't check bases for collisions. If two post types, or a post type and a page, use the same base, one of them will stop working.

Editor

Choose the Block editor or the classic editor, and which built-in features the edit screen has: Title, Content editor, Featured image, Post excerpt, Post author, Comments, Trackbacks, Revisions, Page attributes and Post formats.

Default Sidebar width (Default, Medium, Wide) sets how wide the VX fields panel opens in the block editor. Editors can still resize it.

See Keep the built-in features before turning the title, content or featured image off.

Visibility

Where the post type shows up: Publicly queryable (whether entries have front-end pages at all), Exclude from WP search, Available in nav menus, Show in admin bar, Show in admin menu, and Menu position, including placing it as a submenu of another menu item.

REST API

Show in REST API is WordPress's own switch for the /wp/v2/… endpoints. The block editor needs it on; turn it off and the post type falls back to the classic editor.

REST base is the segment those endpoints appear under. Leave it empty and WordPress uses the post type key.

This switch isn't the VX REST module, which decides which field values appear on those endpoints. A post type must have Show in REST API on before the VX REST module can expose its fields.

Labels and Fieldsets

Labels overrides the wording WordPress uses in the admin ("Add New Book", "No books found"). VX fills these in from your singular and plural names, so most sites never touch them.

Fieldsets is a read-only list of the fieldsets whose Locations target this post type. To change it, edit the fieldset's Locations.

Technical details for LLMs

• Tri-state values: auto | enabled | disabled. auto defers to the registrant's value (or WordPress's default for VX-created types).
• Permalink base normalization: lowercase, punctuation/whitespace → -, trim /, fold accented Latin (remove_accents); non-Latin scripts preserved. Empty base = key.
• Prepend front base, Feed URLs and Pagination URLs have no effect when the registrant disabled rewrites (rewrite: false), unless a permalink base is set, which re-enables rewrites.
• Rewrite rules are dropped (rebuilt on the next request) after a dashboard save or vx-framework/update-post-type that changes permalink settings, after create/delete, and after config-as-code imports, restores and resets. For changes that bypass those (a JSON file edited on disk, a PHP registration changed, a 404 after import), call vx-framework/flush-permalinks; its undo is none.
• Under plain permalinks (no permalink structure in Settings → Permalinks), custom bases never appear in URLs.
• Show in REST API off: no block editor for the type and no /wp/v2 route.