Forum Replies Created
- Posts
Hello Berto,
Thank you for reaching out and I am happy to assist you with this.
You explained the process, and yes, this is correct. Once the Page Cache is purged, the cached files get the _old extension, which means that those are expired files. This is actually done to prevent loading the cached page, and force updating the page cache. The Garbage collection interval: in Performance>Page Cache>Advanced is used to remove all the _old files from the cache directory in the specific time set, which is triggered by wp_cron.
By default, the Garbage collection interval is set to one hour (3600s) and after the cache is purged, the _old files will be removed in that interval.I hope this clarifies things and answers your question.
Thanks!
Hello Andrea,
Thank you for reaching out and I am happy to assist you with this.
I’ve checked your website and as I can see the W3 Total Cache is enabled on your website:<!-- Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/ Object Caching 805/809 objects using memcached Page Caching using memcached Lazy Loading Minified using memcached Database Caching 3/69 queries in 0.058 seconds using memcached Served from: calabria7.it @ 2022-09-16 17:59:00 by W3 Total Cache -->Can you please share the screenshot of your admin area and see if you have W3 Total Cache under Plugins>Installed Plugins and if the Performance is listed in the left admin tab?
Thanks!
Hello Jeff,
Thank you for your feedback and I am happy that the issue is resolved.
You can access the W3TC support change within the plugin in Performance>Support, or via the website contact form.
For any additional questions regarding your W3 Total Cache Pro subscription, please send us a direct message.Thanks!
Hello Piotr,
Thank you for reaching out and I am happy to assist you with this.
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.Hello Jeff,
Thank you for reaching out and I am happy to assist you with this.
The license key was sent to the email address used to subscribe to W3 Total Cache Pro. Since this is a public forum, I can not share the email or the actual license key with you here.
I can see that License checked last at 2022-09-15 15:57:16
Please drop us a note directly via the W3TC support channel, or via the website contact form, so I can assist you further with this.Thanks
Hello,
We’ve received your email and replied to it via the W3 Total Cache support channel.
If you have any additional questions, 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.
I’ve checked the W3 Total Cache support channel and we do have 3 emails related to your license, however, none of them is related to the license management problem.
Can you please drop us a note directly via the plugin in Performance>Support, or via the website contact form and share the link for license management
Thanks!Hello,
Sorry for the late reply I was trying to replicate the problem.
By default, minify should not be enabled for logged-in users so you should disable this option.
This is a very peculiar use case, and honestly, I’ve never had a chance to encounter this kind of issue.
As for The unsuccessful transfer queue, you should click the button near it and try to re-upload files.
if works – it’s a temporary issue linked to server resources.
You are using CDN Type: Push, and this means that invalidation of the files needs to be done manually.
The Only purge CDN manually option, if enabled is there to ensure the CDN purge is done manually due to the huge AWS bills for invalidations.
You can always submit a bug report in Performance>Support.Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
I’ve replied to your email via the W3 Total Cache support channel and provided you with all the necessary information, the license key, and the information on how to activate the license.
Let me know if you have any other questions via the support channel.
Thanks!Hello,
Thank you for reaching out.
I’ve replied to your email via the W3 Total Cache support channel, and I’ve just replied again.
Please check your email and continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Saif,
I’ve removed the URL.
You can reach out directly via the plugin in Performance>Support, or via the website contact form.
The file is generated in the /app/cache/minify/ folder. In order to be served from the CDN, you may need to purge the CDN so that new files are uploaded.
If all other files are uploaded, that means that you do not need to add the path to the custom files list.Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
To confirm, you are also using the W3TC CDN feature to upload files to CDN, or are you using some other plugin for this?
If you are using the W3TC CDN module, can you please check if the option “Host minified CSS and JS files” is enabled in Performance>CDN>General?
Is the problem with both CSS and JS files or only CSS files are not being uploaded to the CDN?
Since the path of the files is modified (normally it should be wp-content/cache/minify/), you can try adding the path to the Custom file list: in Performance>CDN>Advanced.Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
W3 Total Cache check for mod_php. Not detected means you don’t use mod_php mode, so you probably use php-fpm. We cannot detect Apache modules in that case, but that doesn’t mean it is not installed/active.
We are working on improving the compatibility check in the future.Thanks!
Hello Stergios,
We’ve received your email and replied to it via the W3 Total Cache support channel.
Please continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Stefan,
Thank you for reaching out and I am happy to assist you with this.
Gzip was designed specifically to compress files. The library has been incorporated into a lot of different programs that need to compress files. The library was incorporated into web servers as compressing content started to be the norm. It was one of two compression algorithms specified in RFC 2616, the HTTPS 1.1 specification. While it wasn’t specifically designed for streaming operations like web servers, it was adapted to it.Brotli, on the other hand, was specifically designed for the web. Google recognized the need for a way to compress streams more efficiently so they designed Brotli.
If you have both settings enabled in the W3 Total Cache Browser Cache section, most of the modern browsers will favor Brotli compression and the ones that do not support it (very few) will show Gzip.I hope this answers your question.
Thanks!
Hello Diego,
Thank you for reaching out and I am happy to assist you with this.
Since this is a public forum, I’ve sent you the information you requested via the W3 Total Cache support channel at diego.bottoni@ email you posted this topic with.Let me know if you have any other questions.
Thanks!Hello Jonathan,
Thank you for reaching out.
What you want to achieve is Full site delivery via CDN. Meaning not only the static files are served from the CDN, but HTML also.
This is possible to achieve, but not the way you mentioned.
For FSD CDN, I would recommend using Stackpath CDN as a provider. Also, note that the FSD CDN feature in W3 Total Cache is only available for Pro users.
Thanks!Hello Stacey,
Thank you for reaching out and I am happy to assist you with this.
Please understand that the number of requests can be huge depending on the time of the day, and also note that W3 Total Cache Pro users have an advantage when it comes to converting images. This is why at some point conversion can take a bit longer than expected.
We are working every day to improve this process to be faster for all users.
You can safely turn the Image service off in Performance>Extensions and deactivate the feature.
Once deactivated all images will be prevented back to original state
I hope this helps!
Thanks!
Hello Duane,
I am sorry about the issue you are experiencing with the W3 Total Cache Pro license, and I am happy to help!
Please reach out to us via the W3TC support channel in Performance>Support and share the license key or subscription information or use the website contact form
Let me know the information so I can check the subscription and the license key.Thanks!
Hello,
Thank you for reaching out and I am happy to assist you with this.
For this, you can use Page Fragment Cache as a method in W3 Total Cache to exclude specific parts of the page from being cached.
With this method, you can wrap the PHP code with(replacing the PHP tag). This will ensure that this part of the page will be excluded from Page cache.
Please note that this is only available when using Page Caching Method Disk, or Memory-based caching methods like Memcached or Redis.
You can check more about this on our FAQ page
The best method is to fire these parts with Ajax, which will automatically bypass the cache.
Thanks!Hello,
Thank you for your question ad I am happy to assist you with this.
When W3 Total Cache is disabled, all extensions and features are also disabled. SO the answer is no, this is not possible, however, this does not mean that the website is not connected to Cloudflare, as the Cloudflare extension is used to connect W3 Total Cache with the Cloudflare dashboard.Thanks!
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!
