szmigieldesign

Mostly awesome!

I was thinking about this issue also in regard to APM (if AMPs are also cached with LSCache). The best way to approach my issue regarding Thrive Comments at present would be to only uncache posts. Main blogroll, tags, categories archives and amp pages don’t use Thrive Comments so they can be cached normally.

So the plugin would have to uncache only pages that follow /blog/ but only on the first path level after (so that /blog/post/amp/ are cached ok). Would that be even possible without being too hard to implement?

Oh, I see. It essentially breaks jQuery.

Yes, on a separate thread you’ve noticed it shouldn’t be handled with nonces but with proper implementation of ESI instead. I’ve read LSCache documentation and it doesn’t look hard to implement ESI in this case. We’ll see.

I’m aware of that and that would be an ideal solution as there’s a tremendous difference in loading times between cached and uncached pages (0.3s vs 1.5s). However, it’s a commercial product and making it compatible with LSCache is a matter of Thrive Comments developers willing to invest their resources in extra work. Modifying it by myself is not an option as it will make the product incompatible with future releases.

On 15th of January I got a reply from their support:
“A feature request with this issues has been logged and will be available in one of our next releases

We will have to see how to prioritize the problem, usually the incompabilities with another plugin are treated based on how the widspread usage of the other plugin.”

You can follow the issue on their comment system here:
https://thrivethemes.com/forums/topic/comments-wont-load-after-certain-time-giving-403-on-wp-json/

It requires an account though.

Consider reaching your host first. For example, in case of polish hosting provider dhosting it is necessary to manually activate LiteSpeed Server cache functionality. Without admin’s intervention LSCache for WordPress didn’t work.

You may want to consider filtering Thrive Leads scripts so that LSCache doesn’t minify them. Also, search for my thread about Thrive Comments as it may be related. Perhaps if we put a lot of pressure on Thrive Themes developers, they’ll make sure their products are compatible with LSCache.

Certainly not. There is very little visual hierarchy in the old version. It’s very easy to miss certain settings and it’s really awkward to work on an old interface using large screens. There’s a difference between well done minimalism and basically no styling at all and I believe the old version was on a no styling side.

Hello.

I’m on PHP 7.1 and with LSCache 1.8 with object cache disabled I’m getting an error

Warning: Invalid argument supplied for foreach() in (...)/plugins/litespeed-cache/inc/object.class.php on line 222

Thanks.

No pressure but I’d just like to know if you’ve had a chance to look into this issue?

Mostly awesome! Thanks for your help. Let’s see if it gets fixed in next version.

What about beta channels per week and stable per month?

Files sent via WeTransfer.

And yes – it seems that my optimized images are being happily reoptimized. Awesome ??