Folders for the post types you register in code
You registered a post type for the client: case studies, branches, products of a catalog. The client added the hundredth item and asked how to sort them.
Plathix PRO adds private folders to the standard list of your type. No taxonomy to register, no admin screen to build. Your code, URLs and queries stay as they are.
You registered the type. The client filled it.
A type with show_ui gets the standard WordPress list and nothing more: titles, dates, status tabs, search.
When the list passes a hundred items, the client asks for groups. A private taxonomy means more code, a meta box, a filter dropdown and one more thing to maintain on every site you hand over.
Plathix PRO adds the folders to the list you already have.
Private labels for your own posts
Developers who register their own types ask the same things. The type works on the site. The list in wp-admin has no private place for the team’s groups.
You want to tag posts with private, admin-only terms. The terms should have no URL of their own and should not be searchable on the front end.
The standard list is not much help. Even simple jobs, like grouping posts by your own rules, make people ask whether everyone writes a plugin for it.
The usual workaround is a custom taxonomy that only the backend uses, plus a dropdown filter on the list.
A type collects years of content. Posts from 2018 to 2020 are still in the list and now have to be cleaned out.
Folders give the standard list of your type a private tree, with no taxonomy to register and no filter to build. None of it shows on the site.
Folders your clients will actually use
By industry
Healthcare, retail, finance: sales opens one folder and finds the right case study.
Waiting for approval
Items the client has not signed off yet stay drafts, together in one folder.
After a migration
Imported a few hundred items from the old site? Keep each batch in a folder until someone checks it.
Old work
Older items stay published and move out of the daily list.
Before you delete
Old posts you plan to remove wait in one folder. Check them there first, and keep the ones that still bring visitors.
What your type needs, and what it gets
Three conditions
show_ui is true, the type keeps the standard edit.php list, and its name has 17 characters or fewer. Then it appears in Settings → General → Enabled Sections.
Its own tree
Each enabled type gets a separate folder tree with its own Folder column. Folder names never mix with Pages, Media or another type.
Your capabilities
Plathix reads rights from your type. Users who can publish its items manage the folders; users who can edit them put items in folders.
REST for scripts
The plathix-pro/v1 namespace has the same folder routes as Plathix Free, with a post_type parameter. Build a tree or file items from a deploy script.
Your code never sees the folders
| What you do | What changes | What stays as it is |
|---|---|---|
| Put an item in a folder | Its Plathix folder | Its URL, slug, parent, terms and status |
| Run your queries on the site | Nothing | They return the same posts as before |
| Rename or move a folder | The folder tree in wp-admin | Permalinks, rewrite rules and menus |
| Trash an item, then restore it | Its Trash state | Its folder: it comes back to the same place |
| Turn Plathix PRO off | The list looks like plain WordPress | Your folders wait in the database and come back |
Folders are a private taxonomy: no URLs, no rewrite rules, not in the WordPress REST API.
How we test custom post types
We run each check on a live site with Plathix PRO and a post type registered in a small test plugin.
Status Planned
Results go to Plathix Lab. Each row turns into a link once it has run.
| Check | What we verify | Status |
|---|---|---|
| Enable a code type | A type with show_ui true appears in Enabled Sections; the panel appears on its list. | Planned |
| Under another menu | A type shown under another plugin’s menu gets the panel on its list. | Planned |
| Custom capabilities | A user with only this type’s capabilities manages folders and files items. | Planned |
| REST with post_type | Create a folder and put items in it through plathix-pro/v1. | Planned |
| Own columns | A type that sets its own columns: where the Folder column appears. | Planned |
| Trash and restore | A trashed item comes back to its folder. | Planned |
Custom post type folders FAQ
Which of my types can get folders?
Why 17 characters?
Can a script create folders and file items?
Who can manage the folders?
Will folders change my queries or URLs?
Is this in Plathix Free?
Related pages
Register the type in code. Hand the client a list with folders.
Your post types with the standard list, in folders your client chooses. Your code, URLs and queries stay as they are.