Forum Replies Created
- Posts
Hello,
Thank you for reaching out and I am happy to assist you with this.
W3 Total Cache does have the ability to cache all products and categories. Depending on your store configuration, some templates may havedefine('DONOTCACHEPAGE', true);constant which is used to prevent caching.I hope this helps!
Thanks!
Hello Tim,
Thank you for reaching out and I am happy to assist you with this.
The message you get in the W3 Total Cache Image service with the Lossless type selected means that, unlike lossy compression, lossless image compression won’t reduce image quality. That’s because lossless compression only removes additional, non-essential data.
The trade-off is that you won’t see a significant reduction in image file size.
W3 Total Cache informs you that with the Lossless conversion, the image may be larger than the original; therefore, the conversion is halted.
Is there any reason you are not using the Lossy option for the conversion?
Thanks!Hello,
Thank you for reaching out and I am happy to assist you with this.
I’ve checked your website and I can see that W3 Total Cache is enabled, specifically, Page Caching is enabled as I can see, and Browser Cache.
I checked the mobile version using Android and iPhone, and with different browsers and I am not seeing the issue you are describing.
Can you please confirm you are still experiencing the problem and can you please share the specific page you are having issues with or is the problem random?
Thanks!Hello Adam,
Thank you for reaching out and I am happy to assist you, with this.
I am afraid that this cannot be done with Akamai. In the W3 Total Cache, Akamain is Origin Pull CDN which means that the assets are automatically uploaded.
You can use different Cnames, however, those should be for JS and CSS separately.I hope this helps!
Thanks!
Hello,
Well, this is very strange.
The Cloudflare support refers you to us, even tho the problem started once you started using Cloudflare. And as we confirmed, you have not been experiencing the problem only with W3TC, and this was solved by excluding the pages from the cache.
I am not quite sure why this is happening when you are using Cloudflare. The best thing in my opinion would be to move the login to a /login/ page or /account/ page and not use the popup since it the problems you mentioned may appear.
I hope this helps!Hello,
Thank you for reaching out.
We’ve received your email via the W3 Total Cache support channel and replied to it.
I’ve also added a few suggestions about future optimization and the limitations of other plugins and your hosting plan.
The subscription is canceled, and the money is refunded.
Thanks!Hello Karin,
Can you please reach out directly to us via the website contact form and provide the information about your account so we can find the subscription?
Thanks!Hello Karin,
I am sorry you wish to cancel the subscription. We will cancel the W3 Total Cache subscription for you with no problem.
Can you please reach out directly to us via the website contact form and provide the information about your account so we can find the subscription?
Please note that this is a public forum.
Thanks!Hello,
As I’ve mentioned in the email via the W3 Total Cache support channel, and in the other forum topic, I’ve reset the active URL activated on 2022-07-11
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,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
As I’ve mentioned in the email via the W3 Total Cache support channel, I’ve reset the active URL activated on 2022-07-11Remove 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,
Thank you for your feedback.
Let me know if the problem persists with the default W3TC Browser Cache settings.
Also, make sure to check and configure Cloudflare Page rules and exclude the page from the cf cache.
Thanks!Hello,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
We are aware of this problem in some cases, and we’ve already fixed the issue which will be added to the upcoming W3 Total Cache release.
Please check out our GitHub repository for more details and if convenient, change the lines in wp-contnent/plugins/w3-total-cache/Licensing_Plugin_Admin.php, or revert back to the previous version and wait for the upcoming release.
Thanks!Hello,
Thank you for reaching out and I am happy to assist you with this.
I have to start by saying that last week I started using the Cloudflare extension you guys offer for the CDN. That being said, I now have to clear caches (both site and Cloudflare at once) in order to solve this issue
Just to confirm, did you start to experience the problem once you connected to Cloudflare? The question is have you been using W3 Total Cache before you connected with Cloudflare or vice versa?
I can see that the cache-control header is set to 14400s and the default in W3TC is 3600s, So you may want to check the Cloudflare settings and set the browser Cache rules to respect the origin
Let me know the answer and again make sure that the BC TTL in Cloudflare settings respects the origin headers.
Thanks!
Hello,
1. This means that the wp-content folder is writable which is needed for W3TC for drop-in files and creating a cache folder as well as writing the constant to wp-config.php and adding the rules to .htaccess
2. This means that the .htaccess file does not have the correct 644 permission set so that W3TC can write the rules, so you should set the permissions to 644.
3. By expanding the notification you will see the rules that need to be added to .htaccess file which due to the restricted permissions are not added automatically.
As for the license question, once you click the Reset Active URLs button, the license key should be removed from the active installation. You can do this manually by removing the license key from Performance>General settings, Licensing sub-box, license field, and saving all settings. Re-enter the license key to the other installation in Performance>General settings, Licensing sub-box, license field, verify the license with the “verify license button” and save all settings.
I hope this helps!
Thanks!
Hello,
Thank you for your feedback.
As I can see the website is hosted on Bitnami.
By default, .htaccess files are disabled due to security and performance reasons (their words).The .htaccess files content is moved to a file called htaccess.conf in the folder /opt/bitnami/apps/APPNAME/conf. You can check more about it at https://docs.bitnami.com/aws/infrastructure/lamp/administration/use-htaccess/.
In this link, you can also find a video tutorial that is using W3 Total Cache rules as an example.
Thanks!Hello,
Thank you for reaching out and I am happy to assist you with this
You need to check your files/folder permissions. For W3 Total Cache to write to files and folders, you need to change folder permission to 755 and your .htaccess and wp-config.php to 644
Simply FTP to your website or use Cpanel and change the permissions or as your hosting provider for assistance.
You can also manually add to following to your wp-config.php just under the opened<?phptag/** Enable W3 Total Cache */ define('WP_CACHE', true); // Added by W3 Total CacheI hope this helps!
Thanks!Hello,
Thank you for reaching out and I am happy to assist you with this.
I’ve checked the website and I can see that the cache-control and expires header are not enabled for static files.
Thank you for sharing the screenshot, however, it only shows that the Browser Cache is enabled in the W3 Total Cache – General settings, and this needs to be fine-tuned.
Can you please go to Performane>Browser Cache, and make sure that the “Set expires header” and “Set cache control header” are enabled in the General box including the sub-boxes (HTML&XMK, CSS&JS, Media&other files). Once enabled, save all settings and purge the cache and see if hose headed are added for static files.Thanks!
Hello Gustavo,
Thank you for reaching out and I am happy to assist you with this.
You can reach out directly to us via the W3 Total Cache plugin in Performance>Support, and ask any questions you may have about the configuration of the plugin.
Thanks!Hello Irina,
Thank you for reaching out.
This shows as it states, the percentage on the JS and CSS compression, or the response of the percentage that is cached.
In W3 Total Cache statistical view for exampleCSS compression in cache: 55 % JS compression in cache: 70 %Thanks!
Hello Vlad,
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 W3 Total Cache is active. I’ve tried adding the products to the cart and I am not experiencing the issue you are mentioning. The cart is always updated with new prices and articles.
Can you please confirm if you are still experiencing the problem?
Thanks!Hello,
I am sorry about the issue you are experiencing with the W3 Total Cache license and I am happy to assist you with this.
I found the subscription associated with your email, Jul 11, 2022 4:22 AM EDT and the license key is connected with your website.
Since this is a public forum I will not share information like the actual license key or your email/website.
If you are still experiencing this problem, please drop us a note directly via the plugin in Performance>Support, or via the website contact form.I hope this helps!
Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
By default and for security reasons, only admins can control W3 Total Cache options, including the cache purge.
Access to W3 Total Cache is controlled by the manage_options capability, so this needs to be added to the Editor role.
You can also approach this with a more programmatic solution.
I hope this helps!Hello Chris,
Thank you for your feedback.
Yes, yes differing JS files may be an instant performance boost, however, as I’ve mentioned in your case, the minified JS file in the header does not like being deferred, and the reason behind this is because some files are jQUery dependent.
What you may want to do is to exclude the jQuery file from minifying in Performance>MInify>Advanced>Never minify following JS files, save all settings and purge the cache, and try to deffer files before again.Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, the technologies available on the server, and since everyone’s site and traffic and theme are different, there is no one-size-fits-all solution.
The page is visited once it’s cached. Unless the cache is manually purged, or determined by the purge policy in Performance>Page Cache>Purge Policy (I would recommend enabling the front page since this is a news website) the cache will remain the same.
Since this is a news website, and articles are being added frequently, the W3 Total Cache will purge the cache once the content is changed and updated and the new cache will be generated on request.
As for the other options, I would advise using DB and Object Caching, however, if you do not have Memcached or Redis available on your server, I would not recommend using the Disk caching method for these caching features.Make sure to check our documentation for more details about the W3 Total Cache options.
I hope this helps!
Thanks!
Hello Martin,
Thank you for reaching out and I am happy to assist you with this.
The idea of an Object Cache in W3 Total Cache is that the WordPress Core, themes, and plugins may store some data that is frequently accessed and rarely changed in an object-store. This is so these objects will not have to be retrieved and processed on each request. Ultimately, Object Caching will reduce the total number of database queries required for each page, and because the CPU does not have to rebuild these blocks of data your response time will decrease.In reality, this potential performance improvements of Object Caching are highly dependent on which plugins or themes you use and whether they correctly store these objects. For example, your response time may not decrease if objects are stored and rarely (if ever) used.
As for your question regarding the “Enable caching for wp-admin requests.” option, this depends heavily on the environment, plugins, theme, etc. This is why the side effects are not described in detail. For example, if some wp-admin request is cached, and one of the plugins or WordPress is using it, some features may not be available. In some environments, updating the plugins via the plugins page was not possible if the wp-admin requests were cached.
I would advise to test this out and see if you are experiencing any issues.
I hope this helps!
Thanks!
Hello,
Thank you for reaching out and I am happy to answer.
We’ve received your email via the W3 Total Cache support channel and provided the instructions on how to activate the license key.
As I can see the license key is now active on your website.
Thanks!Hello Cindy,
Can you please confirm that you are trying to install the W3 Total Cache plugin and this is why you are getting the notification?
Please confirm this so we can point you in the right direction and also, please share the name of the hosting provider you are hosting your website on.
Thanks!Hello Chris,
Thank you for your feedback.
First try to set Minify engine settings back to default-blocking, first for Before, save all settings and purge the cache, and if that does not work, do the same for After
There is a chance that the custom code is jQUery dependent, which means that you need to exclude the jquery from being minified when differing the files.
Thanks!Hello Chris,
Thank you for reaching out and I am happy to assist you with this.
We need to determine which setting in W3 Total Cache may be causing this since the activation of the newly installed W3TC only has Browser Cache enabled.
One thing that comes to mind is minify. To confirm this, please disable minify in Perfirmance>General settings, save all settings and purge the cache and see if the issue persists?
If the issue is gone, re-enable minify, and disable the settings in Performance>minify one by one (HTML minify, JS minify, CSS minify) and see which one might be causing the issue.
Make sure to save all settings and purge the cache after each option is disabled.
Also, check if you are using theme optimization for static files in your Divi settings.
Thanks!Hello Alexey,
Thank you for reaching out and I am happy to assist you with this.
I’ve replied to your request via the W3 Total Cache support channel. Please continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Ralph,
Thank you for your patience.
The issue is now fixed. Please update the plugin to the latest 2.2.3 release.
Thanks!Hello Gemma,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
Please note that W3 Total Cache and some other caching plugins may not be allowed on certain hosting providers.
Please upload your screenshot here and share the image so we can check this.
Thanks!Hello Ralph,
I am sorry about the issue you are experiencing and I am happy to help
We already have the Github issue opened for this and most likely the problem is with the Redis fix in the latest W3 Total Cache 2.2.2 release.
Please share the error log so we can confirm it’s the case with your problem too.
We are working on a fix and the solution as we speak, and I would advise reverting back to the previous 2.2.1 stable release until the patch fix.Thanks!
Hello,
Thank you for reaching out and for a detailed explanation of the problem you are facing.
By default, the Auto-convert image after the upload is enabled in the W3 Total Cache Image Servce feature.
Most of the users do not want to bother and just because of that the option Auto-convert is always enabled.
You can disable this in Performance>Extensions>Image Service. Click on the Settings link and select the Disabled radio button in the Configuration area:
Once the images are translated, you can manually convert all images or a single image in the Media library.
I hope this helps!Thanks!
Hello,
Thank you for reaching out and for a detailed explanation of the problem you are facing.
By default, the Auto-convert image after the upload is enabled in the W3 Total Cache Image Servce feature.
Most of the users do not want to bother and just because of that the option Auto-convert is always enabled.
You can disable this in Performance>Extensions>Image Service. Click on the Settings link and select the Disabled radio button in the Configuration area:
Once the images are translated, you can manually convert all images or a single image in the Media library.
I hope this helps!Thanks!
Hello Pim,
Thank you for reaching out and I am happy to assist you with this.
We’ve received your email and I’ve replied with a detailed explanation about the potential issues you may be facing when caching the pages for logged-in users.
Please continue the correspondence there if you have any other questions so we can avoid duplicating the answers.
Thanks!Hello,
THank you for yoru feebdack.
You can reach out directly via the plugin in Performance>Support, and share any information there.Thanks!
Hello Simon,
Thank you for reaching out and I am happy to assist you with this.
The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, the technologies available on the server, and the details you supply when placing your order. Since everyone’s site and traffic and theme are different, there is no one size fits all solution.
So, I would recommend the Performance Audit solution.
This service also takes into account the idiosyncrasies of Web Performance Optimization (WPO) in a WordPress context. It means 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 Objec, 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.
The deliverable with this service is a faster site. It’s impossible to predict the extent to which our work will improve performance (especially true for code we didn’t write running on servers we didn’t build), but our promise is that we’ll do our best.
Additionally, we’ll send along a performance report that outlines the improvements, recommendations (if any), and what else we can do to help you reach and exceed your performance goals. There are many ways that we can help improve performance, you should think of W3 Total Cache configuration as the starting point for optimizing your site.
Upgrading to W3 Total Cache Pro makes this work even more effective, as we’ll have additional features to utilize in delivering the best possible results. It’s best to upgrade before placing your order since we can do this for you, and you can upgrade right in the Dashboard on any W3 Total Cache page.
I hope this answers your question.
Thanks!
Hello Yolandi,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
W3 Total Cache is of course a plugin, and as a plugin, it uses drop-ins depending on the configuration.
advanced-cache.php means that the Page cache was/is enabled in the W3 Total Cache settings.
I would advise you to completely remove and re-install W3 Total Cache.
Please follow the steps below and if you cannot find the W3 Total Cache in the dashboard, please skip the first two steps:1. Purge Cache
2. Deactivate and Delete Plugin
3. Check the .htaccess File (make a 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.
4. 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)
5. 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.
6. Go to your wp dashboard and re-install W3 Total CacheI hope this helps!
Thanks!
