Query on Transient woodmart_swatches_cache (Great Size BD)

Hi Team,

I am reaching out regarding a substantial increase in our WordPress database size due to numerous entries related to the woodmart_swatches_cache transient. We are currently using the LiteSpeed Cache plugin and are concerned about potential redundancy or conflicts.

Could you please advise if this transient is essential when using LiteSpeed Cache, and if it is safe to purge these entries to reduce database bloat?

Your guidance on best practices for managing these transients with caching plugins would be greatly appreciated.

Regards

Attachments:

You must be logged in to view attached files.

Hello,

We don’t recommend disabling this cache because it will increase load on your server load. Yes, if you have a full page cache like Litespeed it will not affect your website a lot. To disable these transients you can add this snippet to the functions.php file in your child theme

add_filter( 'woodmart_swatches_cache', '__return_false' );

Kind Regards

Hi Artem,

Ok, I will check it. Thanks.

Regards.

You are welcome. Feel free to contact us if you have any further questions.

If using a cache like Seraphinite Accelerator and using Object Cache 4 Everyone with memcache, is it safe to say we can remove the bloat from wp_options with

add_filter( ‘woodmart_swatches_cache’, ‘__return_false’ );

then remove transients
DELETE FROM wp_options WHERE option_name LIKE ‘%woodmart_swatches_cache%’;

If we wish to roll back and enable the swatches again, simply remove the add_filter and the cache will be generated as pages load; or do we need to run something to restore wp_options?

[Author]

Posts