Marko Vasiljevic

Hello Florian,

Thank you for reaching out and I am happy to assist you with this.
In W3 Total Cache Performance>Page Cache, there is a “Late initialization” setting. This is available with Disk: Basic or any memory-based caching.
Have you tried enabling this and see if it helps!?
Thanks!

Hello Andrei,

Thank you for reaching out and I am happy to answer.
W3 Total Cache is a free plugin and upgrading to W3 Total Cache Pro to unlock advanced analytics, fragment caching, full site delivery, extension support, and other tools that will allow you to completely fine-tune your website’s performance.
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. If you are interested in bulk licensing, please email us for more information.

Thanks!

Hello Daniel,

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

Can you please disable the settings one by one in W3 Total Cache Performance>general settings, save the settings and purge the cache after each setting is disabled and see which one might be causing the issue?

Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
Can you please drop us a note directly via the W3 Total Cache support channel within the plugin in Performance>Support>Billing, or via the website contact form? Please provide any information about your W3TC Pro subscription there so we can find the subscription and provide the access to account management.
Thanks!

Hello Mike,

Thank you for reaching out and I am happy to assist you with this.
Can you please drop us a note directly via the W3 Total Cache support channel within the plugin in Performance>Support>Billing, or via the website contact form?
Thanks!

Hello Peter,

Thank you for reaching out and I am happy to assist you with this.
This may be called by some other plugins as well, depending on a theme or the plugins you are using. Since you are updating a product category, there is a chance that woocommerce is calling flush_all.
The W3 Total Cache only purges the page that is updated.
To confirm this, please disable all purge settings in the Performance>Page Cache>Purge policy and let me know if the problem persists.
If the issue persists, it means that 3rd party plugin//them is calling the purge and we have a programmatic solution for this.

Thanks!

Hello Marc,

Sorry for the late reply.
There is no option to do this via the wp-config.php file. You can try is adding db-config.php
Please check more details on our wiki page.
Thanks!

Hello Stephanie,

Thank you for reaching out and I am happy to assist you with this.
You can call the W3 Total Cache function w3tc_dbcache_flush(); to purge the DB cache. You can also use wp_cli and call wp w3-total-cache flush database.

Thanks!

Hello Wolfgang,

In the screenshot, I’ve shared you can see that the image BP-01.jpg is served as webp.
This is how webp conversion works.
All images converted with the Image Service tool are sent to a third-party server maintained by the W3 Total Cache team which reduces resource consumption and allows for a large number of conversions in environments where resources can be limited such as shared hosting. Images sent to the W3TC server for conversion are only held temporarily and no permanent information is kept on the server regarding the images.

WebP optimizations with the Image Service tool do not replace the original image file and all conversions can be reverted without any loss of data.

As you can see in the “Type” section, the image type is webp, which indicates that the image is converted.
Thanks!

Hey Kevin,

Thank you for reaching out!
The license key was sent to the email address used to subscribe to the W3 Total Cache Pro, the one you provided here.
I’ve re-sent the information with the instructions on how to add the license and enable the Pro mode

Thanks!

Hey Maxim,

We have received your email via the W3 Total Cache support channel and replied to it with the information about the license.
Thank you for your patience

Hello Ali,

Thank you for reaching out!

We have received your email via the W3 Total Cache support channel and replied to it with the expiation on how to activate the Pro version.
Please continue the correspondence there so we can avoid duplicating the answers.
Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
Since this is a Public forum, we should avoid sharing sensitive information. Please reach out to us directly via the W3 Total Cache support channel in the plugin Performance>Support, or via the website contact form and share the information about the payment so we can check the subscription for you.
Thanks!

Hello Rod,

Thank you for reaching out and I am happy to assist you with this

I’ve removed the PayPal transaction IDs since this is a public forum.
Please reach out to us directly via the W3 Total Cache support Channel in Performance>Support and provide the information so we can assist you with this.
Thanks!

Hello Alina,

Thank you for reaching out and I am happy to assist you with this.
I’ve checked your website and I can see that the CDN is enabled in W3 Total Cache Performance>General settings, however, you have not selected any provider or configured the CDN.
Can you please disable the CDN in Performance>General settings and let me know if the problem persists?
Thanks!

Hello Jason,

Thank you for reaching out and I am happy to assist you with this.
As per woocomerce suggestion, those pages should be excluded from Page Caching and minify.
This being said, you can exclude any pages from being Cached or minified by adding them to the W3 Total Cahe exclusion:
Page Cache:
In Performance>Page Cache>Advanced>Never Cache following pages field, add /cart/ and /checkout/ – save all settings and purge the cache

Minify:
In Performance>Minify>Advanced>Never Minify following pages field, add /cart/ and /checkout/ – save all settings and purge the cache

Let me know if this helps!

Thanks!

Hello Margo,

Thank you for your feedback.
Usually there two things that may cause this and none of them is related to the W3 Total Cache directly

1- This error is mainly due to the file permissions setting on your server. Try to delete the plugin and install it again. You won’t lose any of your settings this way. It’s like the same process when updating the plugin from Dashboard.

2- Sometimes this error occurred due to not having enough disk space or reaching max files in the web hosting account. Check on the available space in the c-panel because WordPress needs enough space to download the plugin, unzip it, and then move the files across.

I hope this helps!

Thanks!

Hello Edi,

I am sorry about the issue you experienced and I am happy to answer and assist you with this.
W3 Total Cache, depending on a configuration, needs to drop-in specific files in the wp-content in order for the caching to work.
Page Cache – advanced-cache.php
Object Cache – object-cache.php
Database Cache – db.php
If Database Cache is enabled W3TC detects if there is an existing db.php file and if so, there is a notification in the Wp-admin area that the db.php detected is not a W3 Total Cache drop-in and asks the user if the file should be removed. This means that W3 Total Cache does not automatically overwrites the dp.php file, it only removes that file and replaces it with its own if instructed to do so.
Every plugin that has the option for Database Cache needs to add its own db.php file in order to be able to perform as expected.
I hope you made a backup of your own db.php

Let me know if you have any other questions or suggestions.
Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
I believe I already replied to you via the W3 Total Cache support channel and explained this.

What the feature does is this:
– Check the last offset
– Check how many URLs are allowed to be processed per run
– Fetch all URLs from sitemap (even nested sitemaps work)
– Loop through a set of URLs to visit them
If the end of the list is reached, it will start from the beginning in the next run
Calling the wp-cli command is the same as the cronjob, but if you want you can specify where to start this run and how many pages should be visited (instead of using the configuration values)

If your cron job is running every day instead of every minute, that means only one run can be done per day. If the cron job is set to every minute and the interval is set to a higher value, the plugin will check if the interval specified in the configuration has passed since the last time.
So that means if the cron job is not set to every minute, the priming could be delayed, especially if you set it to 1 hour and priming to 1,5 hour
The best is to have the cron job interval smaller than the priming interval and the priming interval should be equal to or a multiplied value of the cronjob interval

I hope this answers your question.

Thanks!

Hello Marc,

Thank you for reaching out and I am happy to assist you with this.
You can check more on how to set up W3 Total Cache with AWS FSD CDN on our wiki page.
Thanks!