Jose Mortellaro

<p>Normally, if a web page is served by the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>, its content will be always the same until the cache is deleted.</p>
<p>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.</p>
<p>You don’t need this plugin to exclude the entire page from the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>.<br />
This plugin is to exclude a part of the page from the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>. It’s useful if you need to cache a page, but part of that page should not be cached.</p>
<p>Imagine you have a page that has this content:</p>
<p>Hello this is some text.<br />
Another line of text<br />
Another line of text<br />
Current day: Monday</p>
<p>if that page is served by cache, the user will always see:</p>
<p>Hello this is some text.<br />
Another line of text<br />
Another line of text<br />
Current day: Monday</p>
<p>If you need that the last line of text is always updated, this plugin will help you.<br />
The entire page will be served by the cache, but the plugin will get the updated content that you need.</p>
<h3>How to show dynamic content with full page cache</h3>
<ul>
<li>Install Content No Cache</li>
<li>Create a new element “Content No Cache”</li>
<li>Add to that element all the content that you want to exclude from the cache</li>
<li>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).</li>
<li>Add the shortcode to the page where you want to display that content.</li>
</ul>
<h3>Compatible <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">caching plugins</a> tested with Content No Cache</h3>
<ul>
<li><a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-fastest-cache/" rel="ugc">WP Fastest Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-optimize/" rel="ugc">WP Optimize</a></li>
<li><a href="https://wordpress.org/plugins/comet-cache/" rel="ugc">Comet Cache</a></li>
<li><a href="https://wordpress.org/plugins/cache-enabler/" rel="ugc">Cache Enabler</a></li>
<li><a href="https://wordpress.org/plugins/hyper-cache/" rel="ugc">Hyper Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-super-cache/" rel="ugc">WP Super Cache</a></li>
<li><a href="https://wordpress.org/plugins/litespeed-cache/" rel="ugc">LiteSpeed Cache</a></li>
<li><a href="https://wordpress.org/plugins/sg-cachepress/" rel="ugc">Speed Optmizer</a></li>
<li><a href="https://wp-rocket.me/" rel="nofollow ugc">WPRocket</a></li>
</ul>
<p>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</p>
<h3>Compatible CDNs</h3>
<ul>
<li><a href="https://www.cloudflare.com/" rel="nofollow ugc">Cloudflare</a></li>
<li><a href="https://bunny.net/cdn/" rel="nofollow ugc">BunnyCDN</a></li>
<li><a href="https://www.stackpath.com/" rel="nofollow ugc">StackPath</a></li>
<li><a href="https://www.keycdn.com/" rel="nofollow ugc">KeyCDN</a></li>
<li><a href="https://www.fastly.com/" rel="nofollow ugc">Fastly</a></li>
<li><a href="https://aws.amazon.com/cloudfront/" rel="nofollow ugc">CloudFront</a></li>
</ul>
<h3>Main features</h3>
<ul>
<li>Ultralightweight plugin. The few lines of code will run only where you add the shortcode.</li>
<li>No jQuery, no JS libraries, only a couple of lines of pure JavaScript</li>
<li>No database queries, no extra HTTP requests for external assets, no bloat</li>
<li>With a few line of ultralight code you can fully cache the page even if you need dynamic content on that page</li>
<li>It provides a shortcode, so you can add it everywhere, no matter the builder</li>
</ul>
<h3>Tips to speed up the process to get the content</h3>
<ul>
<li>Install <a href="https://wordpress.org/plugins/freesoul-deactivate-plugins/" rel="ugc">Freesoul Deactivate Plugins</a></li>
<li>Go to Freesoul Deactivate Plugins => Actions => Content No Cache</li>
<li>Disable all the plugins that you don’t need to output the content</li>
</ul>
<h3>Example</h3>
<p>You can see Content No Cache in action visiting the blog post <a href="https://josemortellaro.com/exclude-specific-content-from-being-cached/" rel="nofollow ugc">Exclude specific content from being cached</a>.<br />
You will see a number that is always different when you refresh the page. But the page is served by full page cache.<br />
In the example it’s just a number, but you can output whatever content you want.</p>
<h3>Possible conflicts</h3>
<p>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.<br />
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”]<br />
The plugin will retrieve the content in a different way that will be a little slower, but this will solve this kind of conflict.</p>
<h3>Help</h3>
<p>If something doesn’t work for you, don’t hesitate to open a thread on the <a href="https://wordpress.org/support/plugin/content-no-cache/" rel="ugc">Support Forum</a><br />
Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">this detailed tutorial</a> on <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">how to enable debugging in WordPress</a> to learn more.</p>


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

