[wp-trac] [WordPress Trac] #29118: Registering rewrite rules is hard, so let's introduce remove_rewrite_rule.

WordPress Trac noreply at wordpress.org
Tue Sep 9 01:57:07 UTC 2014


#29118: Registering rewrite rules is hard, so let's introduce remove_rewrite_rule.
---------------------------+------------------------------
 Reporter:  ericlewis      |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Rewrite Rules  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------

Comment (by rmccue):

 FWIW, I'd tend to agree, which is why I hadn't patched this up. It's easy
 to write for if you're expecting it to get called every page. I'd also
 like to note that the result of `get_terms` is cached, so that specific
 example is fine on sites with object caching. (If you're writing rules
 like that for performance reasons, it'd be crazy not to have object
 caching installed. That doesn't help for the general case of plugins doing
 it though, obviously.)

 That said, we could consider bringing this functionality in as part of a
 "lazy" reload system. Basically, we'd have the normal stored rewrite
 rules, plus an additional part generated on load and mixed in (but not
 saved). That's new functionality that you'd have to opt-in to and I'd
 prefer not to do that personally, but it is an option.

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


More information about the wp-trac mailing list