When implementing a Page Fragment Caching Exception, you are telling W3 Total Cache to bypass cache for a particular section of content. A great use case for this is dynamic content that you wish to update real time, separate of the page caching itself. The following article will walk you through the process.<\/p>\n

Using W3 Total Cache 2.10.0 or later?<\/strong> The mfunc<\/code>\/mclude<\/code> syntax changed in 2.10.0 — tags now reference a registered callback instead of containing code, and tags written for older versions no longer run. Follow How to Implement a Page Fragment Caching Exception in W3 Total Cache 2.10.0+<\/strong><\/a> instead. The steps on this page apply to versions before 2.10.0<\/strong>.<\/p>\n<\/div>\n

\n\n\n <\/div>\n\nSpeed Up Your WordPress Website.<\/strong><\/p>\n A Difference of Just 100ms in Page Load Speeds Can Cause a Visitor to Prefer Your Competitor’s Website.<\/p>\n<\/div>\n\nView Plans<\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n \nSelect your fragment caching method in Performance → General Settings\n\nWe recommend you choose a memory-based caching backend such as Redis or memcached<\/a><\/li>\n<\/ul>\n<\/li>\n Enable “late initialization” on the Page Cache settings page<\/li>\n Add define(‘W3TC_DYNAMIC_SECURITY’, ‘mycode’); to your wp-config.php file<\/li>\n<\/ul>\nAnd finally, use this format to implement the caching exception in your template for the dynamic content:<\/p>\n⚠️ The syntax below applies to versions before 2.10.0. On 2.10.0+, see How to Implement a Page Fragment Caching Exception (2.10.0+)<\/a>.<\/p>\n