Support » Plugin: W3 Total Cache » W3 Total Cache Fragment Caching

Viewing 3 replies - 1 through 3 (of 3 total)
  • I’m having this problem too. I think the latest version of W3TC borked it. Am I right, Frederick Townes?

    In the past, I always had to modify my theme to run dynamic code. Don't I need to do that again for this plugin?
    For now no; there are some special cases that we will address with an upcoming release for highly dynamic sites.

    My JetPack Twitter sidebar no longer works correctly, since the Twitter feed generation is called via PHP and not JS.

    Yes, seems the latest version of W3TC broke fragment caching.

    There is a solution here:

    I just tried it and it works great.

    You don’t actually have to put the security constant in the wp-config.php file though.

    If you want to do fragment caching from a plugin/theme that you distribute, it will be tough to do so, giving all users instructions to add this to their wp-config.php

    You can literally check if it has been defined and if not, define it as your theme’s functions.php or your plugin’s core file is included by WordPress.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3 Total Cache Fragment Caching’ is closed to new replies.