Changes between Initial Version and Version 1 of Ticket #54541, comment 9
- Timestamp:
- 09/20/2022 05:47:30 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54541, comment 9
initial v1 5 5 Is it possible that `load_template()` is where these exact hooks belong (with the `$template_names` param removed)? Obviously, that is the function responsible for requiring the located file with the intended variables available to it, and the measurable code execution for Query Monitor is the extraction of the `query_vars` and the rendering/inclusion of the template file. 6 6 7 In addition, `load_template()` is used by many of the most popular WordPress plugins – not `locate_template()` – which means their template parts will never see these hooks fire and unable to benefit from any imaginary fragment caching implementation that may-or-may-not come in the future because of these hooks.7 In my research & experience, `load_template()` is used by many of the most popular WordPress plugins – not `locate_template()` – which means their template parts will never see these hooks fire and be unable to benefit from any future fragment caching implementation that may want to use them. 8 8 9 9 === Scopecreep … … 13 13 == Plugins 14 14 15 Mostly, the se plugins use `load_template()` to get around the fact that `locate_template()` is strictly locked down to the parent/child theme hierarchy, and they write their own "locators" with extra locations to add to the core hierarchy under certain controlled conditions.15 Mostly, the plugins below use `load_template()` to get around the fact that `locate_template()` is strictly locked down to the parent/child theme hierarchy, so they write their own "locators" with extra paths to add to the core hierarchy under certain controlled conditions. 16 16 17 17 * bbPress & BuddyPress for theme compatibility … … 28 28 29 29 Asking respectfully for your friendly additional thoughts & feedbacks 💫🤝 30 31 (Edit: reworded some stuff for improved tone 💟)