I'm the author, but also a user of this plugin. I solved some serious problems with this plugin, so I will give it a 5 stars review.

By the author

Nice, simple, working as expected, what else can anyone can say?

I just wish there would be a better (and easier way) to trigger the no cache policy, like having a custom CSS class imposing the no cache for a block or div for those who use the Classic editor. Actually even better would be if each block (core or third party) having no cache checkbox on the sidebar.

Nevertheless, for me, for my specific needs, this gets the job done, and some !

Does one thing and it does it really well.


I use this to display "Latest post X hour ago"



It's being cached and sometimes inaccurate. This plugins fix it.



Good job Jose


Works like a charm

Serve uncached partial content even when you add it to a page that is fully cached.

Shitalben Parmar

<p>Export GitLab issues to a CSV file with AJAX progress tracking and Fluent Boards compatibility.</p>
<p>Key features:<br />
* Export issues directly from GitLab into CSV format.<br />
* AJAX-based export with live progress tracking.<br />
* Fluent Boards compatibility.<br />
* Manage and delete generated CSV files from the admin panel.</p>
<h3>How to Create a Project Access Token in GitLab</h3>
<h4>Prerequisites</h4>
<ul>
<li>You must have sufficient permissions (Owner or Maintainer role).</li>
<li>On <strong>GitLab.com</strong>, Project Access Tokens require <strong>Premium or Ultimate subscription</strong>, or a trial.</li>
<li>On <strong>self-managed GitLab instances</strong>, tokens are generally available without restrictions.</li>
</ul>
<p>References:<br />
* https://docs.gitlab.com/user/project/settings/project_access_tokens/<br />
* https://forum.gitlab.com/</p>
<h4>Steps</h4>
<ol>
<li>Log in to GitLab and open your project.</li>
<li>Navigate to <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Access Tokens</strong>.</li>
<li>Click <strong>Add new token</strong>.</li>
<li>Fill in:
<ul>
<li>Token name</li>
<li>(Optional) Token description</li>
<li>Expiration date (default 30 days; non-expiring tokens removed since GitLab 16.0)</li>
<li>Role (Guest, Reporter, Developer, Maintainer, Owner)</li>
<li>Scopes (e.g., <code>api</code>, <code>read_api</code>)</li>
</ul>
</li>
<li>Click <strong>Create project access token</strong>.</li>
<li>Copy and save the token immediately — it will only be shown once.</li>
</ol>
<h3>External Services</h3>
<p>This plugin connects to the GitLab API (https://gitlab.com) to retrieve project issues and export them as CSV files.</p>
<p>Data sent:<br />
* Project ID (required to fetch issues)<br />
* Access token (required for authentication)</p>
<p>Data usage:<br />
* Sent only during export via AJAX requests.<br />
* No WordPress personal user data is sent to GitLab.</p>
<p>Service Provider:<br />
* GitLab Inc.<br />
* Terms of Service: https://about.gitlab.com/terms/<br />
* Privacy Policy: https://about.gitlab.com/privacy/</p>


Issues Exporter for GitLab


Very easy to use and works exactly as expected. Exporting GitLab issues was straightforward and saved me a lot of time.


Simple Setup Great Results


I’ve been using the Issues Exporter for GitLab plugin and it has made my workflow so much easier. The setup was straightforward, and exporting issues into CSV only takes a couple of clicks. I really like the live progress bar during export. it gives me confidence that everything is running smoothly.



The exported files are well-structured, easy to manage, and I can delete or regenerate them directly from the WordPress dashboard. It also works nicely with Fluent Boards, which is a big plus for my team.



Overall, it’s a lightweight plugin that does exactly what it promises without any unnecessary complications. Highly recommended for anyone who works with GitLab and needs quick reports in CSV format!


Simple, Fast, and Works Like a Charm!

Export GitLab issues to a CSV file with AJAX progress tracking and Fluent Boards compatibility.

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