[wp-trac] [WordPress Trac] #24944: Include a new `locate_template_override` filter to let plugins duck-punch how templates are included.

[WordPress Trac]

#24944: Include a new `locate_template_override` filter to let plugins duck-punch
how templates are included.
-----------------------------+------------------------------
 Reporter:  georgestephanis  |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Template         |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |
-----------------------------+------------------------------

Comment (by georgestephanis):

 #13239 - unrelated.  Deals with a much more limited use case that wouldn't
 solve for this regardless.

 #24814 - unrelated.  Deals with a much more complicated fix for a much
 more unnecessary use case.  In comment 10, nacin wrote:

 > [http://core.trac.wordpress.org/ticket/24814#comment:10]
 > You do have one option: To avoid the hierarchy entirely and write your
 own handling that includes subdirectories. (That's basically what you'd be
 doing anyway.)

 Which this is attempting to address.

 #12877 - Again, unrelated.  This is not intended to swap out which
 template file is used (although it could certainly be used as that) -- but
 rather to enable a modification of how the template is itself pulled in.
 It can enable a lot of fun and useful customizations, and the citations
 you're sending back really aren't addressing the issue at hand.

 #21062 is the closest, but it's still a different use case.  I believe
 that this could give a tool for folks that need the above as a side
 benefit, but it keeps things simple -- the same way we did with #15989
 with r20694

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