[wp-trac] [WordPress Trac] #34136: Allow register_post_type's rewrite to remove CPT slug

WordPress Trac noreply at wordpress.org
Mon Mar 10 10:41:12 UTC 2025


#34136: Allow register_post_type's rewrite to remove CPT slug
---------------------------+------------------------------
 Reporter:  BenRacicot     |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Rewrite Rules  |     Version:  4.3.1
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by Tomas Eklund):

 Replying to [comment:4 michael.ecklund]:
 > I guess I don't understand why you wouldn't just use the built-in
 hierarchical Post Type (`page`) for that.

 I guess I don't understand why you still don't understand... People have
 been giving several good explanations already. But nothing seems to
 happen. Not even an acknowledgment that "We understand now how this would
 be beneficial, and we'll see if and how it can be implemented..."

 This request would be very useful and move WordPress one step closer to
 actually becoming a CMS instead of a blogging platform on steroids, which
 it still is. This legacy really limits what you can do with WordPress on a
 professional level.

 Sometimes you need the built-in Page post type AND a custom post type
 (CPT). And the CPT is often the most central and significant content,
 which really need the shorter URLs (without CPT slug prefix) for the site
 to appear professional.

 Currently I'm doing something similar to what you suggested and reuse the
 Posts post type, for something that is really Custom Post Type content,
 but this means I need to use custom PHP code and plugins to rename the
 post type to something meaningful in the admin panel, as to not confuse
 the client who is editing the content. It feels like I'm hacking WordPress
 rather than it working with me.

 I guess I interpret your question like this:

 I guess I don't understand why you are still using WordPress?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/34136#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list