Search results

It seems you are using the LiteSpeed cache plugin for Wordpress. If there are any issues with this plugin please follow the recommendations to get help provided by this forum. https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/ So please read this...

If LiteSpeed support doesn't answer your question, please contact me by PM.

This issue is related to the LiteSpeed cache plugin for WordPress, but support for this plugin has been discontinued since many years. For support please use the support forum at Wordpress and read this...

Unfortunately, ChatGPT did not do a good job because ChatGPT misunderstood "synchronize". In the specific context, synchronize does not mean that all cron jobs should be executed at the same time to turn 4 cron jobs into just 1. The generated code does exactly that and that is not helpful...

FYI: You don't need 4 or 3 not synchronized cron jobs, but only 1 cron job. The first cron job for product reindex starts the next process if finished and starts the process for sitemap generation and if finished it starts the process to purge the cache. This procedure needs only 1 cron job and...

Yes.

This recommendation depends only on certain hosting providers. Most hosts have enabled ESI by default.

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...