Forum Replies Created
-
Posts
-
Hello Mark,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
WE’ve received your email via the support channel and replied to it so please continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Aninda,
Thank you for your inquiry and I am happy to assist you with this.
Are you trying to setup FSD CDN or just serving the static assets from the AWS?
Can you please share the screenshot of the settings in Performance>CDN>Configuration: Objects?
Thanks!Hello Kiem,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
Can you please share the screenshot or more detailed information about where you are seeing the error message?
A screenshot would be great.
Thanks!Hello Michael,
I am sorry about the issue you are experiencing with mixed content and I am happy to assist you with this.
I would recommend completely removing and re-installing W3 Total Cache, including all residual files:
1. Purge Cache
2. Deactivate and Delete Plugin
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 leftover in your .htaccess file after deleting the plugin.
4. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– dbcache.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content (if exists)
5. 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.
6. Go to your wp dashboard and re-install W3 Total CacheOnce enabled, Enable the settings one by one, save all settings and purge the cache after each setting is enabled, and make sure to check your website.
Also in Page Cache, make sure that the option “Cache SSL (HTTPS) requests” is enabled
I hope this helps!Hello Mitchell,
Thank you for the information.
I’ve checked your website and as I can see the website is accessible as well as the https://custom-tiles.com/wp-admin/ and W3 Total Cache is active on your website.<!-- Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/ Page Caching using disk: enhanced Content Delivery Network via N/A Lazy Loading Minified using disk Served from: custom-tiles.com @ 2021-02-24 19:55:39 by W3 Total Cache -->Can you please confirm that you are still experiencing the issue?
Thanks!Hello Mitchell,
The provided steps need to be taken first in order to access your dashboard. So to access your dashboard you need to manually delete those files from the server following the steps provided.
Once those files are deleted, you can then access the dashboard and re-install W3TC and making sure that OC and DB Cache are not enabled.
What hosting support did is most probably disabled the plugin by renaming it in the wp-content/plugins/
The problem is that the settings you enabled are still in wp-content/w3tc-config/master.php and the cached files are in the /cache/ folder.
Thanks!Hello Mitchell,
Simple deactivation of the plugin is not sufficient.
Please follow the steps provided and completely remove everything related to W3 Total Cache.
Once that’s done, install W3 Total Cache without any leftover files remaining and make sure not to use Object Caching and Database caching if on shared hosting and if caching to Disk.
Thanks!Hello Mitchell,
I am sorry about the issue you are experiencing and I am happy to assist you with this.
Can you please completely remove W3 Total Cache and re-install it and once the plugin is reinstalled make sure that Object Cache and Database Cache are not enabled in the General settings especially if on shared hosting and if caching to disk and see if the issue persists:
1. 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.
2. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– dbcache.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, and as I mentioned, make sure that Object Caching and Database Caching are disabled if on shared hosting plan and if caching to disk.
Thanks!Hello Nadia,
Thank you for your question and I am happy to assist you with this.
We received your email via the support channel so please continue the correspondence there so we can avoid duplicating the answers.
Thanks!Hello Hannah,
Thank you for your inquiry and I m happy to assist you with this.
In order to be able to use the Opcode caching method (APC/APCu for example ), you need to make sure that the PHP extension is installed on your server. Only then you will be able to choose it from the Page Cache Method: list.
However, I would advise keeping the Page Cache Method: on Disk: Enhanced as it providing the best results when it comes to Page Caching.
Thanks!Hallo Maarten,
Thank you for your inquiry and I am happy to assist you with this.
As you can see in the gtmetrix report The total size of your website is 10.7MB and 9.04MB or that are images. Gtmetrix suggests that you need to optimize images, which W3 Total Cache cannot do. So the bottleneck of your website performance is your images.
Gtmertix also suggests using CDN to serve static content and I would suggest Stackpath CDN as it’s easy to set up and it offers the best performance.
As for eliminating render-blocking css, W3 Total Cache does have an option “eliminate render-blocking CSS by moving it to HTTP body” however that option is available after updating to Pro.
Thanks!Hello Steven,
Thank you for your inquiry and I am happy to assist you with this.
The notification you are seeing suggests that the CDN is not enabled in Performance>General settings:
So make sure that the CDN option is enabled and Stackath is selected under the CDN type, save all settings, and purge the cache.
Also, make sure to check this article about how to setup Stackpath with W3 Total Cache.
Thanks!Hello Tony,
Thank you for the information and I am sorry that the issue is still occurring.
Please check this article about the wp debug and error logs. From what you’re saying the uploads times out for some reason so you should check if there are any errors in the log, wp-debug or any PHP errors.
Thanks!Hello Emmanuel,
As I’ve already replied via the support channel, to access the premium support for W3 Total Cache, please navigate to your wp dashboard, Performance>Support, and purchase the Performance Audit solution.
After that, we will provide you further instructions in the Premium support email chain.
Thanks!
Hello Tony,
Thank you for the info.
Can you please check your error log?
If the error.log is not showing anything there is a possibility that the upload timed-out and it takes too much time for your host to upload file and timeout are set to lower value to process responses on your host.
So, in this case, you should increase it.
There is also a possibility that Wordfence or some other security plugin or firewall could be blocking W3TC from accessing too many directories/files at once.
Thanks!Hello Joshua,
I’ve inspected your website and I can see that the calendar is not loaded (infinity loading). After checking the Console errors I saw a 404 error for https://headshotsla.com/?wc-ajax=wc_bookings_find_booked_day_blocks&product_id=1046777&wc-ajax=wc_bookings_find_booked_day_blocks&security=15c6cabcbb&min_date=2021-02-15&max_date=2021-03-22
This is for page https://headshotsla.com/product/8-look-8-retouch/
Can you please disable the W3TC settings one by one in Performance>General settings, save all settings and purge the cache after each setting is disabled, and see which setting might be causing this.
Thanks!Hello Tony,
Thank you for the information and I am glad you managed to set up the CDN successfully.
Check if you have the information about the Unsuccessful transfer queue, click the button near it and try to re-upload files.
if works – it’s a temporary issue linked to server resources.
Also, make sure to check your master.php file. If cdn.force.rewrite”: “1 should be avoided in the long-term since it causes continuous reuploads of the same files. Just change it to cdn. force.rewrite”: “0
Thanks!Hello Matteo,
Thank you for the information.
In the July 2020 update, we’ve fixed the following:- Fixed Take “Accepted Query Strings” into account when “Cache query strings” enabled
- Fixed the typo in the variable for lazy loading
- Added lazy load Google Maps reference to the general settings page
- Added Support background-image: together with background: for lazy loading
So there is nothing that would suggest the issue you are referring to except if you are possibly caching a query string.
As I can see you are using Page Cache with Memcached. I would suggest switching to Disk: Enhanced, as it’s more performant than any other caching method when it comes to page caching, and see if the issue persists.
Thanks!Hello Tony,
The settings are saved in wp-content/w3tc-config/master.php Make sure to make a backup of the mentioned file.
YOu can manually replace the lines around line 572 (depending on the configuration) with default values:"cdn.azure.user": "", "cdn.azure.key": "", "cdn.azure.container": "", "cdn.azure.cname": [], "cdn.azure.ssl": "auto",Once you save the changes, go to Performance Dashboard and re-enable CDN (make sure CDN is disabled before this), and select Microsoft Azure Storage from the CDN type menu.
Once you go to Performance>CDN the values should be default.
Thanks!Hello Matteo
The most likely issue is that there are leftover files of the other caching plugin you are using and therefore is making a conflict with W3 Total Cache.
We cannot assist you in this case unless you completely remove the other plugins and make sure there are no leftover files.
Alternatively, we can offer you our premium support in Performance>Support.
Thanks!Hello Mattei,
It would be great if you could share your website URL.
The Cron schedule for W3TC is not correct. I am not able to see the screenshot at the moment.
There is a possibility of a conflict so you should make sure that you do not have any other caching solution installed like server-side caching or any other caching plugin and make sure to disable it.
Thanks!Hello Tony,
I am sorry about the issue you are experiencing with setting up Azure CDN with W3 Total Cache and I am happy to assist you with this.
The replace hostname should be automatically populated after connecting with the Account key as you can see in the image below:
I would recommend checking out this article which explains the proper setup of Azure CDN with W3 Total Cache.
Please let me know if you have any other questions.
Thanks!Hello Joshua,
Thank you for your inquiry and I am happy to assist you with this.
As I can see from the tests you have a lot of render-blocking CSS. This means that you should eliminate render-blocking CSS and that feature is available in W3 Total Cache after upgrading to Pro.
So yes in this case you need the Pro version for the plugin. As for our premium support, you can purchase Plugin Configuration or Performance Audit solution via the plugin in Performance>Support.
Thanks!Hello Matteo,
I am sorry about the issue you are experiencing with corn schedules and I am happy to assist you with this.
As you can see W3TC does have a few events scheduled, depending on features enabled in the General settings.
Also, as I can see in the screenshot WP_CRON_LOCK_TIMEOUT constant is defined to 60sWhen WordPress is loaded, it checks to see if a cron job is running (if cron is locked). If cron is not locked, it will try to create a lock – if the lock timeout has not been reached, no lock can be acquired and cron will not run.
The constant is limiting the W3TC schedules and therefore those are not executed. You should either change the limit or comment out the WP_CRON_LOCK_TIMEOUT line in wp-config.
I hope this helps!
Thanks!Hello Stien,
I am sorry about the issue you are experiencing and I’m happy to assist you with this.
We’ve also received the email via the support channel, and I asked you some follow-up questions. We can continue the correspondence there since you are a Pro user.
IS REST API cache enabled in Perfomrance>Page Cache>REST API?
I can see that you’ve set up Full site delivery, however, you are also using the CDN with the URL rewrite, so in this case, you should disable the CDN in Performance>General settings and only use FSD CDN.
The pages are cached once visited. So if you wish to preload the pages you can use Cache Preload in Performance>Page cache and Automatically prime the page cache. There you will also see the option Preload the post cache upon publish events which does exactly that. since the Cache Preload is triggered by the page view and sometimes wp cron is not very reliable, I would advise using the default settings in Cache Preload and possibly set a custom cronjob for page visit on your server, for example, every 5-10 mins or better yet use wp-cli.
Logging is available in wp cli so instead of calling wp cron via crontab – you should call it directly via
wp w3-total-cache pgcache_prime
and track the output which pages / sitemap positions are primed by script.
Thanks!Hello Julieta,
As Jesse stated You can reach out to our billing team privately directly from your WordPress Dashboard, in the Performance > Support menu, or by using this contact form, and we will be more than happy to assist you with this.
Thanks!Hello KLC,
I can see that you are using Cloudflare and Autoptimize, however, I do not see traces of W3 Total Cache.
If you are using W3 Total Cache, make sure that Minify is disabled since you are also using AO and Cloudflare. Also, make sure that Cloudflare Minify is disabled since AO is handling this.
NOw when it comes to Google Page speed suggestions, They are related to the plugin you are using to Minify the assets, so in order to eliminate render-blocking resources, you need to address this to Autoptimize support.
Removing unused JS/CSS cannot be done by any plugin. This is because the theme you are using and the plugins you are using are loading js/CSS files on all pages and not just the pages intended.
Also, you might want to pay a bit more and use Stackpath Full site delivery instead of the Cloudflare free plan. I’ve also found this article which may help you with the configuration.
Thanks!Hello Antonello,
Please drop us a note via the plugin in Peformance>Support>Billing or secure support request on w3-edge.com as Jesse suggested so we can send you the requested invoices.
Thanks!Hello Mike,
Thank you for your question and I am happy to assist you with this.
As I’ve already replied in wp.org topic, we cannot troubleshoot if we don’t see the problem.
Can you please share the Performance>Minify settings (a screenshot would be great) and check the nginx cond if it contains necessary rules provided in Perfomrance>Install.
And please let me know where you wish to continue the correspondence so we can avoid duplicating the answers.
Thanks!Hello eddyeten,
I’ve checked your website (the provided URL) and I don’t see that W3 Total Cache is installed.
Can you please confirm that W3TC is installed and configured and also provide the screenshots of the settings or the master.php file?Thanks!
Hello Carolee,
You can use User Agent Groups for this. In Performance>Cache Groups>Manage User Agent Groups, you can specify the group of user agents by specifying names in the user agents field. Assign a set of user agents to use a specific theme, redirect them to another domain or if an existing mobile plugin is active, create user agent groups to ensure that a unique cache is created for each user agent group. Drag and drop groups into order (if needed) to determine their priority (top -> down).
So in your case, enable the group, select pass-through in the Theme drop-down, and add the URL in Redirect users to: field that is required by the redirect plugin.
Make sure to save all settings and purge the cache after the changes are made
I hope this helps!
Thanks!Hello Nicola,
Thank you for your patience.
As it appears you are correct. The delete_option is not running due to the $extras parameter being empty.
I’ve opened a GitHub issue on your behalf in our Github repository. Please make sure to check the progress of the issue regularly and add more information if needed.
Thank you!Hello Nicola,
Thank you for providing the info and detailed explanation.
Let me test this and get back to you to see if I can replicate this and if the provided code works without any issues.
Once again thank you for provided details and your patience.Hello Franko,
Thank you for your inquiry and I am happy to answer.
The Pro license unlocks the additional W3 Total Cache features like Eliminate render-blocking CSS by moving it to HTML body, REST API Caching, FSD CDN, etc. The Plugin Configuration solution or Performance Audit does not include the Pro license, so the Pro license needs to be acquired separately.
To check the prices, please go to Performance>Support in your wp-admin dashboard (check the screenshot below)
Thank you!Hello Nicola,
I am sorry about the issue you are experiencing with clearing the w3tc_minify option from the database.
I need to check this and try to replicate and I’ll get back to you as soon as investigate this more.
Thank you for your patience.Hello Nicola,
Thank you for your inquiry and I am happy to assist you with this.
Browsers that support brotli send br along with gzip in the accept-encoding request header. If brotli is enabled on your web server, you will get a response in brotli compressed format.
This means to me that if the client supports both, brotli is preferred over gzip.
At the moment I can see that all minified files are “brotlied”
If convenient, can you please share the exact changes you made inMinify_Environment.phpand also, are both brotli and gzip enabled in Performance>Browser Cache>CSS&JS and if so, you should disable gzip if you are using brotli for those files.
Thank you!Hello Dominique
Thank you for the information.
It seems that jquery-migrate is necessary and custom.unified.js?ver=4.8.1:51 is dependable on it so you should keep that option disabled.
I am glad to know the issue is resolved!
Thanks!Hello Dominique,
As Jesse stated we are unable to replicate the issue on WP 5.6 Divi 4.8.1 and W3TC 2.0.1.
Can you please disable the settings one by one in Performance>General Settings, save all settings and purge the cache after each setting is disabled, and see which one might be causing the issue.
Please let us know the results so we can assist you more with this.
Thanks!Hello Chris,
Thank you for the information provided.
As I’ve already answered you in wp.org and this a duplicate post please make sure to check the wp.org topic:
https://wordpress.org/support/topic/prevent-caching-with-gravityforms/#post-13868293For your convenience this was my reply:
You should use the correct groups and each group should specify
{key}={value}
Depending on what key you are using, that should look like{key}='{“strict”:”1″,”thirdparty”:”0″,”advanced”:”0″}’
So you should replace {key} with the actual cookie name.And don’t forget to enable all the checkboxes (enable and cache)
Once again as the cookies are cached and may change depending on a value, you should exclude those pages from being cached to avoid this.
This is simply how cache works. I hope this helps!
Thanks!Hello Gregorio,
Thank you for your inquiry.
There is no known incompatibility with JWT authentication and since the Page Cache should always be disabled for logged in users REST API caching will not be performed in this case.
The_embedparameter indicates to the server that the response should include these embedded resources.
So for example, /wp/v2/posts?_embed=author,wp:term will only embed the post’s author and the lists of terms associated with the post and it will be cached if REST API cache is enabled.
For more details on what is actually cached, you can use Statistic in Performance>Statistic and Under the PHP requests section, you should see the Cache Fill option which you can then open to see /wp-json.
Thanks!
