Marko Vasiljevic

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!

Hello,

Thank you for reaching out and I am happy to help!
Currently, there is no way to achieve what you are trying to achieve with the W3 Total Cache, or any other plugin without some custom dev work.
We are working on a solution for this which will solve a lot of problems and potential problems with the issue you are describing and other things with e-commerce websites.
It’s difficult to cache-per-user without collecting the user data so we are working on a different approach.
Thank you for your question and your patience.

Hello Karen,

Thank you for your feedback and for providing the screenshot.
This is the first time I have seen this type of problem. Just to confirm, this issue is gone when Lazyloading is disabled in the W3 Total Cache?
Also, does this occur on specific pages, and when are specific actions taken?
Thanks!

Hello Karen,

Thank you for reaching out and I am happy to help!
Can you please share an example, like a screenshot or paste here what you are seeing so I ca understand the issue?
I’ve checked the website, and I can see that the Lazyload is enabled in the W3 Total Cache settings.
Please share the details so I can understand better what you are referring to so I can assist you with this.
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
Without looking and checking the actual website, it’s hard to troubleshoot this.
When you say that the images are loading as original images, are you referring to the extension of the content type of the image, meaning how it’s being served?
As for your API question, the Global API permissions cannot be changed as far as I know. However, you can set required permissions (your choice) create a custom API token, and use this instead of Global API as this is also supported in the W3 Total Cache.
I hope this helps!

Hello Heather,

Thank you for reaching out and I am happy to help!
Have you purged the cache in the W3 Total Cache once the update was finished and see if the issue still persists?
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,

Thank you for reaching out and I am happy to help!
Can you please share if any other options besides the Page Cache are enabled in the General settings in W3 Total Cache and 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 Larry,

Thank you for your feedback.
Ah yes, this seems to be occurring problem with the wp 6.0 and above.
I’ll share this with the team and we’ll have to double-check this and make sure to avoid this.
Thank you for taking the time to report this.

Hello,

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 help!
It seems that you did not save the W3 Total Cache settings after you verified the license key.
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 Ryan,

Thank you for reaching out and I am happy to help!
W3 Total Cache does support PHP 8.3. The error you are mentioning is not comming from our plugin, so can you please share the full error or the screenshot where you are seeing this?
Thanks!

Hello Joe,

Thank you for your feedback.
The dev team is checking this issue and I’ll get back to you as soon as I have more information for you.
Thanks!

Hello Charles,

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 in Perfomance>Support>Billing or this contact form and provide the information about the subscription (This is a public forum so please don’t post any sensitive information), so we can share the information you need?
Thanks!

Hello Lucas,

Thank you for reaching out and I am happy to help!
I’ve replied to the W3 Total Cache support question in the wp.org topic you opened for this issue. Please continue the correspondence there so we can avoid duplicating the questions.
Thanks!