# Installation¶

Before installing and activating the LSCache plugin, deactivate all other full-page cache plugins.

Tip

You can still use other types of cache (like object cache), but only one page cache can be used at a time, so you’ll need to disable any other page caches, if you want to use LSCache.

## Module Installation¶

Note

Please see the Overview for the server-level requirements before attempting to install this module.

3. Set Advanced Parameters > Performance> Debug mode > Disable all overrides to NO. This is required to ensure proper functioning of the ESI hole-punching feature.
4. Navigate to Modules > Module Catalog, and click on Install a module.
5. Select the LSCPS zip file.
6. Enable the module by navigating to LiteSpeed Cache > Settings and setting Enable LiteSpeed Cache to Yes.

### Fixing an Error¶

If you see the following error message, Directory /home/example/example.com/app/logs is not writable, you can fix it like so:

touch /home/example/example.com/app/logs
chown example:example /home/example/example.com/app/logs


Then, upload and install the module again.

## .htaccess Update¶

When you enable or disable LiteSpeed Cache from the plugin, the .htaccess file should be automatically updated. If the update fails, it is usually due to file permissions. You can update it manually if necessary.

At the top of your .htaccess file, located in the document root of your PrestaShop installation, add the following:

# LITESPEED_CACHE_START Do not remove this comment line, LiteSpeedCache plugin will automatically update this block
<IfModule LiteSpeed>
CacheLookup on
</IfModule>
# LITESPEED_CACHE_END


## Verify Your Site is Being Cached¶

You can verify a page is being served from LSCache through the following steps:

1. From a non-logged-in browser, open the developer tools and navigate to your site. Open the Network tab.
2. Refresh the page.
3. Click the first resource. This should be an HTML file. For example, if your page is http://example.com/webapp/, your first resource should either be something like example.com/webapp/ or webapp/.
4. If you see headings similar to
X-LiteSpeed-Cache: miss
X-LiteSpeed-Cache-Control:public,max-age=1800
X-LiteSpeed-Tag:B1_F,B1_

(for example), this means the page had not yet been cached, but that LiteSpeed has now stored it for future use.
5. Reload the page and you should see X-LiteSpeed-Cache: hit in the response header. This means the page is being served by LSCache and is configured correctly.
6. If you don't see X-LiteSpeed-Cache: hit or X-LiteSpeed-Cache: miss, then there is a problem with the LSCache configuration.

Last update: August 22, 2020