Search results

You can't compare any other module with LiteSpeed cache module. This module is only a control panel to tell the web server (the web server caches, but not the module) what he has to do. Anyway, you are basically right. It is up to LiteSpeed to fix an issue, but LiteSpeed can't consider every 3rd...

It means what it means. If neither PrestaShop nor Cache Plugin is updated for a long time and nobody is willing to update, then you can't expect that the issue will resolve itself. Sorry, but this is sadly reality. I can't speak for LiteSpeed, but I think an update will be released first if...

Check this: https://wordpress.org/support/topic/is-cloudflare-plugin-no-longer-compatible-with-litespeed-cache-plugin/

@elektronen PrestaShop and cache plugin for PrestaShop have been updated more than 1 year ago. What do you expect?

It is not only about Cloudflare. LiteSpeed has added a new feature in the current release that checks installed plugins for conflicts with other plugins based on reported issues. In my opinion, this new feature is not about patronizing users or displacing other plugin manufacturers, but about...

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

If you have no other application with LScache running you can purge the entire cache with a blank PHP file. Place this file with a filename of your choice whereever you want and add code below into this file. <?php header("X-LiteSpeed-Purge:*"); Execute this file in your browser and the...

Basically yes, but it is no good idea only to "refresh" the affected product page(s). Information about a product can be displayed everywhere in an online shop?! Did you consider that?

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

It depends on the request. If user types in http://www.domain.com there are 2 redirects. If he enters https://www.domain.com it is only one redirection. Unfortunately this cannot be prevented.

This will redirect all requests with http to https RewriteCond %{SERVER_PORT} !^443$ RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L] And this will redirect all requests with www. to no non www. RewriteCond %{HTTP_HOST} ^www\. RewriteRule ^(.*)$ https://domain.com/$1 [R=301,L]...

If you have cache plugin for Wordpress, read this: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/ Otherwise a link to your page and information about what kind of plugin you use would be very helpful.

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Would you provide us with information from support what is going wrong and how it can be fixed?

Sorry, have no information about a new release, but you can use https://www.litespeedtech.com/slack to get more information.

Okay, open a support ticket to get qualified support.

Nothing seems to be wrong. Crawler script checks cache status and if status is "miss" then it requests URL again to cache it. If you run crawler again message for cache status should be "hit".

This is only a warning, but is a consequence of that current cache plugin version isn't PHP 8.x ready.