Tagged: Page Cache
May 10, 2021 at 11:44 am #37551KirillGuest
Please explain which parameters should I set to normal enable normal caching.
1. “Cache SSL (HTTPS) requests” the function is disabled. Otherwise, in pagecache.log has a lot of unreal lines.
For example it will try to cache (I could check it in pagecache.log) /products/* but real page is /product/* (/product pages preloaded too), a lot of 404 pages (“Cache 404 (not found) pages” option disabled), non-existent pages, /wp-content/ pages with images (404 too), etc.. This pages are not present in sitemap.
Could you explain why you need to cache SSL requests? There, for example, “?add-to-cart” or contact form 7 requests can be seen in the log file.
If this value is set, then the plugin will load 30 pages in 50 seconds, and then do others? And what if you don’t have time for 30 pages in 50 seconds?
!! We need to preload ALL pages and store it for a day (or forever until manual reset or by reference (script via wget)). Then regenerate preloaded cache. During the process, users should see the stale cache, and not try to regenerate it when reopening the page. No user should see uncached pages in between cache preload process while they are being re-generated.
3. Why mobile version creates only then page loaded from mobile manually (someone should open page on mobile)? Page preload cannot do it. Tablets and phones are enabled in Cache Groups. Mobile and Tables pages are different (it cannot preload only desktop page and show it on mobile).
Mobile and tablet preload is important.
4. How to preload pagination? /page/2, /page/3, etc
5. How to preload filter? We are using BeRocket filter for products. Here a lot of unique pages but we need it.
6. How to fresh preloaded cache and regenerate it again by link? We are using sync plugin and need to do it via wget request.
7. How to disable preloaded cache freshing? We will do it manually by sync script (sync prices and then refresh cache by wget request). Also, ” Preload the post cache upon publish events” enabled. We want to change something by hands and then cache of this page should be regenerated.
Thank you!May 10, 2021 at 12:00 pm #37577Marko VasiljevicKeymaster
Thank you for reaching out, and thanks for using W3 Total Cache.
1. If you use SSL, then this option is recommended. SSL is becoming more and more popular. So, keeping it enabled is recommended. And if you don’t use SSL at the moment, it’s safe to when it’s enabled.
Also, it’s recommended to cache SSL requests when some of your pages are secure (HTTPS) and some pages are ordinary (HTTP).
Unique caching means that W3 Total Cache caches up to two versions of a page: non-secure (HTTP) and secure (HTTPS).
Anyway, if you don’t want to cache specific SSL pages (e.g. with a shopping cart), you can keep “Cache SSL requests” enabled, but exclude the pages in Performance>Page Cache>Never Cache following Pages
2. Update interval: in your case 50 is the number of seconds to wait before creating another set of cached pages. Again with the provided settings batch of 30 pages will be cached and another patch will be cached after the 50s. Please note that this will increase the server usage so the default settings are recommended.
3. There are no separate cache files for phones and tablets. They are all using the same cache since most likely your theme is mobile/tablet responsive.
If however that is not the case and you are experiencing issues like getting the desktop version of the website on mobile and vice-versa, you can Manage user agent groups in Performance>Cache Groups>Manage User Agent Groups and enable the first two groups for mobile and tablets to ensure that a unique cache is created for each user agent group. Of course, as you can see in the description, you need to select your active theme in the Theme dropdown. Pass through is used if you are using some mobile plugin and in this case, you need to add the URL to Redirect Users to: filed.
4. 5. 6. 7. The cache Preload depends on the sitemap. So every page in the sitemap will be preloaded. There is no other possibility. Once the complete website is preloaded, the process will start from the beginning if in the meantime the cache is not purged. The only way to stop the Preload is to disable Automatically prime the page cache.
If you do not want to rely on wp-cron, you can also use wp-cli call it directly via
wp w3-total-cache pgcache_primeand track the output which pages/sitemap positions are primed by script.
I hope this helps!
- The topic ‘Questions about Page Cache Settings’ is closed to new replies.