Prevent caching for elements with specific classes or IDs

Hi Simon,

this is a great idea. Yes, it’s possible, with some tricks, but it’s possible.
The PRO version will give the possibility to exclude from the cache HTML elements by CSS selectors.
For example, if you have something that looks like:

<div id="sample-id" class="sample-class">
...
</div>

You will be able to exclude all that it’s inside the div and the div itself by asking Content No Cache to exclude #sample-id, or .sample-class, or whatever CSS selector defines the wrapper.

I will be happy to give you a lifetime license as thanks for this brilliant idea.
At the moment I can’t say when it will be ready. It may require up to 1-2 months because we are very busy at the moment, but I will be very happy to add this feature.

However, for me, it’s hard to believe elements like progress bars aren’t updated with JavaScript. JavaScript is a client-side language, and you should not have any problem with the page cache.

The page cache is widespread and it seems strange to me that there are still elements such as progress bars that do not take into account the cache
If you have a plugin that adds this kind of elements via PHP, you should write the authors and make them notice they should use JS for those elements.

Have a great day

Jose

@szymonfortuna

Hi @advwebmaster777, @szymonfortuna, @helderconde

now with Content No Cache PRO v. 5.0.1 you can uncache the content by CSS class.
It’s important to know that it will work only with the CSS classes that are added with Gutenberg, page builders, or classic editor. If the CSS class is written in a template file, then it will not work.

Have a great day!

Jose

• This reply was modified 2 years, 5 months ago by Jose Mortellaro.

Hi Simon,

said in other words, all that is saved into the database can work.

The CSS classes that are printed by a PHP file will not work.

I will try to make it clearer with an example.

Imagine your theme displays a page through the file page.php where you have a code that looks like this:

<?php
/**
 * The Template for displaying single pages
 *
 */
defined( 'ABSPATH' ) || exit; // Exit if accessed directly.

get_header();
?>
<section id="primary" class="site-content">
	<div id="content" class="content-no-cache-not-working" role="main">
		<?php while ( have_posts() ) : the_post();
		?>
		<article <?php post_class(); ?>>
				<?php the_content(); ?>
		</article>
		<?php endwhile; ?>
	</div>
</section>
<?php get_footer();

In this example if you want to uncache what is inside the element with the class “content-no-cache-not-working”, it will not work.

Instead, what is printed by the_content() is taken from the database. Inside that content, you can have an element with a CSS class that can work.

You add that kind of content when you edit a post, no matter if you do it with Gutenberg, a page builder, or Classic Editor.

If for example you use Gutenberg and you assign a specific CSS class to a block, then that block will be uncached. The same if you assign the CSS class to an element of a page builder, or if you directly write HTML with Classic Editor.

If it’s still not clear let me know.

Have a great day!

Jose