Object caching cannot be disabled for specific paths, such as /wp-admin.
Adding /wp-admin to Excludes in Litespeed does not have any effect whatsoever.
I’d recommend for you to learning about the difference of “page caching” and “object caching”.
Hi Till,
Thanks for your reply.
So, instead of making comments about learning the differences between page and object caching (both of which I understand very well) I’d recommend that you take a closer look at Lscache’s implementation of their Object cache settings within their own plugin.
Here’s a link, within you will find both information and a screenshot that has a specific setting to enable/disable object caching of the wp-admin area. It makes clear reference that by enabling object caching on wp-admin, you run the risk of serving expired data. Their plugin works brilliantly for object caching however is cumbersome for our requirements.
https://blog.litespeedtech.com/2018/02/07/object-cache-support-in-lscache/
Again, I ask, does your plugin have a similar capability?
It does not and it won’t, because it’s a bad idea.
May I add my 5 cents into this topic. I also read many other similar topics and it would be great if you could post an example usage of filter. Not really clear what to pass.
I tried doing it this way, but it didn’t seem to work:
add_filter('redis_object_cache_get_value',$value,'pageviews',$group,true,$found);
or should I do it this way:
add_filter('redis_object_cache_get_value',null,'pageviews',null,true,null);
You suggest requesting developer’s help in other topic, but really if it’s just a matter of proper writing of this single line of code, it would be great to see an example usage.
Thanks.
-
This reply was modified 5 years, 6 months ago by
SamTyurenkov.