Search results

It's okay now, but you must purge the LiteSpeed cache as well.

Disable all CCC cache settings.

If site cache is the Smarty cache you shouldn't use this kind of cache as it isn't compatible with LScache. Good idea, but you should warmup the cache after the cache is purged. With the Kitt Cache Crawler for PrestaShop you don't need an extra cron for purging the cache since Kitt can do this...

You must place the file to purge the cache in the document_root.

The AWR plugin expects images in this format to be recognized: [filename].[jpg|png].avif and images must be stored in default WP category structure:/wp-content/uploads

This bug has never been fixed, so there is only a quick & dirty fix available. https://www.litespeedtech.com/support/forum/threads/prestashop-login-problem.22707/post-128259

Name the file as you like it. The code allows only to be executed in console or by cron. If executed only the cache generated by LScache plugin for PrestaShop is purged. Setup a cron job with intervall of your choice: php /absolute_path_to_purge_file/filename_of_your_choice.php <?php...

Memcached or Redis are not a LiteSpeed related features. If your host doesn't provide Memcached or Redis then he wants you to invest more money in a hosting plan where Memcached or Redis is supported. If such features are not supported with the current hosting plan, there is no alternative to...

Don't be confused if a solution can be easy. If an error ocurrs the most important thing to find out the reason for an arror is how or what is the error caused by. Every error can be logged, so check the provided error logfiles what was going wrong. Just think logical, nothing happens without a...

A plugin is more than a few lines of code in .htaccess and a plugin is not a universal plugin. Each CMS needs its own cache plugin for php programming.

Yes

A forum is not page cache friendly. Too many changes to the content in too short a time. You also need an intelligent purge solution for new or changed threads, which can only be created to a very limited extent using .htaccess. If at all, the cache and purge configuration must be done using PHP.

If you want the crawler to be enabled you must notify the A2 support on which domain or sub-domain you need the crawler. A2 support is good, but not every (first level) supporter is a specialist for LiteSpeed, so you should give as much information as possible to redirect your need to a...

Normally it doesn't take more than 24 hours to get an answer from A2 support.

A2 supports the crawler, but it must be enabled for every domain and sub-domain (on shared hosting plan), so if you have the crawler support requested wait for confirmation. btw. The Kitt cache crawler isn't limited by any restrictions!

If you have access to the LiteSpeed WebAdmin complete the settings, otherwise and if you are on Shared Hosting contact A2 support as the crawler must be enabled for every domain and sub-domain. On Shared Hosting the ESI function is enabled by default at A2.

The settings in WebAdmin are globally, so if lscache, the crawler and ESI are enabled, these settings should be available on all domains. You can check it by creating a custom test php file. Create a custom php file and enter <?php echo $_SERVER['X-LSCACHE'] upload this file where you use...

lscache, the crawler and ESI must be enabled in WebAdmin console. You can check the settings by running phpinfo() in a custom php file.

I don't see any LiteSpeed cache header!? Kitt for PrestaShop expects PrestaShop to be installed. thirty bees isn't supported. ESI must be enabled in LiteSpeed WebAdmin console.

There is a fallback solution integrated in the LScache plugin for Wordpress, but this fallback needs the main document to be requested, means, if a webp image is requested directly and the browser doesn't support webp this webp image can't be displayed by this browser. But you shouldn't worry...