Forum Replies Created
-
Posts
-
Hello Danil,
Thank you for reaching out and I am happy to help!
The W3 Total Cache does add the .webp extension to the images once converted. We are not replacing the existing images, we are converting them via the W3TC API and serving them as webp, without changing the extension to .webp.
Are you using any other plugin like some image optimization plugin to convert the images to webp?
Thanks!Hello Peter,
Thank you for reaching out and I am happy to help!
Since this public forum, I recommend you don’t share any sensitive information. Please reach out directly via this contact form, and share the information about your W3 Total Cache Pro subscription so we can check this for you.
Thanks!
Hello Pavel,
Thank you for reaching out and I am happy to help!
I’ve sent you an email via the W3 Total Cache support channel. Since this is a public forum, The details about your license and the instructions to activate it were sent to the email you used for this topic it@
Please continue the correspondence there if needed so we can avoid sharing sensitive information in public.
ThanksHello Rob,
Thank you for reaching out and I am happy to help!
First, we should determine which W3 Total Cache setting may be causing the problem in this case.
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?
Please start with lazyloading if it’s enabled and let me know if this helps!Thanks!
Hello,
Thank you for your feedback and I am sorry about the typo.
Yes, I meant /wp-content/ instead of /wp-config/ So for example if you want to exclude legal_blocks.js just add /wp-content/plugins/iubenda-cookie-law-solution/assets/js/legal_blocks.js to Performance>Minify>Advanced>“Never minify following JS files”I hope this helps!
Thanks!
Hello,
Thank you for reaching out and I am happy to help!
Yes, you can exclude specific JS/CSS in W3 Total Cache. Go to Performance>Minify>Advanced, and add the path to the file in “Never minify following JS files” for example:
/wp-config/plugins/some-plugin/some-js-file.js
Make sure to save all settings and purge the cache.
Thanks!Hello,
Thank you for reaching out and I am happy to help!
Have you configured the CDN accordingly and set up the Azure CDN with the Account name, Account key, and container?
You can also use the Generic Mirror CDN type in the W3 Total Cache for the Azure CDN.Thanks!
Hello,
Thank you for reaching out and I am happy to help!
To completely remove the W3 Total Cache, please follow the instructions below:
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 enable the 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.Thanks!
Hello Kim!
Thank you for reaching out and I am happy to help!
This is very interesting as the W3 Total cache should not create duplicate images. Can you please share the website URL and also, please share the blog post where those images are duplicated so I can have a look?
Please let me know the details so we can assist you with this.
Thanks!Hello Markus,
I am sorry for the issue you are experiencing with the purchase.
We’ve received your email via the W3 Total Cache support channel and replied to it.
Once again I am sorry about the inconvenience, however, please follow the instructions in the email and continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Eva,
Thank you for reaching out and I am happy to help!
The Content Encoding Error suggests that a web server whose HTTP response headers indicate that it will be responding with one type of encoding, but instead responds with a different type of encoding.
In W3 Total Cache Gzip compression is used for this. However, you may have some server-level configurations that utilize different types of compression.
What I would suggest is to completely clear the Firefox browser Cache on your end, re-enable Gzip compression in the W3 Total Cache, save all settings, and purge the cache.
Check if the website is still throwing this error. If the issue persists, please check with your hosting provider if some compression is enabled on their end. For example, you can check for zlib.output_compressionThis can be enabled in the php.ini file, cpanel, or the Apache config file – .htaccess
If you are unsure about this, please check with your hosting provider support.
Let me know if this helps!
Thanks!
Hello Dmitry
Thank you for your feedback.
Ah yes, sometimes, depending on the server the nginx needs to be restarted in order for the configuration to update.
I’ve removed the previous replies with some sensitive details.
As I’ve mentioned before, W3 Total Cache utilizes the rewrite capabilities of the server, to serve the web images. W3 do not change the image extension or replace existing images.
So you will not see the extension changes, just toe content-type: headerThanks!
Hello Dmitry
Thank you for your feedback.
Yes, I can see that the images are converted, when I change to .webp.
Please check your Performance>Install tab, and check the wepb rules. See if those rules are applied to yoru nginx.conf and move them to the top of the nginx.conf file.
I can also see that you are using Cloudflare. This can also impact the files so please make sure that the Cloudflare settings are set to respect origin rules when it comes to Browser Cache TTL.
The main thing you should check is the rewrite rules in the nginx.conf.THanks!
Hello Florian,
Thank you for reacing our and I am happy to help!
Can you plaese ahre the W3 Total Cache version you are curretnly using?
This is not specificaly related to the plugins, and theme, but mostly to the server and server resources.
Can you please inspect the soruce, and check the network tab once the Conver all button is clicked, and see if there are any 404 ajax requests?
Additionaly please check the PHP allowed memory size.
Thanks!Hello Dmitry
Thank you for reaching out and I am happy to help!
W3 Total Cache webp conversion is using a rewrite for the webp. In some cases, it comes down to wether Imagick supports the webp.
Can you please sahre the page on which the image you shared is showing so I can check the source?
Also, have you been using bulk conversion or a single conversion in the Media Library and please let me know if you are using any other image optimization plugin
Thanks!Hello,
You are most welcome!
We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
Thanks!Hello Ranante,
Thank you for reaching out and I am happy to help!
Can you please follow the steps below to completely remove and re-install the W3 Total Cache and see if the problem persists:
1. Deactivate and Delete Plugin
2. Check .htaccess File (make backup)
W3TC will create many directives in .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.
3. 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)
4. 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.
5. Go to your wp dashboard and re-install W3 Total CacheThanks!
Hello David,
Thank you for reaching out and I am happy to help!
The W3 Total Cache detects the Memcached if installed and if running. The notification indicates that the Memcached should be restarted
Check the service at the CLI/SSH: memcached-tool 127.0.0.1:11211 display and memcached-tool 127.0.0.1:11211 stats.
telnet 127.0.0.1 11211
should communicate with memcache and respond to status commands etc
Look if the service is running: ps afux | grep memc
restart the service if needed (as root/sudo): service memcached restart.Hello Paul
Thank you for your feedback.
There is no specific value for the cache to never expire. There is no specific option for this in the W3 Total Cache settings. What you can do is to cache for a year as the static files are cached in the browser, and also add the same value to the Browser Cache settings for the HTML&XML
as for point 2. When you say reverted, what exactly you mean by that? Are you making any changes or the configuration is reset to default?
Thanks!Hey Michael,
Thank you for reaching out.
We’ve received your email via the W3 Total Cache support channel.
We replied with some instructions so please provide more details there so we can assist you further.
Please continue the correspondence there so we can avoid duplicating the answer.
Thanks!Hello,
Thank you for your feedback. Glad to know the problem is resolved
You are most welcome!We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
Thanks!Hello Michael,
Thank you for reaching out and I am happy to help!
Just to confirm, you are trying to manage your W3 Total Cache subscription and you want your email updated for this?
If this is the case, please confirm this, and drop us a note directly via the W3 Total Cache plugin in Performance>Support or the contact form: https://www.w3-edge.com/contact/
So we can provide access to your account as this is a public forum.Thanks!
Hello
Thank you for reaching out and I am happy to help.
When inspecting the source, the testimonial images have this class and style:
class="kt-testimonial-image lazy" style="background-image:
As you can see they are lazyloaded by the theme or the plugin you are using for this, and this may cause conflict.
In the W3 Total Cache there are various ways you can exclude images from being lazyloaded. One of them is to add skip_lazy, however, there is no skip_lazy added for those images as I can see.
In Perforamnce>User Experience, since those are background images, you can disable the option: Process background images, save all settings, and purge the cache. This will result in all the images withstyle="background-image:not being lazyloaded by the W3 Total Cache.
You can also exclude those testimonial images from Lazyload by adding the class namekt-testimonial-imageto Perforamnce>User Experience>Exclude words section.
Make sure to save all settings and purge the cache.I hope this helps!
Thanks!
Hello,
We’ve received your reply.
Thanks! Can we please continue the correspondence via the support channel (email) to avoid duplicating the answers?
Thanks!Hello,
Thank you for reaching out and I am happy to help!
In W3 Total Cache there are advanced settings for each caching module, Page Cache, Object Cache, DB Cache, etc. If you are using Redis, in the Redis settings you can find the Default lifetime of cache objects. With this option, you can manage the cache expiration, however, please note that depending on the website this can impact the memory..
As for the cache express header, the default for the static files is one year and for the HTML is one hour if set. You can also increase this in the Browser Cache settings.
Thanks!
Hello,
Thank you for your patience and the details provided.
In 99% of the cases, there is no need to add anything manually so it’s all down to the server configuration and if the server allows the plugin to modify the files or not.
We cannot force this so in some cases such as yours, the server configuration prevents this.
I’ve checked the files and as I can see the rewrite is now taking place, and all the files look good in terms of not removing the characters. Can you please confirm this?
As for the CDN, and the minified files not being uploaded to the CDN, if you are using origin push, you may need to invalidate those files manually.
You should visit the page as logged in. That will find out which minified URLs are used by that page and the queue upload process of minified urls.
Go to the backend and check that the upload queue is empty. if not – process it.
visit page as logged in again. it should use cdn urls now.
Now you can purge the page cache and visit it as an anonymous user to check that cdn urls are used by page cached version tooI hope this helps!
Thanks!
Hello Paul
Thank you for reaching out and I am happy to help!
In W3 Total Cache there are advanced settings for each caching module, Page Cache, Object Cache, DB Cache, etc. If you are using Redis, in the Redis settings you can find the Default lifetime of cache objects. With this option, you can manage the cache expiration, however, please note that depending on the website this can impact the memory.As for the 2. and 3. this does not seem to be related to the W3 Total Cache. I would need to check this more and get back to you on this.
Thanks!
Hello,
Thank you for reaching out and I am happy to help!
The W3 Total Cache can also process background images and lazyload them. In some cases, the theme or some other plugin, or the way those images are added are also lazyloading those images, and doing this with the W3 Total Cache also can cause conflict, for example:
div class="footer-content lazy" style="background-image: url("https://guillaumelaccordeur.ca/wp-content/uploads/2021/06/Pied-dune-pianiste-et-pédales-du-piano.jpg");" data-bg="url("https://guillaumelaccordeur.ca/wp-content/uploads/2021/06/Pied-dune-pianiste-et-pédales-du-piano.jpg")" data-was-processed="true"This being said, you can try and disable the option in Performance>User Experience Process background images which will prevent W3 Total Cache from lazyloading them, and if that does not work, simply add the URLs of those images to Performance>User Experience>Exclude words: field. Make sure to save all settings and purge the cache after each setting is changed.
I hope this helps!
Thanks!
Hello
Thank you for reaching out and I am happy to assist you with this.
Can you please disable the W3 Total Cache 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 your feedback.
Let me investigate this more and check all the details and I’ll get back to you once I have more information on this.
Thanks!Hello,
I just want to add that manual minify is an advanced technique of minification that allows you a lot of freedom on how you wish to minify the files.
There is no straightforward way of doing this as it all depends on the website, the file dependency, and the number of JS files.
Thanks!Hello,
Thank you for your feedback.
Is there a reason why the Rewrite structure is disabled is disabled? Are you having issues with the rewrite on your environment?
How it should work is when the Files are minified (manual or Auto) they should be stored in the /cache/minify/ folder if you are caching to disk.
the Rewrite structure is disabled, which may also be related to the gzip compression. You should also check if you have zlib enabled and that may be causing double compression.I cannot replicate any of those things you mentioned as the files are minified correctly, gzip is enabled and the files are uploaded to the CDN.
When it comes to the javascript errors, I can confirm that the W3 Total Cache does not remove anything from the files when minified, so you may want to disable minify and see if any of the files are corrupted or if you are getting the errors in the console.
You should also provide details about your environment, the setup, the PHP and the wp version, the type of server, and the plan with your hosting provider.I also want to mention that the replies will not be faster if you ask the same question in multiple channels, like here, via the plugin or the chat. Please understand that some issues are very specific to the environment and the server configuration and cannot be easily replicated.
Thanks!
Hello,
Thank you for reaching out and I am happy to help!
The minified files should be served from the CDN, and that should not be a problem.
In W3 Total Cache, you have to push and pull CDN Type and also the options To serve minified files.
Can you please share your website URL and the screenshot of the CDN settings?Thanks!
Hello Allen,
Thank you for reaching out and I am happy to help!
The settings are stored in wp-content/w3tc-config/master.php. When the W3 Total Cache is temporarily disabled, this file is not removed. This being said, if the plugin is disabled and then enabled again, the settings will remain the same so you won’t need to re-configure from the start.
Thanks!
Hello Carly,
Thank you for reaching out and I am happy to help!
In W3 Total Cache, the HTML minification is just one of the options that can improve the performance of the website. This is a straightforward option; you only need to enable it within the Minify section of the plugin.
However, The vague explanation from the Site Health is misleading the focus of your question. Also, you should take into consideration the inline JS and CSS, and also the number of the JS and CSS files that are embedded in the HTML that also should be minified/combined.
The main reason is the TTFB or time to the first byte which is in your case more than 3 s.
I would suggest you run the setup guide in the W3 Total Cache settings Performance>Setub guide and see which caching methods are available on your server and what is the difference between caching and not caching the pages.
Also, please let me know where the website is hosted and if you are on a shared hosting with limited resources.
Thanks!Hello Emiliano,
Thank you for reaching out and I am happy to help!
The general rule is that you should not cache the pages for logged-in users, simply because of the reason you mentioned. Once cached, the pages will show for the next visitor as cached. This may lead to the sharing of some sensitive information.
You cannot have separate cached pages from logged-in users and non-logged-in users. And even if that is available, you should have a separate cache based on the user to avoid sharing some sensitive/account details. This means, more caching, and more server resource consumption. Not to mention that the separate user caching would have to be based on the data that the user provides, and we cannot collect this data due to the GDPR rules.
However, W3 Total Cache is an advanced plugin for a reason, and you can achieve what you need, but this means some specific configuration.
As a guideline, you should disable caching for logged-in users and only allow caching for subscribers/customers (If this is the user role). Next, Browser Caching is a big NO in this case, so you should modify the Browser Cache for the HTML and set the expires headers to not cache and no-store. This will also impact non-logged-in users.
And of course, any pages with sensitive information like checkout, cart, or account should be excluded from the cache.
The login/logout is also something that should remain dynamic, so this depends on the plugin you are using for this. and you can use Page Fragment Caching, and wrap the PHP code for the login/logout with the mfunc to exclude that part of the page from being cached. Alternatively, you may use AJAX call for login/logout.to direct your question directly, There is no way to only cache a couple of pages for logged in users. There is no option to add pages to cache only to exclude them from being cached.
I hope I explained this and let me know if you have any other questions.
Thanks!
Hello Aleksandra
Thank you for reaching out and I am happy to help!
In W3 Total Cache the limits for the webp conversion are:
The free version:
Hourly limit: 100
Monthly limit: 1000Pro version:
Hourly limit: 10000
Monthly limit: UnlimitedI hope this helps!
Hello Brian,
Thank you for your patience.
I’ve had a chat with the management and there is no non-profit discount at this time for the bulk activations, however, I can confirm that we can give the 2 extra sites at the same rate of the 10 packThanks!
Hello,
Thank you for reaching out and I am happy to help!
Have you confirmed if the issue is related to the Page cache option in the W3 Total Cache?Can you please share if there is a specific page or all the pages on which someone gets banned?
Thanks!Hello Brian,
Thank you for your feedback.
I will check more with the finance dept and the management, however, I can say now that we can go with 12 activations for the bulk of 10
If you have any other suggestions, please reach out directly via the plugin in Performance>Support or via the website contact form.
Thanks!
