We use the Agressive preset and everything is looking good, except the huge size. What can we do to prevent this? Any guidance would be greatly appreciated. Let me know if you need any details from me.
Thank you.
I tried to use Super Page Cache with LS Cache, so I disabled any page caching settings related to LS Cache and successfully connected Super Page Cache with CLoudflare.
All was good until I saw some changes in LS Cache would be back to previous state after saving and hitting refresh, and after trying to purge cache (first LS Cache then Super Page Cache), it made the admin bar available to normal users! And sometimes after purging LS Cache only, it made the admin bar unavailable for everybody (including me the admin!).
That’s a very big security risk and after trying to solve the issue on my own, and failing, I had to deactivate and reactivate the plugin (even rolled back to v 5.0.3) and it got worse (Super Page cache was shown and although deactivated, clicking on it from the admin bar led me to the plugin page!!). Above all, I tried the latest version one more time, and couldn’t get Super Page Cache enabled (it refreshed every time I hit enable, and the same page would show up again). so I had to remove it.
What I’m asking for is a general, newbie friendly guide on how to set Super Page cache and LS Cache, so they would not conflict in any way. I really enjoyed connecting with Cloudflare seamlessly, but Since I’m using LS Cache and I need some of it’s other functionalities, I need help.
P.S. I already went through Tom Dupuis’s article and support thread you went through in the forum. But unfortunately some of these issues were new and I couldn’t find a solution.
I would really appreciate you help
]]>Before accepting the cookies, the page cached & optimized, minified, etc.
After accepting the cookies, the page uncached, means it nullify any liteseed config include any optimization.
I’ve exclude the cookies as instructed in the FAQ, my understanding this options will only exclude this specific cookies but still serve cache page & their optimization.
Does this mean I need to trade “cookies consent feature” with “cached & optimized page”?
How can I get cookies consent accepted with cached & optimized page?
]]>LSCache has a very aggressive preset, but if Elementor works with it, I think with a little effort on your part your animation widgets can work too.
What does this aggressive mode do? It prevents all Javascripts from executing until the user interacts in some way, this greatly increases performance. However, of the plugins I’m using, only yours is no longer working.
I have the Pro version, but this happens with Free too.
Is there a more appropriate forum for this? I understand this is neither a feature request nor a bug… So I hope I’m not in the wrong place.
If it is not possible to make it 100% compatible with this aggressive mode, could you tell us which scripts we should bypass in the LiteSpeed Cache configuration so as not to optimize. (I was using Qi Text Animated)
Thanks!
]]>Is there something on settings side that i should take a look? In woomcommerce settings i have set to purge only product when it is out of stock. Also i have unchecked the “pages” in purge after upgrade settings.
Any ideas why it is happening? very anoying and it renders the LiteSpeedCache unusable, because we get out of stock products every 2 days, which results in all products being purged, which defeats the purpouse, because we have to rerun the crawler that takes 3-4hours
Report number: OIUHMOML
]]>If so was it using a local LS server or using the Quic CDN?
LSCache claims it can handle twice as many requests per second compared with W3T Cache and can also perform caching for logged in users.
Has it lived up to the claims in a PMPpro setting?
]]>I want exclude the plugin WooCommerce Pincode/ Zipcode Checker from caching as each consumer wants to check thier own pincode for delivery date. But i want to exclude the plugin from caching by Litespeed Cache. How can i do that as i have tried excluding the JS & CSS but it didnt work.
]]>We have to manually empty the lscache for the redirections to be taken into account for the users. ]]>
Problem: LiteSpeed Cache will check for the “Accept” header content for the WebP support, “image/webp” if the Image WebP Replacement option is enable, but the plugin will make request without this header settings, and while the cache will be made, it will be for the version of browsers that doesn’t support WebP, so the warmed up cache will not hit on most of the browsers.
Solution: Add an option to manually set the header or add a new header option by the user.
This is the .htaccess LiteSpeed code that will trigger two different cache variants when WebP replacement is enabled.
### marker WEBP start ###
RewriteCond %{HTTP_ACCEPT} "image/webp"
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
RewriteCond %{HTTP_USER_AGENT} iPhone.*Version/(\d{2}).*Safari
RewriteCond %1 >13
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
### marker WEBP end ###TLDR: If you use LiteSpeed cache, disable “Image WebP Replacement” till the module will include more options for request header set-up.
However, there’s a catch. If you use LiteSpeed WebP image replacement, then you should disable it, as the cache will not work on browser with WebP support, most browsers, and the page will re-cache at runtime. In order to handle this, the plugin should be capable to set the “accept:” header to “image/webp”.
This is not a plugin issue, but would be nice to add a feature for compatibility fix (let user add custom header in request) with this type of headers, as it will not cache for a live version of Chrome, for example, that supports WebP without these modifications.
]]>