Enable LiteMage Cache

Global setting. Determines whether your server runs our LiteMage Cache or not.

  • After LiteMage is installed, it’s disabled by default. To enable it, you need to change this setting.
  • Setting this to “no” will auto flush all LiteMage cache.
  • Always enable/disable LiteMage using this setting, do not disable  LiteMage using “disable module output”, doing so will cause trouble.

Admin IPs

Global setting. Allows listed IPs (space or comma separated) to perform certain actions from their browsers using LITEMAGE_DEBUG and LITEMAGE_CTRL parameters.

  • We’ll gradually add more control actions.
  • This makes it very convenient for administrators to perform certain actions from a browser without logging into the admin panel.
  • This also allows you to automate some tasks with scripts. For example, if you have direct database updates for pricing, you can add a script at the end of your update program to purge the related products and categories.

Default Public Cache TTL

Set on a per store basis. Determines how long (in seconds) public cached pages and data are stored for. The recommended value is 86400.

  • Change this setting based on your store’s needs. If your store updates frequently, set this to a lower value, otherwise, set it to a higher value. The default setting is 24 hours (86400 seconds).

Default Private Cache TTL

Set on a per store basis. Determines how long (in seconds) private cached pages and data are stored for. The suggested value is 1800 and the suggested maximum value is 3600 as that is the default Cookie Lifetime value and this should not be set higher than the Cookie Lifetime setting (System → Configuration → Web).

  • Each user’s private data is stored in private cache, this value can be in sync with your PHP session timeout and Magento session timeout.

Home Page TTL

Set on a per store basis. Determines how long (in seconds) the home page is stored for.

  • Use this setting to specify a different TTL for the home page.
  • By default, this setting will use the Default Public Cache TTL setting’s value.

Track Recently Viewed Products

Set on a per store basis. Allows for recently viewed products functionality to work correctly even when page is served from cache. Disabling this will speed up page loading, but may make recently viewed products not appear and Magento “most viewed” reports not accurate. If you would like to know how to disable the “recently viewed products” block from your template, try this guide from TemplateMonster.

  • Turn this off if your store front end does not show recently viewed products.
  • If your store shows recently viewed products, it is highly recommended that you review your store’s design and user behavior to determine whether it is really needed. We recommend you remove the recently viewed products block from your template because having this enabled will greatly slow down the page. Every product page, even if most of the page was served from cache, will also go to the Magento backend and insert the last viewed product for that user into the database. However, if you need this feature, you can leave it on. LiteMage will work properly for this case while many other cache solutions cannot.

Separate Cache Copy per Customer Group

Set on a per store basis. Enable this only if you have a different view or pricing schema for different customer groups.

  • If you have a different view based on customer groups, you need to enable this.
  • For example, users who aren’t logged in cannot see the price while users who are logged in can see the price information. To accomplish this, you need to set the Separate Cache Copy for users who are logged in and users who are not.
  • For example, if you have a wholesale group that sees different prices than regular users, you can set this to “Yes”. This feature will be improved in future to allow you specify which user group it applies to.

Flush Product and Categories When Product Qty Changes

Available since LiteMage version 1.2.0

Global setting. Determines how changes in product quantity and product stock status affect product pages and their associated category pages.

There are four possible values this can be set to:

  • Flush product when quantity or stock status change, flush categories only when stock status changes – This setting is useful if your product page displays a product quantity and both the product and category pages display differently when the product is out of stock.
  • Flush product and categories only when stock status changes – This setting is useful if your product and category pages don’t display product quantities but do display differently when a product is out of stock.
  • Flush product when stock status changes, do not flush categories when stock status or quantity change – This setting is useful if your product page displays differently when the product is out of stock and the category page does not.
  • Always flush product and categories when quantity or stock status change – This setting is useful if both your product page and associated category pages show product quantities and display differently when the product is out of stock.

Mobile Theme

Set on a per website basis. Set this only if using an unresponsive themes with a different mobile template theme.

Adding your mobile template theme to this option will add an extra layer of protection against cache contamination by checking the detected theme against the entered value.

  • Setting this option is required to use the Crawl for Mobile Views option.

Use Alternative ESI Syntax

Global setting. If the standard ESI include tags are being filtered by some extension(s) and causing ESI parser errors, you can enable Alternative ESI Syntax, which is known only by LiteMage and LiteSpeed Web Server.

  • Standard ESI syntax is <esi:include src=”…”/>
  • Some extensions doing html minify may not recognize this syntax and may remove it, causing LiteMage to not function. If you have errors due to ESI syntax being removed, you can enable this setting. The default value for this setting is “No”.