Marko Vasiljevic

Hello Remco,

Thank you for choosing the best caching plugin, W3 Total Cache.
W3 Total Cache Pro licenses are valid on a per-install basis, meaning you need one for every WordPress instance you run. If you have three separate websites, you will need three licenses in total—one for each site. If you have five sites in a WordPress multisite instance, you need just one license for all five sites.
We do not currently offer any licenses for developers, however, if you are interested in bulk licensing, please email us for more information, and let me know the details so we can offer you the best deal.
Thanks!

Hello Carlos,

Thank you for the information and I am glad the issue is resolved.
You can check our Pro support offer and pricing via the plugin in Performance>Support.
Thanks!

Hello Stefano,

Thank you for your question.
Let me check that widget and I’ll get back to you.
Thanks!

Hello,

Yes, you are correct, the Cloudflare is connected.
You are most welcome!
Thanks!

Hello Stefano,

Thank you for reaching out.
The link you provided is the billing account. The W3 Total Cache Pro license key should have been sent to the email address used to subscribe to W3 Total Cache Pro.
W3 Total Cache is a separate plugin so you can drop us a note directly via the plugin in Performance>Support>Billing.
As for the Cloudflare question, you need to use the Global API key. Go to your Cloudflare dashboard>Get your API token, select API Tokens in the top menu, and under API Keys click “view” in Global API Key section:

As for the Backup plugin, this is only a notification that you are not using the recommended Blodgrid Total Upkeep plugin which we recommend.
Thanks!

Hello Eric,
Well, this is really strange.
So the cache control applies to the files but not to the HTML/XMl?
Can you please share more information about your environment?
Thanks!

Hello Diego,

Thank you for reaching out.
I’ve checked your website and I am seeing absolutely no warnings or errors in the console.
Can you please share the screenshot of what you are seeing?
Thanks!

Hello Kamran,

Thank you for reaching out.
Can you please share more specific information on how the website is behaving and what tool you used to test the performance of your website?
Thanks!

Hello,

We’ve received your email and replied to it.
Please follow the instructions there.
Thanks!

Hello Kirill,
I’ve checked the video and now I understand what you are saying, however, this has nothing to do with cache preload.
This is simply the issue with the theme and how it reacts when choosing different user agents via desktop.
Checking the website on mobile indicates that everything is working perfectly as every time the website loads fast on mobile and with no styling issues.
Thanks!

Hello Jason,

Thank you for reaching out!
Please follow the instructions below to completely remove the W3 Total Cache.

1. Check .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are leftover in your .htaccess file after deleting the plugin.
2. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– db.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content/plugins/ (if exists)
3. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled the minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
4. Go to your wp dashboard and re-install W3 Total Cache

5.Please make sure not to use DB caching or OC caching (Disk caching method) if on shared hosting as it’s not recommended to use this anyway if you don’t have VPS or a Dedicated server.

Thanks!

Hello Sherlyn,

Thank you for reaching out.
On the Performance –> General Settings Tab, scroll down to the Miscellaneous section near the bottom. There, you need to uncheck “Use single network configuration file for all sites.”, save all settings and purge the cache.
Once that is done all you need to do is to enable specific setting for each module of the specific website:

Thanks!

Hello Ants,

Thank you for the information.
This is not a very reliable method for testing, however, as I can see you created the same cookie group for all cookies?
You should try creating a separate cookie group for each cookie individually and see if the issue persists.
Thanks!

Hello, Ants,

Thank you for the screenshots.
I’ve checked again and we received no email from you, unfortunately.
The best way to contact us is via the plugin in Performance>Support.
When you say you are not seeing separate caches are generated based on different cookie groups can you please share how you are checking this?
Thanks!

Hello Prajakta,
Thank you for reaching out.
As I’ve already stated in the email I am currently testing the behavior.
No, you do not need the Pro version of the plugin to use Cache Groups.
I’ll get back to you as soon as I can replicate this on the multisite.
Thanks!

Hello Kirill,

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

1. W3 Total Cache does not auto-purge cache unless the post/article is published/updated or any other change on the website that triggers the Perofmrnace>Page Cache>Purge Policy settings.
You can entirely disable those options if you want to purge the cache manually. If the cache continues to be purged after the Purge Policy is disabled then something else might be doing this and not W3TC.

2. You can purge the single page when logged in. In the top admin bar, however over Performance and click on Purge Current Page. Alternatively you can call w3tc_flush_url( $url );
Thanks!

Hello Taofik,

Thank you for reaching out, and thanks for using W3 Total Cache. I am happy to assist you with this.
Can you please share the screenshot of the Performance>Object Cache settings?
WHere are you pulling the info in the provided screenshot from?
Also, is the option Store transients in database enabled in Performance>Object Cache?
Thanks!

Hello Raf,

Thank you for reaching out.

Yes, as suggested those pages should be excused from the cache. Woocommernce added a DONOTCACHEPAGE constant to some templates so it’s not necessary, however, it’s best to exclude those pages from the cache. You can check out this article for more details.
As for the WPML, W3 Total Cache is compatible with the WPML, however, in some cases the Pro extension is needed to improve the caching performance of websites localized by WPML.
Localization is a type of personalization that makes websites more difficult to scale. This extension reduces the response time of websites localized by WPML.
Thanks!

Hello Gertjan,

Thank you for the information. I was going to suggest that or delete the w3-total-cache language in /wp-content/languages/plugins.
If you want to use full site delivery, then yes you should configure the DNS settings as well. If you however only wish to serve static assets from the CDN like JS/CSS files and images, you should follow the steps in the article provided in the previous post.
THanks!

Hello Gertjan,

Thank you for your inquiry and I am happy to assist you with this.
The mentioned notification is in the Stackpath Dashboard widget and it’s only suggesting that CDN is not enabled.
First, you need to signup to Stackpath and follow this guide to set up the Stackpath CDN with W3 Total Cache.
The possible issue with the Authorize button is that it may not work in languages other than English so you should switch your dashboard language to English and try to authorize the Stackpath credentials.
I hope this helps!
Thanks!