[Josh]

Oops, turns out turning caching back on (see previous post) doesn’t work. Guess we have to leave caching off.

Hopefully updating the plugin in the future will clear the cache as stated by Steven above since it will set the $cache = TRUE again and rely on the cached data as created by the Plugin.

NOTE: I also tried the functions.php snippet to force refresh the cache for the items, but it didn’t work for me either.

[Steven Zahm]

@ Josh

Sorry, yes, the php snippet isn’t going to work the way I thought. refreshing the cache is going to be trickier than I initially thought.

Dropping this in the theme’s functions.php file should be update safe. It disables the use of the cache. Using the same method as editing the core files does.

function cn_disable_output_cache( $cached ) {

	return FALSE;
}

add_filter( 'cn_address_cached', 'cn_disable_output_cache' );
add_filter( 'cn_phone_cached', 'cn_disable_output_cache' );
add_filter( 'cn_email_cached', 'cn_disable_output_cache' );
add_filter( 'cn_messenger_cached', 'cn_disable_output_cache' );
add_filter( 'cn_social_network_cached', 'cn_disable_output_cache' );
add_filter( 'cn_link_cached', 'cn_disable_output_cache' );
add_filter( 'cn_date_cached', 'cn_disable_output_cache' );

• This reply was modified 12 years, 10 months ago by Steven Zahm.

[Steven Zahm]

@ Tim

Can you use the method from my previous post?

[Tim]

@ Steven

I added this code and it seems to work.
I assume that the cache values are not used at all when I have these settings in.

I also assume it might have some impact on performance if there’s a lot of information to load (as it has to load from all tables instead of just the one).

If you do work out a way to mass refresh the cache (even if it’s from the dashboard using a bulk action of “refresh cache”) that would help. Maybe to include in the next version?

Thanks.

[Steven Zahm]

@ Tim

Right, using these filters disable the use of the object caches which will mean more db hits; about 7 per entry displayed on the page. That’s not the end of the world considering WP can already be db intensive. Two things that can be done to mitigate the additional db load. Use a template that supports pagination and add a page caching plugin.

I think what I may do, rather than baking it into the plugin, is create a free extension that’ll add a bulk action.

[Author]

Posts