Skip to content

Configuration

System Config Page

After installation, start here: Stores > Configuration. This is where you tell Magento to use LiteMage, and then give LiteMage some basic instructions.

System Tab

System Config, System Tab

Magento has a built-in full page cache, so if you want to use LiteMage, you need to change the default. In the Full Page Cache section of the System tab, next to Caching Application, make sure Use system value is unchecked, and then choose LiteMage Cache Built in to LiteSpeed Server from the drop-down.

You can change how quickly content expires, if you wish. Under TTL for public content, uncheck Use system value, and enter your preferred TTL in seconds.

Press the Save Config button when you finish making changes.

LiteMage Cache Tab

General Settings

System Config, LiteMage Tab

Context Vary Bypass

By default, LiteMage does not cache if there's a context vary change in the response. Context Vary Bypass allows you to override this behavior for global, cacheable contexts. List the context variables here in a comma-delimited string, and LiteMage will cache them despite any changes.

Enable Custom Vary

Enable Custom Vary controls whether to allow customized varies (for example, different currencies based on GeoIP). And if it is allowed, you must choose how to handle a customer's first visit. Is it more important that they are served from cache for that visit? Or is it more important that the value of the context variable is evaluated immediately?

  • No does not enable custom vary.
  • Yes and allow guest mode for first visit ensures that the customer gets a fully-cached version of the page on the first visit. However, the content served will be based on the view of a non-logged-in guest and will not take the value of the custom vary into account until the customer loads the next page.
  • Yes and enforce vary checking on first visit will show the customer the correct content for the custom vary, but the customer will not be served from cache until their next page load.
Ignored Identity Block Names

Identity blocks output cache tags. Cache tags are important for intelligent caching, and the ability to selectively purge groups of related cache objects. But if an identity block outputs many unnecessary tags, or the block appears on every page, this can impact performance. If you have identity blocks like these, you can ignore their cache tags and improve performance.

Add the comma-delimited block names to this list.

Ignored Cached Tags

Similar to the previous setting, this setting allows you to improve performance by ignoring unhelpful cache tags. In this case, though, you can specify a single tag instead of an entire block name.

For example, you can ignore any tags that appear on every page, since purging one of those tags is the same as running a Purge All command. There is no benefit to tracking such cache tags, and in fact, tracking them may degrade server performance.

Turn on LiteMage Debug to examine the tags shown on the header, and determine which ones may safely be ignored. Add these tags to the ignore list in a comma-delimeted string.

Developer Settings

System Config, LiteMage Tab

Enable Debug

You can enable debug mode, if you are trying to troubleshoot a problem. There are three options in the Enable Debug setting: No, which is the default setting; Yes; and Yes and set X-LiteMage-Debug response headers. You can learn more about what this last setting does for you in our Troubleshooting Guide.

Log Debug Messages Only for Listed IPs

In order to keep the error log size under control, and make debugging easier, you can specify one or more space-separated or comma-separated IP addresses for logging. Debug messages will only be logged for requests originating from the listed IPs.

Log Backtrace for Purge Events

This setting helps you troubleshoot unexpected purge events. When enabled, a backtrace will be logged every time the cache is purged.

Front-End Store ID

This setting allows you to determine which store is purged when the cache is flushed from the backend.

This is helpful in a multi-site and multi-store setup, where an incorrect URL might otherwise be purged.

LiteMage Server IP

If LiteMage is behind a CDN or proxy server, use this setting to specify the location of the LiteMage Cache server. This way, a cache flush can access the LiteMage server directly, instead of going through the proxy.

Cache Management Page

Cache Management

The Cache Management page (System > Cache Management) is where you enable page cache so LiteMage can work. It's also the place where you can flush the cache, and keep an eye on your LiteMage plan usage.

Enable Page Cache

If Page Cache does not have a green Enabled indicator in the Status column, then you will need to enable it. Click the checkbox next to Page Cache, select Enable from the dropdown box at the top of the table, and press Submit. LiteMage Cache will then be enabled.

You can disable LiteMage in the same manner, except you would choose Disable from the drop-down list.

Flush LiteMage Cache

The Flush Magento Cache button at the top flushes all of the enabled caches on the Cache Type list, including Page Cache, aka LiteMage.

To flush only LiteMage, click the checkbox next to Page Cache, select Refresh from the dropdown box at the top of the table, and press Submit. LiteMage Cache will then be flushed.

Check LiteMage Usage

Here's what each field of the usage chart indicates:

  • Current LiteMage Plan: Your current plan, which would be LiteMage Starter, LiteMage Standard, or LiteMage Unlimited.
  • Public Cache Hits: Number of requests that hit public cache since the last Flush All. This number should not be 0.
  • LiteMage Cached Objects: Current publicly cached object count. There should be more than 0 of these.
  • Not Cached (Limited by Plan): Number of requests not served from cache due to plan limitations. You can upgrade your LiteMage plan if this value is not 0. If your store's number of cached objects hasn't reached the limit yet, it will show 0. This is fine. It means your store is in good shape and does not require more caching than your plan can handle.

Last update: May 20, 2022