Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:litemage:configuration [2015/11/12 21:00]
Michael Alegre
+++ litespeed_wiki:cache:litemage:configuration [2017/04/27 20:59]
Jackson Zhang [Configuration Settings By Section]
@@ Line 1: / Line 1: @@
 ====== Important Note About Updating ======
-Updating LiteMage will overwrite LiteMage's "config.xml" file. Before you update, make sure to copy and save your "config.xml" file if you have made any customizations.
+Updating LiteMage will overwrite LiteMage's "config.xml" file. Before you update, make sure to manually copy and save your "config.xml" file if you have made any customizations.
-====== Magento Configuration =====
+====== Preliminary Magento Configuration =====
   * For LiteMage to work correctly, you must have both "Configuration" and "Layouts" enabled under System -> Cache Management in the Magento Admin Panel. If you are using Magento Enterprise, you must also disable "Page Cache".
@@ Line 30: / Line 30: @@
-===== Notes On Specific Configuration Settings =====
+===== Configuration Settings By Section =====
+  * **[[litespeed_wiki:cache:litemage:configuration:cache_storage_management| Cache Storage Management]]**
-  * **Default Private Cache TTL:** Should not be set higher than the Cookie Lifetime setting (System -> Configuration -> Web). The default Cookie Lifetime value is 3600.
+  * **[[litespeed_wiki:cache:litemage:configuration:general_settings|General Settings]]**
-  * **Enable Cache Warm Up:** Because LiteMage is encrypted, the Magento cron.sh must use a PHP with IonCube Loader. Updating the cron.sh PHP_BIN setting to "PHP_BIN=/usr/local/lsws/fcgi-bin/lsphp5" will connect it to LSWS's PHP. (How to set up the Magento cron job: http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/how_to_setup_a_cron_job )
+  * **[[litespeed_wiki:cache:litemage:configuration:system-defined_cache_rules|System-Defined Cache Rules]]**
-  * **Enable LiteMage Cache Only for Listed IPs:** This setting is used to allow administrators to test caching from certain IPs on a production server. When you are ready to use LiteMage Cache for all users, leave this setting blank. After updating this setting, flush LiteSpeed's cache (System -> Cache Management). This will get rid of the cached copies made during testing (which cannot be served to normal users).
+  * **[[litespeed_wiki:cache:litemage:configuration:user-defined_cache_rules|User-Defined Cache Rules]]**
-  * **Track Recently Viewed Products:** Recommend setting to "No" if your template does not show last viewed items. If set to "Yes"; every time a product page is viewed it must be recorded in Magento's backend database, initializing the Magento framework and greatly slowing down the site. If you would like to know how to disable the "recently viewed products" block from your template, try this guide from [[http://www.templatemonster.com/help/magento-how-to-remove-recently-viewed-products-block.html|TemplateMonster]].
+  * **[[litespeed_wiki:cache:litemage:configuration:caching-additional-urls|Caching Additional Known Cacheable URLs]]**
-  * **Flush LiteMage Cache:** The Flush LiteMage Cache button (under System -> Cache Management) flushes all public and private caches. Cache Warm Up (if enabled) will also be started automatically after the cache is flushed. Disabling LiteMage through LiteMage Configuration will also cause the cache to be flushed.
+  * **[[litespeed_wiki:cache:litemage:configuration:cache_warm_up|Cache Warm Up]]**
+  * **[[litespeed_wiki:cache:litemage:configuration:developer_testing|Developer Testing]]**