Page slug priority over post archive slug
I’m using custom post types in WordPress and I’m also looking for ways to improve the way they work.
I have created an
archive-retailer.phpfor my retailer custom post type, and I’ve also added a
* Template Name: Retailersto the file so I can use it as a page template. (the file has conditional code for both the archive and the page)
The slug for my retailer custom post type is ‘retailers’, so the archive of this custom post is /retailers. When I’m using the
archive-retailer.phppage template on a page with the slug ‘retailers’, whant visiting the /retailers link the code for the archive template is used instead of the code for the page.
Is there a way to overwrite this behaviour? Should I start a discussion and see if this behaviour (allow page slugs to overwrite the archive slugs) could be added to the core?
- The topic ‘Page slug priority over post archive slug’ is closed to new replies.