[wp-trac] [WordPress Trac] #64465: Add locate_template_paths filter to allow extending template resolution paths

[WordPress Trac]

#64465: Add locate_template_paths filter to allow extending template resolution
paths
--------------------------------------+-----------------------
 Reporter:  lucascarvalhopl           |       Owner:  (none)
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:
Component:  Themes                    |     Version:  trunk
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  template
--------------------------------------+-----------------------
Changes (by lucascarvalhopl):

 * status:  closed => reopened
 * resolution:  duplicate =>


Comment:

 Hi folks,

 I understand why this ticket was marked as a duplicate of #13239, since it
 addresses the same underlying issue. However, I’d like to clarify an
 important distinction.

 Ticket #13239 was opened over 16 years ago (WordPress 3.x era) and,
 despite multiple reports and confirmations from users over the years, it
 never progressed to an actual implementation. Its last activity was more
 than two years ago, which effectively leaves the issue unresolved and
 stalled.

 This ticket is not a re-report of the problem, but rather a concrete and
 working solution for it.

 The accompanying PR:

 * Implements a functional fix for the issue described in #13239
 * Includes automated tests
 * Follows current WordPress coding standards and best practices
 * **Is compatible with current WordPress version**

 In other words, this is the missing piece that #13239 never reached: a
 real, reviewed, and test-covered implementation that can finally close a
 long-standing issue affecting many users.

 Closing this as a duplicate without evaluating the proposed solution
 effectively keeps the original problem unresolved, despite the fact that
 it is now demonstrably solvable.

 I’d kindly ask that the PR be reviewed on its technical merits, either by
 reopening this ticket or by explicitly linking and evaluating the
 implementation within #13239, so we can finally move this forward and
 resolve the issue for good.

 Thanks for your time and for maintaining WordPress core.

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