Litespeed Compatibility

Hi @salujagaurav

We haven’t tested it together with the litespeed cache plugin. I just had a look at that plugin and see they offer REST caching too, but you are able to disable that in their settings. Having our plugin activated and REST caching enabled within litespeed will probably cause some issues, but if you would disable REST caching in litespeed I think there shouldn’t be any issue when using our plugin combined with litespeed.

Thank you, it is actually causing cache error on product pages, even when I disabled the Cache Rest API option in Litespeed. Product pages are back to normal once I disabled WP Rest Cache plugin.

Any solution to this?

Is there any update?

Hi @salujagaurav

I just did some tests with Litespeed and our plugin combined and switched off REST caching in Litespeed. I then did some calls to the REST API and they were cached perfectly fine, after editing some of the posts the caches were also flushed correctly. So far I don’t see any issue.

But you are talking about “Product pages”, this probably means you are using WooCommerce? Our plugin doesn’t cache the WooCommerce REST API by default. So if it is being cached for you, you probably have written some custom code to have it cached by our plugin. Somewhere in that code you will most likely find the problem. Unfortunately I cannot help you with that, because I don’t have your code.

I haven’t written any custom code. Can you provide me a code to enable all rest api cache calls?

Hi @salujagaurav

No I cannot provide you with code to enable all REST API cache calls… Caching different endpoints requires different flushing mechanisms. You don’t want us to cache WooCommerce REST API endpoints but never flush them.

We are working on a (paid) add-on for our plugin which will cache the WooCommerce REST API, this is however a long-term project and I do not have any specific date when it will be finished. If you search these forums, there are some topics about caching WooCommerce where I have given some pointers on how it should be done, but that is not finished code you can use straightaway.