Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. vs Menu Cache

Normally, if a web page is served by the cache, its content will be always the same until the cache is deleted. By adding the content with the shortcode provided by Content No Cache, you will be able to show dynamic content even on pages served by cache. You don’t need this plugin to exclude the entire page from the cache. This plugin is to exclude a part of the page from the cache. It’s useful if you need to cache a page, but part of that page should not be cached. Imagine you have a page that has this content: Hello this is some text. Another line of text Another line of text Current day: Monday if that page is served by cache, the user will always see: Hello this is some text. Another line of text Another line of text Current day: Monday If you need that the last line of text is always updated, this plugin will help you. The entire page will be served by the cache, but the plugin will get the updated content that you need. How to show dynamic content with full page cache Install Content No Cache Create a new element “Content No Cache” Add to that element all the content that you want to exclude from the cache Copy the shortcode that you will see in the section “Shortcode”. It will look like [content_no_cache id=”3328″]. The parameter “id” is the ID of the content element (in this example 3328). Add the shortcode to the page where you want to display that content. Compatible caching plugins tested with Content No Cache W3 Total Cache WP Fastest Cache WP Optimize Comet Cache Cache Enabler Hyper Cache WP Super Cache LiteSpeed Cache Speed Optmizer WPRocket All of those caching plugins are compatible with Content No Cache. If your favorite caching plugin is not compatible for any reason, let us know it Compatible CDNs Cloudflare BunnyCDN StackPath KeyCDN Fastly CloudFront Main features Ultralightweight plugin. The few lines of code will run only where you add the shortcode. No jQuery, no JS libraries, only a couple of lines of pure JavaScript No database queries, no extra HTTP requests for external assets, no bloat With a few line of ultralight code you can fully cache the page even if you need dynamic content on that page It provides a shortcode, so you can add it everywhere, no matter the builder Tips to speed up the process to get the content Install Freesoul Deactivate Plugins Go to Freesoul Deactivate Plugins => Actions => Content No Cache Disable all the plugins that you don’t need to output the content Example You can see Content No Cache in action visiting the blog post Exclude specific content from being cached. You will see a number that is always different when you refresh the page. But the page is served by full page cache. In the example it’s just a number, but you can output whatever content you want. Possible conflicts Some plugins don’t load the shortcodes during ajax requests. Because Content No Cache retrieves the content through ajax, in those cases the content will not be displayed properly. If you have this kind of issue set the parameter request=”remote”. In this case the shortcode will look like [content_no_cache id=”3328″ request=”remote”] The plugin will retrieve the content in a different way that will be a little slower, but this will solve this kind of conflict. Help If something doesn’t work for you, don’t hesitate to open a thread on the Support Forum Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read this detailed tutorial on how to enable debugging in WordPress to learn more. Backend Speed Optimization Is your dashboard slow? I optimize admin performance by improving queries and plugin load. Read Backend Speed Optimization for more information.

Features Caches the output of your menus. That’s it 😉 Specifically, it caches the output for every unique page. This allows the menus to retain the current/parent/child classes unlike most other menu caching plugins. Why should I use this plugin? If you want to cache your menu content obviously, but specifically if you want to cache your menu content and keep the current/parent/child page classes working. Most menu caching systems do not cater for keeping the various classes working, whereas this plugin does. Why shouldn’t I use this plugin? You should not use this plugin if you have a huge number of posts/pages on your site. The plugin caches each menu individually for each post. This can result in a huge number of cached menus on some sites, which could actually resulted in a slower site in those situations. It could also overload your object cache backend if it has insufficient memory to store them all. Languages USA English Deutsch (German) – thanks to Alexander Praetorius for providing this translation.