Marko Vasiljevic

Hello Daniel,

Thank you for the information.
As I can see the images you converted are now being served as webp:

This means that the Image conversion is working as expected. The fact that ImageMagic supports webp means that other formats of the image are also converted.
Enabling the Image Service Extension also adds the Total Cache Image Service under Media in the WordPress admin menu, which allows for bulk conversions or reversions of the entire Media Library at once. Use the Convert All or Revert All buttons in the Tools section to manage your WebP image conversions for the entire Media Library at once.
You can do this in Performance>Extensions>Image Service settings:
Thanks!

Hello Daniel,

Thank you for reaching out and I am happy to assist you with this.
As I can ee images are converted:
https://blendup.art/wp-content/uploads/2021/12/significado_tatuagem_cruz_malta_7-768×613.webp
I can see that you are using Cloudflare. Have you purged the W3TC and Cloudflare cache and have you checked the Cloudflare Browser Cache TTL?
Also, If you find that your original image has been converted to WebP, but other image sizes are missing WebP versions, you may need to double-check that your WordPress environment supports the WebP format.

While the original image is converted via our API service, the different sizes (e.g. Large, Medium, Thumbnail) are created by your own server. For this, you must have WordPress 5.8 and the appropriate libGD or ImageMagick package available on your server.

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.

I hope this helps!
Thanks!

Hello Stephanie,

I am sorry about the issue you are experiencing with W3 Total Cache and I am happy to assist you with this.
I’ve replied to your email and provided instructions on how to troubleshoot the problem.
Please continue the correspondence there so we can avoid duplicating the answers.
Thanks!

Hello Juha,

Thank you for reaching out and I am happy to assist you with his.
The pages are preloaded in W3 Total Cache according to the sitemap that needs to be added to Performance>Page Cache>Cache Preload>Sitemap URL:
If the pages are in the sitemap, those pages will be preloaded as well.

I hope this helps!
Thanks!

Hello,

I am sorry about the issue you are experiencing with W3 Total Cache and I am happy to assist you with this.
I’ve checked your website and as I can see you are using some other caching plugin.
Can you please confirm you were not using both plugins at the same time?
YOu also stated that you were using the basic settings. Can you please share which settings were enabled in W3 Total Cache?
Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
Can you please disable minify in W3 Total Cache Performance>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.
Thanks!

Hello Malcolm,

Thank you for reaching out and I am happy to assist you with this.
The website you are referring to is not hosted by W3 Total Cache as W3 Total Cache is an optimization plugin and not a hosting service.
The website you are inquiring about is hosted on DigitalOcean, LLC
Thank you!

Hello,

Thank you for reaching out and I am happy to assist you with this.
Unfortunately, no. The problem, in this case, is that the Global API is used to authorize Cloudflare with W3 Total Cache, which contains all sites created under a single account.
We are working on improving this and adding the ability to use API token with required permissions per zone/domain, that way it wouldn’t have permissions to view/edit others from the Cloudflare account.
Please make sure to follow the progress of the GitHub issue, and feel free to leave any comments which you may find helpful.
Thanks!

Hello,

Thank you for reaching out and for your interest in the W3 Total Cache Pro license.
Yes, we do have a discount for a bulk of 5 and 10 activations, for any specific questions regarding the license please drop us a note directly via the plugin in Performance>Support, or via the website support forum.
As for the Pro features, please check out this article for all the Pro features and their description.
Thanks!

Hello Rob,

You are most welcome and I am glad the webp conversion procedure is more clear now.
As for your question regarding the ImageMagic, I’ll try to explain.
One image conversion equals one request to the API server to convert the image. Depending on the website, a single image can have the original image, and 3-6 resized images (thumbnails) so that can multiply a single request to API server 6 times. More requests mean slower conversion and that’s where Image Magic kicks in.
I hope this explains the reason for this and let me know if you have any other questions.
Thanks!

Hello,

Thank you for the feedback.

There are a couple of things that you can try.
Add the following rule to the top of your .htaccess file:

# FONT CORS
<IfModule mod_headers.c>
  <FilesMatch "\.(ttf|otf|eot|woff|woff2)$">
    Header set Access-Control-Allow-Origin "*"
  </FilesMatch>
