Forum Replies Created
- AuthorPosts
- Marko VasiljevicKeymaster
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!Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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!February 10, 2021 at 8:22 am in reply to: I would like to cancel my subscription to Total Cache #33666Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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!February 4, 2021 at 8:55 am in reply to: Not generating minified css / js files but referencing them in links #33514Marko VasiljevicKeymasterHello 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!February 2, 2021 at 10:57 am in reply to: Help optimizing my site with W3 Total Cache Premium #33455Marko VasiljevicKeymasterHello 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!
Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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.Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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.Marko VasiljevicKeymasterHello 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.php
and 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!January 19, 2021 at 11:46 am in reply to: [Resolved] JS error Cannot read property ‘concat’ making crashing my Divi blog #33072Marko VasiljevicKeymasterHello 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!January 19, 2021 at 8:54 am in reply to: [Resolved] JS error Cannot read property ‘concat’ making crashing my Divi blog #33060Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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!Marko VasiljevicKeymasterHello 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_embed
parameter 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!Marko VasiljevicKeymasterHello Svyatoslav,
Thank you for your inquiry about the caching statistics feature.
The improved Statistics page allows you to check the Hit rates and overall effectiveness of every configuration enabled in your General settings.
You can use Statistics to check the following:- Page Cache (Disk, Disk-Enhanced, Redis, Memcached)
- Minify
- Object Caching
- Database Caching
- Fragment Cache
- System info (PHP Memory, CPU Info)
- Cache storage size used (Redis, Memcached)
Enabling the Debug mode for each setting in Performance > General Settings > Debug gives you more detailed information by clicking on a link of the desired setting in the Statistics Page.
If for example, Object Cache is disabled, it won’t be available in Statistics
In Performance > General Settings > Statistics, you can enable Statistics and customize your desired settings.
Please check this screenshot
You can check more detailed information in our documentation.
Thanks!Marko VasiljevicKeymasterHello Steven,
As per our conversation in the support channel, W3 Total Cache does not support push-type FSD so in this case, we cannot help with this. You should reach out to AWS directly for assistance for your use-case.
Thanks!
September 2, 2020 at 12:55 pm in reply to: Does W3 Total Cache work with a “Force Login” Plugin #26377Marko VasiljevicKeymasterHello Michael,
Thank you for the clarification.
In this case, you can use W3 Total Cache for caching. However, once the user is logged in if the option in W3 Total Cache “Don’t cache pages for logged in users” is enabled, then the user will not receive cached pages. In case you want a logged in users to see cached pages, you should disable that option.
Again it’s not recommended to serve cached pages to logged-in users.
If you by any chance run into any kind of issue, please make sure to drop us a note so we can assist you with this.
Thanks!
September 2, 2020 at 10:09 am in reply to: Does W3 Total Cache work with a “Force Login” Plugin #26358Marko VasiljevicKeymasterHello Michael,
I’ve checked the Force Login plugin and it appears that it may be adding no-cache headers to prevent caching.
It is not advisable to cache pages to logged-in users. The reason for this is because some secure content may be displayed to the other users that should not have access to this.
Also, please share some more information on what you want to achieve, what do you expect to be cached, and do you want pages also cached for logged in users?
Thanks!
- AuthorPosts