[wp-trac] [WordPress Trac] #14310: Make template hierarchy filterable

[WordPress Trac]

#14310: Make template hierarchy filterable
------------------------------+-----------------------------
 Reporter:  scribu            |       Owner:  johnbillion
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  Future Release
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------

Comment (by DrewAPicture):

 Replying to [comment:64 influencebydesign]:
 > So why does this ticket seem to have such a problem getting through the
 process? The last time the Milestone was changed to Future Release was 5
 years ago. I'm not familiar with the ins and outs of WordPress's core, but
 it seems like the idea behind apply_filters is that by default without
 hooked functions it wouldn't change anything.

 The problem is that while on the surface this seems like a simple change,
 it could have far-reaching unintended consequences. Making the template
 hierarchy broadly filterable would effectively make it possible to
 completely override expected behavior for how templates work in WordPress.
 That's a really big deal.

 When used ''as intended'' it's not a bad idea. But time and again, core
 has introduced hooks that have been ''misused'' and abused, and if enough
 people are doing the abusing, that sometimes becomes something core has to
 support.

 Part of what makes WordPress so approachable by developers of all levels
 is that there are certain constants in how it can be expected to work.
 Therefore, I don't think it's unreasonable to approach a feature request
 like this with a high level of caution as has been demonstrated here.

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