WordPress / WordPress/secure-custom-fields
π³ Feature Request: Nested Custom Post Types with Automatic Hierarchy and URL Management
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
WordPress currently allows hierarchical Pages and hierarchical posts within a single Custom Post Type, but it does not support nested Custom Post Types.
For large websites such as IT companies, agencies, product catalogs, documentation websites, universities, and enterprise websites, developers often need to create multiple related Custom Post Types and manually connect them using taxonomies, relationship fields, or custom code.
This makes the website structure more complex to manage and requires additional configuration in page builders such as Elementor and other.
Example
An IT company website may have the following service hierarchy:
Services
βββ Website Development
βββ WordPress Development
β βββ Custom Theme Development
β βββ Custom Plugin Development
β βββ WooCommerce Development
β βββ Website Maintenance
β
βββ Shopify Development
βββ Webflow Development
βββ Laravel Development
βββ React Development
Desired URL Structure
/services/
/services/website-development/
/services/website-development/wordpress-development/
/services/website-development/wordpress-development/custom-theme-development/
/services/website-development/wordpress-development/custom-plugin-development/
/services/website-development/wordpress-development/woocommerce-development/
Automatic Features
- Automatic parent/child relationships
- Automatic permalink generation
- Automatic breadcrumbs
- Automatic hierarchy detection
- Easier querying of parent and child content
- Better Elementor template support
- Better organization inside the WordPress admin
- Hierarchy-aware template conditions
- REST API support
- Easier filtering
- Dynamic navigation
Benefits
- Less custom code
- Easier content management
- Better scalability for large websites
- Cleaner URL structures
- Easier template management
- Better developer experience
- Better content organization
Use Cases
- IT company websites
- Digital agencies
- Product catalogs
- Documentation websites
- Knowledge bases
- University websites
- Enterprise websites
- Service-based businesses
This would provide a much more intuitive way to build and manage complex website structures while reducing custom development work and improving compatibility with page builders.
This feature would simplify building complex content structures while keeping the WordPress admin easy to use.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, entry points, or tests are named. Start by narrowing the requested hierarchy, permalink, admin, template, filtering, and REST API behavior into an agreed scope. Done should be defined by explicit acceptance criteria covering the selected behavior rather than the full feature list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100