[wp-hackers] Saving the entire HTML sent to client

Haluk Karamete halukkaramete at gmail.com
Thu Dec 8 02:18:07 UTC 2011

We got one of those installed. I think the totla cache. And when it
was engaged, it was not showing the latest changes I made in the back
end. Of couese, I had logged in as admin maybe that's the reason?

To get those changes, ( for example to see the output of the latest
loop I created ), I had to add to the url stuff like q=32113213 to
avoid caching.

With the implementation I suggested however, I was seeking my own
programmatic solution where I can feel in control and manage the
caching business in however I want, in whatever chunks I want. But to
be able to do that, I need to get a hold of the "HTML so far"!

Maybe there is just no way to get a handle of what HTML that the PHP
functions have generated so far?

Would it be nice to have the option of doing something like this

$content = get_header()

Is this technically not possible?

On Wed, Dec 7, 2011 at 5:56 PM, Dion Hulse (dd32) <wordpress at dd32.id.au> wrote:
> On 8 December 2011 12:52, IC IC <icwordpress at gmail.com> wrote:
>> To minimize the DB queries down to nothing on the home page of your
>> magazine styled web site, what do you say about the following idea?
>> Every time, you create a post or page (or cat or tag for that matter
>> ), at the time committing that change into the database, have a plug
>> in run the home page  internally ( as if a visitor visited your home
>> page ) and grab the html generated and create a text file out of that
>> HTML ( from all the way up DOCTYPE down </html).  This way, your home
>> page ( be it home.php or front-page.php or whatever), may check if the
>> current user logged in and if not, just do a PHP include of that
>> recently generated file?
>> Does PHP provide a way to get a hold of that entire HTML? Would that
>> be a wp_footer hook?
> That sounds like you want a Static cached page which only updates when
> you add posts?
> If so.. Pretty much every Caching plugin out there does this, Have a
> look into Wp Super cache and Wp Total Cache for a start.
> You can take it further and using those plugins, combined with a
> .htaccess rule, have the web server serve the static cache file
> directly - avoiding the PHP overhead all together
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list