Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #166401 Reply
    Robert Cassidy
    Guest

    W3 Total Cache cannot be completely deleted. I have tried, including re-installing and disabling everything then removing all files when prompted before deletion. So, shows up on View Page Sourse of my website. Worse, when I change my style.css file, it will not reflect the change, when I open my website. I have tried Chrome, Firefox, Opera and cleared their browser cache, more than once, cleared server cache, purged cloudflare cache, but no luck, same ol’ website style and layout. Many on Google complain about the same problem that it cannot be completely deleted from WordPress.

    #166434 Reply

    Hello Robert,

    Thank you for reaching out, and I am happy to help!
    As with any other plugin, W3 Total Cache can be deleted via the plugins section in the WP-Admin area. W3 Total Cache is a robust plugin as it offers a lot of possibilities for optimization. This being said, there are a lot of files; however, the W3TC is not responsible if the files are not deleted from the server when removing the plugin. What happens is that the hosting restrictions, especially when it comes to permissions, may cause some residual files to remain on the server. I assure you, the W3TC, when being removed, is like any other plugin; however, you can always do this manually

    As for the other question regarding the CSS issue you are experiencing, this is why the W3 Total Cache is the best optimization solution, as it offers something called Cache-busting
    The option “Prevent caching of objects after settings change” in Performance>Browser Cache can be enabled for individual files, and it can be enabled for all CSS and JS files under the CSS&JS section in the Browser Cache. Since the suggested expiration for the static files is 1 year, the “cache-busting” can be achieved with the Prevent caching of objects after settings change, which adds the query string to the file, and once updated, the browser will naturally fetch a new version since it’s not the same file
    For example, if the option is enabled on the plugin that has a file https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css the query string will be added:

    https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x1234

    If the content of the CSS file is changed, and the option “Prevent caching of objects after settings change” is enabled for CSS&JS files, all you have to do is to update the media query string using the “Update media query string” button in the Performance>Browser Cache at the top of the page, which will then update the string and force the plugin to fetch the new version:

    https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x4231

    After updating the query string, you also need to purge the cache.

    I hope this helps!

    Thanks!

    #166435 Reply

    Hello Robert,

    Thank you for reaching out, and I am happy to help!
    As with any other plugin, W3 Total Cache can be deleted via the plugins section in the WP-Admin area. W3 Total Cache is a robust plugin as it offers a lot of possibilities for optimization. This being said, there are a lot of files; however, the W3TC is not responsible if the files are not deleted from the server when removing the plugin. What happens is that the hosting restrictions, especially when it comes to permissions, may cause some residual files to remain on the server. I assure you, the W3TC, when being removed, is like any other plugin; however, you can always do this manually

    As for the other question regarding the CSS issue you are experiencing, this is why the W3 Total Cache is the best optimization solution, as it offers something called Cache-busting
    The option “Prevent caching of objects after settings change” in Performance>Browser Cache can be enabled for individual files, and it can be enabled for all CSS and JS files under the CSS&JS section in the Browser Cache. Since the suggested expiration for the static files is 1 year, the “cache-busting” can be achieved with the Prevent caching of objects after settings change, which adds the query string to the file, and once updated, the browser will naturally fetch a new version since it’s not the same file
    For example, if the option is enabled on the plugin that has a file https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css the query string will be added:

    https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x1234

    If the content of the CSS file is changed, and the option “Prevent caching of objects after settings change” is enabled for CSS&JS files, all you have to do is to update the media query string using the “Update media query string” button in the Performance>Browser Cache at the top of the page, which will then update the string and force the plugin to fetch the new version:

    https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x4231

    After updating the query string, you also need to purge the cache.

    I hope this helps!

    Thanks!

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: Reply #166434 in W3 Total Cache cannot be completely deleted
Your information: