Marko Vasiljevic

Hello

Thank you for reaching out, and I am happy to help!
I’ve replied to your email via the W3 Total Cache support channel.
Please check yoru email and the screen recording I’ve sent
Thanks!

Hello Maarten

Thank you for reaching out and thank you for taking the time to report this.

We’ve checked this and confirmed. This security issue has a low severity impact, hwoever we are aware of this and working on a fix that will be released as soon as possible for the W3 Total Cache.

Thank you again for reporting this, and this will be patched soon!

Thanks!

Hello Christy

Thank you for reaching out and thank you for taking the time to report this.

We’ve checked this and confirmed. This security issue has a low severity impactin the W3 Total Cache; however, we are aware of this and are working on a fix that will be released as soon as possible.

Thank you again for reporting this, and this will be patched soon!

Thanks!

Hello Jonathan

Thank you for reaching out, and I am happy to help!
I’ve sent you an email via the W3 Total Cache support channel with the attached invoice you requested.
Please check your email and continue any correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Kesenia,

Thank you for reaching out, and I am happy to help!
Since the issue occurs randomly, it seems that the possible issue is related to your server configuration or resources, and when clearing the W3 Total Cache, the issue is fixed.

Enable logging in wp-config.php:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);

Then wait until the issue happens again and check:

/wp-content/debug.log
What can also be related to your hosting is:
– limit PHP workers
– kill long requests
-restart PHP-FPM automatically
-restart OPcache on deploys/backups

When that restart hits during a request – empty response.

Without cache, one visitor sees an error.
With cache – whole site blank.

Check if therea re any errors when the issue occurs.
Please let me know if you made any updates on your server, like changing the php version?
Also pelase check your PHP Memory Limit and let me know what is it

Thanks!

Hello Stephen,

Thank you for reaching out, and I am happy to help!
I’ve sent you an email via the W3 Total Cache support channel and provided you with all the information you requested.
Please check your inbox and continue the correspondence there if needed, so we can avoid duplicating the answers.

Thanks!

Zdravo Dimitar,

Thank you for your feedback and for providing the information!
This seems to be related to the cache-control for the Browser Caching.
Can you please re-enable the Browser Cache in Performance>General settings, and go to Performance>Browser Cache, and disable the Set expires header in the HTML&XML section, save all settings and purge the cache and let me know if the issue persists.
If the issue is still there, please diable the settings in the Browser Cache section one by one, save all settings and purge the cache after each setting is disabled and let me know which specific setting is causing the problem
Thanks!

Hello Rajiv,

Hello Shenn,

Thank you for reaching out and I am happy to help!
We’ve received your email via the W3 Total Cache support channel. Please check your email and reply to it so we can avoid duplicating the answers
Thanks!

Hello Shenn,

Thank you for reaching out and I am happy to help!
We’ve received your email via the W3 Total Cache support channel. Please check your email and reply to it so we can avoid duplicating the answers
Thanks!

Hello James,

Thank you for reaching out, and I am happy to help!
The W3 Total Cache does not support username/password for Redis authentication; instead, it supports SASL.

You can, however, use the default ACL user (password-only); this way, only the password is needed. Are you able to update the redis.conf for this?

Thanks!

Hey Lauren,

I’ve just re-sent the email with the invoice is attached!
Thanks!

Hello Jelena,

Thank you for reaching out, and I am happy to help!
I’ve sent you an email via the W3 Total Cache support channel, as your subscription is for the W3 Total Cache Pro.
I’ve sent you all the information there because this is a public forum, and we should avoid sharing sensitive data.
Please check yoru email and reply to it so we can avoid duplicating the answers!

Thanks!

Hello Cinzia,

Thank you for reaching out, and I am happy to help!
Just to confirm, you have enabled the fragment Cache Extension in the Performance>Extensions settings in the W3 Total Cache?

What is the Caching method used for fragment caching and also for Page Caching in this case?
And can you please clarify if you are trying to utilize Fragment Caching as an extension or the page Fragment Caching to exclude specific parts of the page using mfunc?
Thank you!

Hello,

Thank you for reaching out, and I am happy to help!
Can you please reach out directly to us via the W3 Total Cache support channel in Performance>Support, and link this topic?
We would be excited to do our part in your endeavor!
This is a public forum, and it’s best to go through a private channel
Thanks!

Hello Lauren,

Thank you for reaching out, and I am happy to help!
Your W3 Total Cache subscription is now canceled, and no additional invoices will be issued for this subscription.

Thanks!

Hey Bill,

Thank you for your feedback.
We’ll make sure to fix this and thank you forbringing this to our attention!

Hello Katie!

Thank you for reaching out, and I am happy to help!
I’ve sent you an email with the requested information via the W3 Total Cache support channel.
Please check the email and the attached invoice.

Thanks!

Hello Bill

Thank you for reaching out, and I am happy to help!
We are aware of the issue relatedto the authentication of the Google page speed tool in the W3 Total Cache, and we are working on the solution and some new implemtations

Thank you for your patience with this!

Hello Clive

Thank you for reaching out, and I am happy to help!
We’ve received your email via the W3 Total Cache support channel and replied to it.
Please continue any correspondence there so we can avoid duplicating the answers
Thanks!

Hello Pascal,

Thank you for reaching out and I am happy to help!
Your W3 Total Cache Pro subscription is now canceled and It will remain valid until 2026-01-30
No additional invoices will be issued for this subscription.

Thanks!