Comments on: WordPress Hook for Entire Page Using Output Buffering

By: August Karlstrom

August Karlstrom — Thu, 04 Mar 2010 17:55:28 +0000

Elegant!

By: Admin

Admin — Tue, 23 Feb 2010 21:19:58 +0000

[asterix]: There are not any performance issues that I am aware of. Basically, all this does is prevent any page output until you tell it to display it, so that you can modify the final output before it is sent to the browser.

I suppose that if you were doing quite a lot of processing to the output before flushing the buffer, it could cause a delay in the loading of the page, but that is more of a script performance issue than the use of this method.

Glad you found it useful!

By: [asterix]

[asterix] — Tue, 22 Dec 2009 20:16:38 +0000

Wow, that’s great! Thank you. Didn’t know anything about these output buffers before, but they are cool.

Are there any performance issuses, maybe?

By: Admin

Admin — Wed, 08 Jul 2009 02:37:13 +0000

This code has been verified to work with WordPress 2.8

By: Admin

Admin — Mon, 23 Feb 2009 04:13:49 +0000

This code modification has been tested in the latest release of WordPress (2.7.1)

By: geldverdienen

geldverdienen — Fri, 10 Oct 2008 19:45:53 +0000

buffer_start is executed at the end of the header section of the html. The parameter, the callback function, is called at the end of the output buffering. This occurs at the footer of the page, when the second registered action, buffer_end, executes.

The callback function is where you add your code to change the value of the output (the $buffer variable). Then you simply return the modified code and the page will be displayed.