Marko Vasiljevic

Hello @qiuzman

Thank you for the feedback.
Please let us know when you are able to test this again
Thanks!

Hello @belenberrueta

Thank you for reaching out and i am happy to help!
Can you please check if the file advanced-cache.php exists in the /wp-content/ folder and if so, please delete this file?
Are you using any other plugin that may be utilizing Page Caching?
Thanks!

Hello @idovecer

Thank you for reaching out and I am happy to help!
This is most likely related to the nonce system. This means that the cache needs to be invalidated for example every 10-12 hours and the default expiration is set to 3600s

Can you please share the page whare the form is added, and please try to exclude the page from being cached in Performance>Page Cache>Advanced>”Never Cache following pages” save all settings and purge the cache. This way we can determine if the issue is related to Page Cache

Thanks!

Hello @wamwebdev

Thank you for your feedback
I am interested to see how you configured the cache priming. Does the sitemap contain all URL’s? How many urls/pages are in on the website?

What the feature does is this:
– Check the last offset
– Check how many URLs are allowed to be processed per run
– Fetch all URLs from sitemap (even nested sitemaps work)
– Loop through a set of URLs to visit them

If the end of the list is reached, it will start from the beginning in the next run

Basically it’s like visiting the website to do what a real visitor would do otherwise. The cron job triggers the page cache generation, so the real visitors won’t experience any delay. Meaning, the cache will be primed again even if it’s not expired

I hope this helps!

Hello @wamwebdev

Thank you for reaching out and I am happy to help!
If you are using custom cron you can set the specific time when the preload should start (Note that priming will start from the beginning once the end of the sitemap is reached)
Alternatively, you can use wp-cli and call wp w3-total-cache pgcache_prime [--start=<start>] [--limit=<limit>]
Let me know if this helps!

Thanks!

Hello @spoodes

Thank you for your feedback.
I would recommend staying up to date and checking the Newsletter (hoping you are a Pro user).
I would also recommend you to sign up for Woo beta testing for this and you can do this by checking our form .
Thank you again for your patience

Hello @spoodes

Thank you for reaching out and I am happy to help!
I cannot disclose everything at the moment, I only can say that the solution we are finishing up is going to solve these problkems when it comes to cahcing and currency swithcer, geolocation etc.

At the moment The solution would be to fire the currencly swithcer with Ajax which involves more dev work if the plugin you are using for this does not have that as an option.
We appreciate yoru patience.

Thanks!

Hello @dylandawg

Thank you for reaching out and I am happy to help!
This may be some temprary hiccup or serving stale cache, meaning the Browser is still fetching the existing cache if it’s nor reloaded.
This being said, You shoul also reload the browser as the cache may also be stuck there.

There is also a possibility that you have another layer of caching that needs to be cleared also.
Is tehre a chance you can share the website URL and also please let me know how you confirmed that the cache is served from the disk?

Thanks!

Hello @lyk-1

Thank you for reaching out and I am happy to help!
The answer is yes. The cache is a bit different when it comes to W3TC created cache and the Cloudlfare as the website is useing cloudflare as a CDN. So yes, once the Cache is invalidated with the W3 Total Cache, the content is also invalidated and updated in Cloudflare.

I hope this helps!

Thanks!

Hello @qiuzman

As you can see in the examples you can use {wp_content_dir}/uploads/*

And to confirm, are those css and Js uploaded?

Thanks!

Hello @more-than-god

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

 W3 Total Cache usees the ability of the server to use caching methods like Memcached or Redis. This notification you are getting means that the W3TC detects the Memcached, however, the Memcached service is not running or it needs to be restarted.
If you are unsure about this, please reach out to your hosting provider or use terminal to do this yourself:

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 @qiuzman

Thank you for reaching out and I am happy to help!
Can you please share exactly which CDN type is selected in the Peformance>General Settings – CDN section?

Also you are mising * in the path list:

{wp_content_dir}/uploads/elementor/*.css

{wp_content_dir}/uploads/porto_styles/css/*.css

You can also use {uploads_dir} placeholder or the entire path of like /wp-content/uploads/elementor/*.css

Also please sahre the CDN settings in Performance>CDN

Thanks!

Hello @ediet

Thank you for your feedback

Yes, this means that the pages with query stings should not be cached.
Can you please share an example of the amp page you are having issues with that is not updating so I can check this? Do you have any other layer of caching like server side caching or some proxy cache?
Thanks!

Hey @n3wjack

Thank you for your feedback.
This may have something to do with the cached data and autoupdate so it is only a temporary problem.
I would also like to empasize that as you can se ein the description, it’s recommended to use memory-based caching method like Redis or Memcached for Object Caching and DB Caching so if your provider has the option, please check this in order to avoid issues in the future

Thanks!

Hello @ediet

Thank you for reaching out and I am happy to help!
Can you please share which caching method you are using for Page Caching and is the option to cache pages with query strings enabled in Performance>Page Cache?

Thanks!