Marko Vasiljevic

Hello Arslan,

Thank you for reaching out and I am happy to help!
I’ve replied to your email via the W3 Total Cache support channel and provided the requested invoice.
Please check your email
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
I’ve sent you all the requested information via the W3 Total Cache support channel
Please check your email and continue any correspondence there so we can avoid duplicating the answers
Thanks!

Hello,

Thank you for reaching out and I am happy to help!
Just to confirm, you do not want to use Access key ID and Secret key: to connect the AWS with the W3 Total Cache?
Can you please confirm this and let me know what would you expect to be using when connecting to the CDN?
Thanks!

Hello Bilal,

Thank you for reaching out and I am happy to help!
TBT measures the total amount of time that a page is blocked from responding to user input, such as mouse clicks, screen taps, or keyboard presses. The sum is calculated by adding the blocking portion of all long tasks between First Contentful Paint and Time to Interactive. Any task that executes for more than 50 ms is a long task. The amount of time after 50 ms is the blocking portion. For example, if Lighthouse detects a 70 ms long task, the blocking portion would be 20 ms.
Eliminating render-blocking resources will yield the biggest improvement and in the W3 Total Cache you need to Minify the JS and CSS, make sure to select eliminate render-blocking CSS and deffer minified JS.
Please check the documentation below for more details:

W3 Total Cache: Minify Cache Settings Guide

Eliminate Render-Blocking CSS with W3 Total Cache Pro

I hope this helps!

Thanks!

Hello Meghann,

Thank you for reaching out and I am happy to help!
Just to confirm, when you made those changes in the W3 Total Cache you saw that the website is active in the W3TC_PRO_DEV_MODE

Thanks!

Hello Doug,

Thank you for reaching out and I am happy to help!
I was not able to replicate this in the W3 Total Cache setups and I’ve checked the code and there are no syntax issues.
Can you please download the config file in Performance>General settings, scroll down to Import Export and export the json
1. 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.
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 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 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.
4. Go to your wp dashboard and re-install W3 Total Cache

Hello Mark
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 @

Thank you for your patience.

Do we need to locate all Ajax actions in our plugin?

Thanks!

Hello,

Thank you for reaching out and I am happy to help!
We’ve received and replied to your email via the W3 Total Cache support channel.
Please continue the correspondence there so we can avoid duplicating the answers
Thanks!

Hello Florian,

Thank you for reaching out and I am happy to help!
I’ve sent the requested invoice via the W3 Total Cache support channel to the email address you provided
Please check your email and if you have any other questions, please reply to that mail so we can avoid duplicating the answers
Thanks!

Hello Jackie,

I will reply to this topic and close the other one so we can avoid duplicating the answers.
I am not familiar with Klaviyo and as I mentioned before, they do not have sufficient documentation that I can check and provide assistance as I am unsure how it works and what is the actual problem
Have you by any chance tried reaching out to their support, and check what are the recommendations with the optimization plugins?
Thanks!

Hello,

We’ll be releasing the fix soon so you can wait for that one
The file is in wp-content/plugins/w3-total-cache/Root_Environment.php

Line 224 change if ( ! emtpy( $license_key ) ) { to if ( ! empty( $license_key ) ) {

Let me know if this helps!
Thanks!

Hello Doug,

Thank you for reaching out and I am happy to help!
We already have a fix in place for this:
https://github.com/BoldGrid/w3-total-cache/commit/bbaa490e8bfa0708f198760cd052a656ac4b47ef

Just re-download the latest W3 Total Cache version, make the changes manually or check the next patch release

I hope this helps!

Thanks!

Hello

Thank you for reaching out and I am happy to help!
Can you please apply this fix and change the line of the code in the plugin files: https://github.com/BoldGrid/w3-total-cache/commit/bbaa490e8bfa0708f198760cd052a656ac4b47ef

Once applied, please reload the W3 Total Cache Dashboard and try to disable the W3 Total Cache.

Thanks!

Hello Belle

Thank you for reaching out and I am happy to help!
Can you please apply this fix and change the line of the code in the plugin files: https://github.com/BoldGrid/w3-total-cache/commit/bbaa490e8bfa0708f198760cd052a656ac4b47ef

Once applied, please reload the W3 Total Cache Dashboard and try to disable the W3 Total Cache.

Thanks!

Hello Peter

Thank you for reaching out and I am happy to help!
What you see in the folder are the expired cache files. This option in the W3 Total Cache is set in Perormance>Page Cache>Advanced> Maximum lifetime of cache objects:
Once the cache is expired, the _old file is created and this indicates that the cached file is served, however, if the page was not visited, no new file is created so the older cached version is served.

Have you tried increasing the Maximum lifetime of cache objects and also please try using Cache Preload to always have a fresh cached page available

Thanks!

Hello Alexia,

Thank you for reaching out and I am happy to help!

This is related to the Memcached installation on your server, to be able to use it in the W3 Total Cache
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.

Let me know if this helps!

Hello Riccardo,

Thank you for reaching out and I am happy to help!
Can you please provide a piece of evidence for this? Have you configured the W3 Total Cache accordingly, following the Google Page speed recommendations and which aspect of the GPS score was lowered after the configuration?
Thanks!

Hello Tony,

Thank you for reaching out and I am happy to help!
Can you please try to manually remove the W3 Total Cache files and folders? It seems that the environment you are on has some limitations
1. 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.
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 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 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.
4. Go to your wp dashboard and re-install W3 Total Cache

Let me know if this helps!

Thanks!

Pozdrav Dusane!

Thank you for reaching out and I am happy to help!
Currently, we are not offering any trial periods for the W3 Total Cache Pro. You can set up a community version and check which Pro settings are needed.
Since we are offering a 30-day money-back guarantee, you can purchase the pro license which is currently 50% off and if you are not satisfied with the product, reach out to us in Performance>Support>Biling or let us know if we can be of any assistance with the configuration
I hope this helps!

Thanks!