</IfModule>
# END FONT CORS

Make sure that NGINX Bypass Apache for static files
You can also add the rule to your ngix:

location ~* \.(ttf|otf|eot|woff|woff2)$ {
    add_header Access-Control-Allow-Origin *;
}

As for your other question regarding the custom files, try adding the full path of the file and see if it uploaded, for example,
/wp-content/fonts/some-font.woff

Let me know if this helps!

Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
Can you please share more information about the issue you are experiencing?
1. Which CDN Provider you are using?
2. Which files are affected by the CORS problem?
3. Is your website on Apache, Nginx, or Nginx+Apache?
4. Can you please share your website URL?

Thanks!

Hello Rob,

Thank you for reaching out and for using W3 Total Cache for webp conversion.
As I can see your images are being served from the CND
If you opened the image in the new tab:
https://cdn.robstead.co.uk/wp-content/uploads/2021/06/37.-Susan20201029_05-1024×1024.jpg
The image is loading and the content type is jpeg
If you change the extension to .webp:
https://cdn.robstead.co.uk/wp-content/uploads/2021/06/37.-Susan20201029_05-1024×1024.webp
The CDN will state that the file is missing.
If I change the URL to your DNS:
https://www.robstead.co.uk/wp-content/uploads/2021/06/37.-Susan20201029_05-1024×1024.webp
This will throw the 404 not found.
All of the above means that the images are not converted so I would suggest reaching out to yoru hosting provider and checking if the ImageMagick is enabled and allowing webp.
Thanks!

Hello,

Thank you very much for reaching out and for your efforts in translating the W3 Total Cache.
Please drop us a note via the plugin in Performance>Support, or via the website contact form.
Thanks!

Hello Matrin,

I am sorry about the issue you are experiencing and I am happy to assist you with this.
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server while acting as a gateway or proxy, received an invalid response from the upstream server.
YOu’ve mentioned that the server capacity is reached, so you may want to check the /cache/ folder and delete the content (don’t worry, the files will be cached again) if W3 Total Cache is active
Make sure that if you are caching to disk to disable Object Caching and Databased Caching as it’s not recommended to use those options if caching to disk.
Every 500 error should be logged so I would advise enabling wp_debug and checking the error log once, and if the error occurs again.

Hello John,

Thank you for your feedback.
As I can see the only problem is with the video on the Home page. I’ve checked the source and I can see that it should be style=”width:100% so that is strange indeed.
I’ve also checked the website bypassing the cache and it does not have any difference.
Have you tried disabling W3TC to confirm if the problem is related to our plugin?
Thanks!

Hello Libby,

Thank you for the information.
I’ve checked your website and it’s loading just fine and the testing results look good.

Can you please share what you are seeing?
Thanks!

Hello Michael,

Thank you for reaching out and I am happy to assist you with this.
1. Yes, W3 Total Cache does work with IMH nginx reverse proxy caching.
2. IMH Nginx is controlled in cPanel, however, it cannot be purged via W3 Total Cache.
3. I am not familiar with the plugin you are referring to, so Ic can not suggest it for this use case.

This being said, if you want to purge the IMH Nginx proxy, you need to do this via the IMH Control panel
I’ve opened a Github issue for this and we may add the ability to do this via W3TC.

Thank you!

Hello Brian,

Thank you for the information and I am glad everything is working as expected.
Yes, you can backup the settings:
1. Download the .json file in Performance>General Settings, scroll down to Import/Export settings and click on Download to Export Configuration.
2. You can make a backup of wp-content/w3tc-config/master.php

Thank you!

Hello Brian,

Thank you for reaching out and I am sorry about the issue you are experiencing with W3 Total Cache.

This is a very strange issue to be related to W3 Total Cache, and I am not quite sure (the first time I am seeing this kind of issue) what may be causing this.
Potentially, some cookie was cached in the browser or the Page Caching was not disabled for logged-in users.
I would recommend removing the plugin and re-install:
3. Check .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.
1. 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/ (the folder you renamed)
2. 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.
3. Go to your wp dashboard and re-install W3 Total Cache

Once the plugin is re-installed make sure that when you test the behavior after enabling the settings one by one, and make sure that caching is not enabled for logged-in users.

Let me know if this helps!

Thanks!