Forum Replies Created
- AuthorPosts
- July 8, 2024 at 11:44 am in reply to: Page Cache is preventing moving Media items into the Trash #134961
Marko Vasiljevic
KeymasterHello,
Sorry for the late reply.
I was not able to replicate the issue you are referring to.
I’ve noticed that you have enabled both: “Don’t cache pages for logged-in users” and “Don’t cache pages for following user roles”
If you enabled “Don’t cache pages for logged-in users” there is no need to additionally disable caching for other user roles.
Can you pleas disable “Don’t cache pages for following user roles”, save all settings and purge the cache, and let me know if the issue persists?
Thanks!Marko Vasiljevic
KeymasterHello,
Thank you for reaching out and I am happy to help!
I’ve checked your website and as I can see the images are indeed converted by the W3 Total Cache, however, not served as webp. For example:
https://throughmylens.online/wp-content/uploads/2024/05/Tiger-sniffing-in-the-air.webpCan you please share if the Browser Cache TTL is set in Cloudflare or if it respects the existing headers?
Can you please check and share what is your active editor for media handling and if it supports webp?
To check if your WordPress environment supports WebP, navigate to Site Health > Info > Media Handling and double-check that WebP is listed in the supported file formats for the library shown in the Active editor. If you find these are missing the WebP extension, consult your system administrator to set up the correct packages.
Thanks!Marko Vasiljevic
KeymasterHello Alberto,
Thank you for reaching out and I am happy to help!
Can you please expand this more and let me know what exactly happens when you visit the website while logged in?
What happens if the W3 Total Cache is enabled and you visit the website while logged in?
Thanks!Marko Vasiljevic
KeymasterHello Shane,
Thank you for reaching out and I am happy to help!
Can you please share the website URL? Have you tried re-authorizing the W3 Total Cache for AWS CDN please let me know if you are using Push or Pull CDN type for AWS?
To confirm, once you purge CDN completely with the Purge CDN button the issue is gone?Marko Vasiljevic
KeymasterHello Jackson,
Thank you for reaching out and I am happy to help!
The W3 Total Cache Pro license is annually billed. So there is no option for monthly payment. I am sorry if this was misleading for you and please let me know where you have seen the 8.25$ / month option so we can remove this and make sure that this is more precise.
To confirm once more, the W3 Total Cache Pro license is annually billed and it’s $99/year.Thanks!
June 26, 2024 at 11:56 am in reply to: Page Cache is preventing moving Media items into the Trash #133843Marko Vasiljevic
KeymasterHello,
Thank you for reaching out and I am happy to help!
Can you please share the screenshot of the W3 Total Cache Performance>Page Cache section, and please let me know if the page caching is disabled for the logged-in users because Page Caching should not affect the backend.Thanks!
Marko Vasiljevic
KeymasterHello Adam,
Thank you for reaching out and I am happy to help!
Just to confirm, do you need 5 licenses in total, meaning 3 more W3 Total Cache Pro licenses besides the two you already own?
Can you please share the license? information via the plugin in Performance>Support>Billing as this is a public forum
Thanks!Marko Vasiljevic
KeymasterHello
Thank you for your feedback.
I am not familiar with this plugin, however, this being said, you can preload any image in the mentioned
Preload Requests in Performance>General settings>User Experience section.
With this option, you can also preload other assets, and especially any fonts that may cause render-blocking issues.
I hope this helps!
Thanks!Marko Vasiljevic
KeymasterHello,
Thank you for reaching out and I am happy to help!
First of all, thank you for your support and for the amazing review you posted on wp.org
To answer your question, in W3 Total Cache, you can enable Preload Requests in Performance>General settings>User Experience section. Please note that this is a Pro feature. Once enabled, you can go to Peeformance>User Experience, and add the URL of the image you wish to preload in the Preload Images: field.
Save all settings and purge the cache and that is it! Can you also please share which plugin you are using currently for this?
Thanks!Marko Vasiljevic
KeymasterHello Joe,
Thank you for reaching out and I am happy to help!
Can you please confirm that you were able to set up the CDN in the W3 Total Cache once the Total Upkeep was disabled, once the CDN was up and running you are able to re-activate Total Upkeep, and everything is now working g as expected?
Thanks!Marko Vasiljevic
KeymasterHello Frank,
Thank you for reaching out and I am happy to help!
As this is a public forum, please reach out to us directly via the W3 Total Cache support channel via the plugin in Performance>Support>Billing, and provide the information there so we can share the license key and provide assistance with this!
Thanks!Marko Vasiljevic
KeymasterHello Terry,
Thank you for reaching out and I am happy to help!
The problem is that the license key is still associated with the previous W3 Total Cache installation.
I’ve reset the active URL. I’ve also removed the transaction information as this is a public forum.
Enter the license key in Performance>General settings, Licensing sub-box, license field, verify the license with the “verify license button” and save all settings.W3 Total Cache Pro should be active after these steps!
Let me know if this helps!
Thanks!
Marko Vasiljevic
KeymasterHello,
Thank you for reaching out and I am happy to help!
Something is blocking the Ajax requests. The way this works is that W3 Total Cache is calling Ajax requests over and over and something from the server or some other plugin may be blocking them.
What you can do is to try disabling security plugins and see if that helps. As you can see in the dev tools, network tab when the setup guide is running there is a 404 Ajax requests, and that is the confirmation that something is blocking those requests to the requests limit was hit on the server. This is why you are getting the “Could not update the configuration” error.
The problem can also be a self-signed certificate, fancy permalinks are disabled, or the the php-curl was missingThanks!
Marko Vasiljevic
KeymasterHello
Thank you for reaching out and I am happy to answer
We replied to your email on Mar 12 2024 and the issue was fixed and we never got a reply from you via the W3 Total Cache support channel.
Please check your email, and reply to the email chain.
Thanks!May 3, 2024 at 10:55 am in reply to: Did I decline to let W3 use my data or decline the terms of agreement? #130861Marko Vasiljevic
KeymasterHello
Thank you for reaching out and I am happy to help!
This is for the “Anonymously track usage to improve product quality” option that you can enable/disable in Performance>General Settings>Miscellaneous section of the plugin.
To answer your question, W3 Total Cache will still run normally on your website, the only thing is that you are not sharing the usage of the plugin, like the options used etc.
I hope this helps!Thanks!
Marko Vasiljevic
KeymasterHello,
Thank you for reaching out and I am happy to help!
First, we should confirm which option may be causing the issue. 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!
Marko Vasiljevic
KeymasterHello 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!Marko Vasiljevic
KeymasterHello 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!
Marko Vasiljevic
KeymasterHello 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.
ThanksMarko Vasiljevic
KeymasterHello 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!
Marko Vasiljevic
KeymasterHello,
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!
Marko Vasiljevic
KeymasterHello,
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!Marko Vasiljevic
KeymasterHello,
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!
Marko Vasiljevic
KeymasterHello,
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!
March 22, 2024 at 1:09 pm in reply to: Image Duplication Issue with W3 Total Cache on Thrive Themes WordPress Site #128537Marko Vasiljevic
KeymasterHello 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!Marko Vasiljevic
KeymasterHello 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!Marko Vasiljevic
KeymasterHello 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!
March 15, 2024 at 11:27 am in reply to: The problem with issuing webp using WebP Converter (LEMP) #127724Marko Vasiljevic
KeymasterHello 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!
March 14, 2024 at 1:27 pm in reply to: The problem with issuing webp using WebP Converter (LEMP) #127700Marko Vasiljevic
KeymasterHello 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!
Marko Vasiljevic
KeymasterHello 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!March 14, 2024 at 10:52 am in reply to: The problem with issuing webp using WebP Converter (LEMP) #127692Marko Vasiljevic
KeymasterHello 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!March 12, 2024 at 1:34 pm in reply to: Unable to Activate W3 Total Cache Plugin after switching to WP Single Site #127453Marko Vasiljevic
KeymasterHello,
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!March 11, 2024 at 11:27 am in reply to: Unable to Activate W3 Total Cache Plugin after switching to WP Single Site #127330Marko Vasiljevic
KeymasterHello 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!
Marko Vasiljevic
KeymasterHello 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.Marko Vasiljevic
KeymasterHello 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!Marko Vasiljevic
KeymasterHey 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!Marko Vasiljevic
KeymasterHello,
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!Marko Vasiljevic
KeymasterHello 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!
- This reply was modified 1 year, 7 months ago by
Marko Vasiljevic.
Marko Vasiljevic
KeymasterHello
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-image
to Perforamnce>User Experience>Exclude words section.
Make sure to save all settings and purge the cache.I hope this helps!
Thanks!
Marko Vasiljevic
KeymasterHello,
We’ve received your reply.
Thanks! Can we please continue the correspondence via the support channel (email) to avoid duplicating the answers?
Thanks! - This reply was modified 1 year, 7 months ago by
- AuthorPosts