[wp-hackers] W3 Total Cache and excluding specific page content from caching
nl at thoughtrefinery.com
Mon Sep 9 18:07:18 UTC 2013
Have you tried posting in the W3TC Plugin Support Forum? This is more a plugin issue than a WP issue...
Tried a bundled theme and all unnecessary plugins turned off to check for theme/plugin conflicts?
The thread you mentioned makes it clear that mfunc (especially after the recent security issues) is tough to get going in some environments.
Could also be the widget -- mfunc calls lose a lot of context so the widget code could be working but not pulling actual widget data due to missing info.
Writing an ajax call to replace the cached sidebar content with uncached content from the server would avoid mfunc completely and run the code within WP (keeping context).
Ajax calls the server saying: "give me the (primary/secondary) sidebar for page X" ... which it returns some HTML and jQuery replaces the cached sidebar with the user specific data.
Not a simple solution, but user specific content plus page caching are never simple...
>> On Mon, Sep 9, 2013 at 3:43 AM, William Satterwhite
>> <whsatterwhite at gmail.com> wrote:
>>> I've been doing a lot of research, reading, and made many attempts at
>>> excluding specific content areas from W3 Total Cache's page caching.
>> What I
>>> keep trying is excluding a sidebar and its widgets entirely from page
>>> cache, but leaving the rest of the page cached. Multiple attempts at
>>> so have failed. I've followed many of the <!-- mfunc --> examples,
>>> late init within page caching, and nothing seems to work. There are many
>>> widgets that are used, which display dynamic information produced by PHP,
>>> so having the ability to exclude them from caching would be great.
>>> Any help or feedback would be greatly appreciated.
>>> The following are links that I've found while trying to figure this out
>>> my own:
>>> To complicate things, I'm using the Genesis Framework with a child theme
>>> and trying to get this working with Cart66's "Cart" widget.
>>> Thank you,
>>> Hunter Satterwhite
More information about the wp-hackers