[wp-trac] [WordPress Trac] #12935: Evolve the URL routing system

[WordPress Trac]

#12935: Evolve the URL routing system
--------------------------+-------------------------------------------------
 Reporter:  mikeschinkel  |       Owner:  ryan
     Type:  enhancement   |      Status:  new 
 Priority:  normal        |   Milestone:  3.1 
Component:  Permalinks    |     Version:  3.0 
 Severity:  normal        |    Keywords:      
--------------------------+-------------------------------------------------

Comment(by hakre):

 Well I actually made a ''suggestion'' based on what I ''personally
 assume'' what is happening with this ticket. And I won't fight over a
 single word. My suggestion was from a practical point of view with the
 projects history in mind. I might be wrong and infact for this ticket, I
 really hope I am.

 It's this way: If you ask me for my personal opinion about this, we might
 have more in common as you thought:

 - The current Routing system has immense deficiencies[[BR]]
 - The Permalink Implementation is a mess[[BR]]
 - The Frontend-Controller Implementation is a mess[[BR]]
 - WP_Query needs a refactoring for sure[[BR]]

 So please just fix it and all the best by that. And please do not let
 yourself get de-motivated by design issues, missing specs, backwards
 compatibility blockers and all the fun we have over here. Oh for this one
 you'll get an immense needs-unit-tests for sure, so better be prepared.
 Good luck!

 Keep in mind that some URLs get reflected over HTTP redirects so you might
 want to take a look in the {{{redirect_canonical()}}} function as well.

 I know this can be pretty hard w/o any specs, so I personally welcome any
 input, especially if it's specs and docs. I would love to see this already
 in 3.1!

 On thing I would love to see in a new implementation is to have better
 query var support like

 {{{http://example.com/permalink-of-a-post/print}}}

 instead of

 {{{http://example.com/permalink-of-a-post/print=1}}}

 I think you know what I mean.

 Here is a custom post type example (that feature if often propagated as
 CMS, but well w/o propper URLs I'm totally with you):

 http://lists.automattic.com/pipermail/wp-testers/2010-May/012980.html

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12935#comment:19>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software