[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:  Future Release
Component:  Permalinks    |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------

Comment (by scribu):

 After working with WP_Rewrite even more, I think this ticket's focus is on
 the wrong thing.

 Ordered URL regex patterns are used in many other CMSs/frameworks and are
 a pretty concise and powerfull way of defining rewrite rules, with
 limitations of course.

 But the perceived lack of flexibility of WP_Rewrite isn't due to regexes,
 but due to the way these patterns are generated and stored.

 It's akward to re-order rules, for example. Also, they're not grouped in
 any way after they're generated: you can't easily filter out only the
 taxonomy rewrite rules, or just the rules for a particular post type etc.

 So, although there certainly are use cases for parsing individual path
 segments - this can already be done
 ([http://wordpress.stackexchange.com/questions/9419/remove-taxonomy-slug-
 from-a-custom-hierarchical-taxonomy-permalink/9685#9685 one example]) - it
 shouldn't be the main way of defining rewrite paths.

 We should focus instead on making it easier to manipulate the existing
 regex rules.

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