Marko Vasiljevic

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!

Hello Ellie,

Thank you for contacting the W3 Total Cache support, and I am happy to help!

Your subscription is now canceled, and no additional invoices will be issued for this subscription.

Thanks!

Hello Jesse,

Thank you for reaching out, and I am happy to help!
We’ve received your email via the W3 Total Cache support channel, and we replied to it.
As you mentioned, the images are now fully converted.

Thanks!

Hello Adam,

Thank you for reaching out to the W3 Total Cache support channel, and I am happy to help!

Your subscription is already canceled and no additional invoices will be issued for this subscription.

Thanks!

Hello Robert,

Thank you for reaching out, and I am happy to help!
As with any other plugin, W3 Total Cache can be deleted via the plugins section in the WP-Admin area. W3 Total Cache is a robust plugin as it offers a lot of possibilities for optimization. This being said, there are a lot of files; however, the W3TC is not responsible if the files are not deleted from the server when removing the plugin. What happens is that the hosting restrictions, especially when it comes to permissions, may cause some residual files to remain on the server. I assure you, the W3TC, when being removed, is like any other plugin; however, you can always do this manually

As for the other question regarding the CSS issue you are experiencing, this is why the W3 Total Cache is the best optimization solution, as it offers something called Cache-busting
The option “Prevent caching of objects after settings change” in Performance>Browser Cache can be enabled for individual files, and it can be enabled for all CSS and JS files under the CSS&JS section in the Browser Cache. Since the suggested expiration for the static files is 1 year, the “cache-busting” can be achieved with the Prevent caching of objects after settings change, which adds the query string to the file, and once updated, the browser will naturally fetch a new version since it’s not the same file
For example, if the option is enabled on the plugin that has a file https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css the query string will be added:

https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x1234

If the content of the CSS file is changed, and the option “Prevent caching of objects after settings change” is enabled for CSS&JS files, all you have to do is to update the media query string using the “Update media query string” button in the Performance>Browser Cache at the top of the page, which will then update the string and force the plugin to fetch the new version:

https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x4231

After updating the query string, you also need to purge the cache.

I hope this helps!

Thanks!

Hello Amjad,

Thank you for reaching out, and I am happy to help!

I’ve reset the active URL
Remove the license key from the W3 Total Cache Performance>General settings, Licensing sub-box, license field, and save all settings. Re-enter the license and save all settings.

W3 Total Cache Pro should be active after these steps!

Thanks!

Hello Krisztián,

Thank you for reaching out, and I am happy to help!
When the W3 Total Cache Pro was purchased and when you subscribed to the Pro version, you accepted the terms and conditions, specifically section 12.2 Automatic Renewal of Premium Subscription Plans https://www.w3-edge.com/policies/. This means that you were notified about the auto-renewals, as you can see in the screenshot
The ” Renewal Reminder ” email was sent to the email address used to subscribe to W3 Total Cache Pro, one week prior to the renewal of the license. This email has a link to manage your subscription, and you were able to cancel the upcoming renewal.

Please reach out directly via the W3 Total Cache support channel in the plugin – Performance>Support>Billing and provide information about your subscription so we can avoid sharing sensitive data in a public forum!
Thanks!

Hello Cinzia

Thank you for reaching out, and I am happy to help!

Just to confirm, are you using a Fragment Cache extension in the W3 Total Cache to set this up, or are you trying to set up Page Fragment Caching?

Thank you for the clarification!

Hello Eli,

Thank you for reaching out, and I am happy to help!
I’ve replied to your request on WP.org related to the W3 Total Cache question

Thanks!

Hello Julie,

Thank you for reaching out, and I am happy to help!
This exception list is for the static files, where the random query string is being added if the option in W3 Total Cache – Performance>Browser Cache>Prevent caching of objects after settings change is enabled.
Once enabled, this option adds a random query string to the static files, like: /wp-content/cache/minify/715a5.js?xNNNNN
If the file path is added to the list, it will strip the query string only for that specific file:
/wp-content/cache/minify/715a5.js
If you want to add any page to to exception from caching, you can do this in Performance>Page Cache>Advanced>” Never Cache following pages”, and add a page you wish not to cache to that field, for example:
/some-page/

Make sure to save all settings and purge the cache

I hope this helps!