Marko Vasiljevic

Hello Filip,

Thank you for reaching out and I am happy to help!
I’ve checked your website and it seems that besides other W3 Total Cache, you have more than one caching solution like Cloudflare and a server-side caching: x-dh-cache: HIT
Can you please let me know if you are experiencing the same problem if you temporarily disable the W3 Total Cache?
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
I’ve removed the sensitive information for your initial request as this is a public forum.
I’ve sent the email with all the requested information to the email addresses you provided via the W3 Total Cache support channel.
Please continue any correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Laszlo,

Thank you for your feedback.
The subdomains should be added once per line
https://cyclesoftware.fr/
https://cyclesoftware.be/
Also can you please share what exactly you are trying to change or update on the website so I can understand better the issue you are having?
Can you please share the screenshots of the updated main website and what happens in the subdomains?
Thanks!

• This reply was modified 2 months, 1 week ago by Marko Vasiljevic.

Hello Laszlo,

Thank you for your feedback.
I assume that the plugin is enabled on the main website and the other languages are created with the WPML. In Performance>Extensions, you can enable the WPML extension if you are using the WMPL plugin and the W3 Total Cache Pro.

Also, in Performance>Page Cache>Aliases, please enable the Cache alias hostnames: option and add the subdomains https://cyclesoftware.fr/ and https://cyclesoftware.be/ to the Additional home URLs: field, save all settings and purge the cache and let me know if the problem persists?
Thanks!

Hello Hugo,

Thank you for reaching out and I am happy to help!
This is a public forum, so I have removed all sensitive data, and sent you an email via the W3 Total Cache support channel with all the information you requested.
Please continue the correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Dan,

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

Hello Vladislav,

Thank you for reaching out and I am happy to help!
Can you please share if this is a Multisite or the subdomains are created with the Polylang?
In W3 Total Cache, Performance>Page Cache>Aliaces, enable the Cache alias hostnames: and add the additional URL’s to Additional home URLs: save all settings and purge the cache and let me know if this helps!
If this does not help, please disable the settings one by one in 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 Peter,

Thank you for reaching out and I am happy to help!
I’ve removed the sensitive data you shared as this is a public forum.
I’ve also sent you an email with the updated invoice attached via the W3 Total Cache support channel so please make sure to check.
It was sent to the email you provided here.
Thank you!

Hello Altin,

Thank you for reaching out and I am happy to help!
You can exclude the scripts from Minify in W3 Total Cache, however, scripts are also part of the HTML, and once the page is cached, the content of the page is cached also.
Can you please share more details on what you are trying to achieve? When you add a product, does that product show on any of the pages that may be cached?
Do you need any specific part of the website to not be cached or cache should be bypassed?
And can you also clarify the issues with the checkout process?
Thanks!

Hello Simone,

Thank you for reaching out and I am happy to help!
We’ve sent all the information to the email you provided about the activation of the W3 Total Cache Pro
Please check your email and continue the correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Leo,

Thank you for reaching out and I am happy to help!
In the W3 Total Cache General settings, remove the license key from Performance>General settings, Licensing sub-box, license field and save all settings. Re-enter the license, verify the license with the “verify license button” and save all settings.

W3 Total Cache Pro should be active after these steps!
Thanks!

Hello Oleg,

I am sorry about the issue you have experienced with the PayPal checkout and I am happy to help!
I can see that you have purchased a W3 Total Cache Pro with the Credit Card and I am glad it worked for you
We are aware of the current issue with the PayPal checkout and we are working on a fix for this.
Thank you for taking the time to report this and for your patience.
Thanks!

Hello Fred,

Thank you for reaching out and I am happy to help!
This indicates that you have enabled the Lazyloadin option in the W3 Total Cache, and what you are referring to is a placeholder that is used in those cases.
This is perfectly normal behavior and it does not impact the website performance or act as an external resource.
As the user scrolls down the page, the image placeholders start coming into the viewport (visible part of the webpage). We trigger the load for these images when they become visible.
I hope this helps!
Thanks!

Hey Daniel,

Thank you for your feedback.
I’ve checked the support channel and there are no emails from you still.
If you’ve sent a request let me know so I can confirm this
Thanks!

Hello Eric,

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

Can you please remove the W3 Total Cache completely and re-install the fresh version?
1. Check .htaccess File (make backup)
W3TC will create many directives in the .htaccess file to control the 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 left over 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 the 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 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

I hope this helps!

Thanks!

Hello Mike,

