Change an established content model safely
Post type slugs, taxonomy slugs, field names, public bases, and relationships become durable contracts once editors add content and visitors use the resulting URLs. Review their consumers before changing them on an established site.
This guide is for site owners planning a controlled change. Complete it on a staging copy first and keep a current recoverable backup.
Classify the proposed change
| Change | Main effect |
|---|---|
| Rename a singular or plural label | Editor and public wording changes |
| Change a post type or taxonomy slug | A different registered structure is created |
| Change a custom field name | Templates and existing values may no longer refer to the same field |
| Enable or disable singles or archives | Public routes appear or disappear |
| Change a permalink base | Canonical public URLs change |
| Change connected post types | Editors gain or lose the taxonomy |
| Change a permission rule | A different visitor audience sees the content |
| Change a query preset | Every component using the preset can change |
Label-only changes are usually the narrowest. Machine identifiers and URLs require migration and redirect planning, not an in-place wording edit.
Inventory dependencies
Before changing a setting, record:
- The affected post types, taxonomies, fields, and representative entries
- Single, archive, term, feed, paginated, and multilingual URLs
- Templates that display the content or field
- Query presets, Faceted Search configurations, maps, feeds, and related-content sections
- API consumers and Quick Edit workflows
- Permission rules and fallback templates
- Navigation menus, external links, search indexes, and cached pages
Take a copy of the current setting values and the expected result for each dependency.
Make the change in a controlled sequence
- Reproduce the current model and representative content on staging.
- Change one identifier, relationship, or behavior at a time under Settings → POM Theme → Content model.
- Update every dependent template, query, field consumer, or permission assignment.
- For URL changes, save Settings → Permalinks and add any redirects not provided by the selected POM permalink feature.
- Migrate or re-enter existing values when a field identity changes.
- Clear relevant caches after the underlying content and routes are correct.
- Compare the full dependency inventory with the new behavior.
- Schedule the production change when editors and integrations can be paused if necessary.
POM Theme’s page-backed taxonomy bases and taxonomy-based post permalinks keep their previous supported route as a permanent redirect to the current canonical URL. Do not assume the same redirect exists for an ordinary post type or taxonomy base change.
Validate before launch
Check at minimum:
- Existing entries remain available in the correct administration menu.
- Editors can create and update every field and taxonomy assignment.
- Singles, archives, term pages, pagination, and feeds resolve.
- Templates handle populated and empty values.
- Query presets return the intended count and order.
- Logged-out, allowed, and denied visitors receive the expected result.
- Canonical links, breadcrumbs, language alternates, and redirects use the new URLs.
- API consumers still receive only the intended public fields.
If the result differs from staging, restore the previous setting values before attempting another change. A rollback is safest while the original identifiers, routes, and dependencies are still documented.
For URL-specific behavior, see Taxonomy archive page bases and Taxonomy-based post permalinks.