Timeline for Remove slug from custom post type post URLs
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
|
|
| Oct 2, 2015 at 23:22 | comment | added | Ben Racicot | I see. There should be rewrite rules that append '-1' to future conflicting URL's like native WP posts vs pages. I've created a trac ticket core.trac.wordpress.org/ticket/34136#ticket would love your thoughts. | |
| Oct 2, 2015 at 15:49 | comment | added | Jan Beck | I have updated my answer to show that this does actually break all pages. Without a slug, WP will look for a CPT instead of a page and if it doesn't find it, return an error. So it's actually not related to the post-name. | |
| Oct 2, 2015 at 15:47 | history | edited | Jan Beck | CC BY-SA 3.0 |
added 48 characters in body
|
| Oct 2, 2015 at 14:35 | comment | added | Ben Racicot | So if the goal is to remove the slug for CPT's couldn't we name the CPT something unique that wouldn't collide since it will never be seen in the URL anyways? Or is the post-name the possible conflict if named the same as a page? | |
| Oct 2, 2015 at 12:21 | history | edited | Jan Beck | CC BY-SA 3.0 |
added 374 characters in body
|
| Oct 2, 2015 at 12:13 | history | answered | Jan Beck | CC BY-SA 3.0 |