Woodmart with Redis object cache XTS\Modules\Inline_Css_Files->delete_data

Hello. I use Redis object cache and i have strange things with flushes every second heder module or something from theme
XTS\Modules\Inline_Css_Files->delete_data
8 секунд ago
2025-08-13 20:34:25
XTS\Modules\Inline_Css_Files->delete_data, XTS\Modules\Inline_Css_Files->enqueue_page_inline_css, do_action(‘wp_enqueue_scripts’), wp_enqueue_scripts, do_action(‘wp_head’)

Hello

Thank you for your message. To assist you better with the issue related to Redis object cache and the frequent flushes involving XTS\Modules\Inline_Css_Files->delete_data, please provide more detailed information. Could you share the exact steps you take that lead to this behavior on your website? Screenshots or error logs showing the problem would also be very helpful. Additionally, please specify your current Redis and WoodMart theme versions.

This information will help us diagnose the cause and suggest the appropriate solution.

Regards

І am writing to report a critical performance issue related to the theme’s built-in CSS generation feature. When this feature is active, it causes our Redis object cache (managed by the Object Cache Pro plugin) to be flushed continuously on every single page load.

Environment Details:

Theme: Woodmart (latest version)
Plugin: Object Cache Pro v1.24.5
Server: Redis v6.0.16
PHP: 8.3

Steps to Reproduce:

Enable Redis and the Object Cache Pro plugin on the server.

In Woodmart Theme Settings -> Performance -> CSS, enable the option responsible for on-the-fly CSS generation (e.g., “Inline CSS files” or similar).

Monitor the “Flushes” tab in the Object Cache Pro diagnostics panel while browsing the front-end of the site.

Expected Behavior:
The object cache should remain persistent to improve performance. Theme-generated data, if stored in the object cache, should not be flushed on every page load.

Actual Behavior:
The “Flushes” log in Object Cache Pro shows a constant stream of flushes triggered by the XTS\Modules\Inline_Css_Files->delete_data method on every front-end page view. This effectively makes the persistent object cache useless for our site and creates a high number of unnecessary Redis commands, which increases server load.

Temporary Solution / Workaround:
The issue is resolved immediately and completely by disabling the “Inline CSS files” feature in the theme’s performance settings. When this feature is turned off, the cache flushes stop entirely, and the object cache works as expected.

Conclusion:
It appears the delete_data method is being called too aggressively. This function should likely only be triggered when theme options are saved or when the CSS cache needs to be intentionally cleared by an admin, not on every page load for every visitor.

This behavior makes the theme’s built-in CSS optimization incompatible with a persistent object cache environment, which is a standard feature for high-performance hosting.

Could you please look into this issue? Thank you for your great work on this theme.

Attachments:

You must be logged in to view attached files.

Hello,

Could you please disable all plugins that are not related to our theme and provide us your admin access so we can check it?

Thank you in advance

Sorry, but cant. I have large working shop 30 000+ products and dont wanna expiriments. I provide u all nessesary pics and log in first messages. But i assure u – when i disable your css future – object cashe dont flush every second. Pls fix it in next updates or patch.
Thanks

At least provide your admin access without disabling the plugins. We will troubleshoot this on your website.

i fix this by disable in theme settings Inline css and all work perfect.
Pls, don’t disable any plugins and don’t clear wp rocket cache. Al my cache generated very long time.
I use perfmatters for work with css, and Wp Rocket – for js and cache.

Sorry, but we can’t log in with this password.
Maybe you can create a staging website where we can troubleshoot this issue?

I explained, I solved the problem with clearing the object cache every second by disabling the inline CSS option in your theme and provided the logs. Making a stage copy of the site is a 68 GB archive, and it’s stupid)) my server will explode.

[Author]

Posts