Thank you for reaching out and I am happy to help!
In W3 Total Cache, Fragment Caching is a Pro feature, the Page Fragment Cache is a different feature and it’s free.
“Page Fragment Cache” dynamically loads the content (in real-time) on your cached pages by parsing them for specific tags you manually embed. Despite the naming, this feature should not be misunderstood with “Fragment Cache”, the premium feature. “Page Fragment Cache” is related to the parsing of templates. “Fragment Cache” adds more complex behaviors to a template/theme or plugin. It extends the transient API in WordPress to provide caching and purge policy management for fragments you manually create. It also enables fragment groups, defined by a plugin or theme, which include common operations to be cached using transients.

Page Fragment Cache cannot be used in combination with Page Cache mode Disk: Enhanced because that mode will load the cached page directly from Apache or Nginx. We recommend using Disk: Basic, which will run PHP to process the requests with the benefit of speeding up responses by loading a cached page instead of building the page from scratch. You can use Page Cache engines Redis or Memcached on dedicated or VPS servers as well.

Note: The comment/code blocks should be added to your theme template files as HTML and not within the PHP open () tags, as it will cause a PHP parse error/syntax error. Do not include any sensitive information in your code fragments; the code can be revealed if W3 Total Cache is deactivated, the Page Cache is changed to use an incompatible storage engine, or the defined W3TC_DYNAMIC_SECURITY string value is changed or not defined.

How does page fragment cache work?
W3TC will search for comments explained below and run the PHP code dynamically before sending it to the browser.

The Page Fragment Cache feature is perfect to display things like the current date and time or content based on the visitor’s session. To be able to use Page Fragment Cache, you define a static variable in your wp-config.php file such as define( ‘W3TC_DYNAMIC_SECURITY’, ‘mysecurestring’ );. Please change the string value “mysecurestring” to something unique. Also add mfunc and mclude to Ignored comment stems: in the Minify settings if it is enabled.

You are then able to use the mfunc and mclude comments as a replacement of the PHP tags like this:

<!-- mfunc mysecurestring -->
if ( is_user_logged_in() ) {
echo '<a href="logout">Logout</a>';
} else {
echo '<a href="login">Login</a>';
}
<!-- /mfunc mysecurestring -->

<!-- mclude mysecurestring -->path/to/file.php<!-- /mclude mysecurestring -->
You could also shorten it a little bit if you prefer one line of PHP code:

<!-- mfunc mysecurestring echo date( 'Y-m-d H:i' ); --><!-- /mfunc mysecurestring -->
<!-- mclude mysecurestring path/to/file.php --><!-- /mclude mysecurestring -->
If you want to use plugin functions or WordPress functions, like is_user_logged_in() in the example above, you have to enable Late initialization: in the Page Cache settings. Other functions, like the ones you defined in your theme, are not available. They should be defined within the fragment to be able to use them.

I hope this helps!

Hello Karen,

It seems that the issue is with your theme and how it handles specific sections of your website.
As I mentioned before, this is the first time I am seeing this and I cannot seem to replicate it. Can you please share the website URL and the specific page you are seeing this on?
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
You cannot specifically exclude the plugin from being cached. In W3 Total Cache, you can exclude specific files from the optimization, if Minify is used, or you can exclude specific pages from being cached.
After checking the plugin you mentioned, this plugin uses Ajax to bypass the cache, meaning depending on the plugin configuration, the cache should not be a problem.
Can you please share the screenshot of the at plugin settings (General Options)?
Also if you are experiencing the issue, can you please disable the settings one by one in 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 Gertjan,

Thank you for the confirmation
Yes, in some cases this may be required (This is not something that is always recommended as it should work automatically), and this is because some rewrite rules need to have priority. In this case, moving the webp rewrite rules to the top of your configuration file is what was needed.
Thanks!

Hello Umberto,

Thank you for reaching out and I am happy to help!
The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, and the technologies available on the server. Since everyone’s site and traffic and theme are different, there is no one-size-fits-all solution.

What should be also be taken into consideration are the idiosyncrasies of Web Performance Optimization (WPO) in a WordPress context. What this means is that WPO best practices have to be modified for WordPress because of how the application operates. The number of counter-intuitive realities could fill a small book.

This means that the best configuration for your site might not involve enabling minify, database caching, and other things that you might expect. As a matter of fact, it can actually hurt performance by implementing features for the wrong situation.

This being said, The W3TC configuration of your website depends on your needs and your resources.
I can see that you are using Cloudflare, which is a form of caching, however, W3 Total Cache works great with Cloudflare so you should check our article about connecting the W3TC with Cloudflare.

Page Caching, Browser Cache, and Object Caching are just some of the things you should enable and use in the W3 Total Cache. The Minify option is also helpful, however, since you are using Cloudflare, Minify may also be enabled there by default.
I hope this helps!
Thanks!