Experiment: template enhancement output buffer#2899
Draft
Conversation
- Experiment with the template enhancement output buffer
cff1a53 to
077b1ba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR experiments with the new template enhancement output buffer introduced with WordPress 6.9.
This output buffer is based on the hook
wp_template_enhancement_output_buffer, which can be used to intercept the full HTML output of a template before being delivered to the browser. Among many other possibilities, this hook could help us to move some front functionalities to the server-side, improving their performance.In this particular experiment, I use the
wp_template_enhancement_output_bufferto replace thepdf_icon.jsfile, in its function of adding an icon to all the links to PDF documents.Testing