Skip to content
This repository was archived by the owner on Jan 19, 2026. It is now read-only.

Latest commit

 

History

History
41 lines (34 loc) · 2.14 KB

File metadata and controls

41 lines (34 loc) · 2.14 KB

Installation Manual for the MageHost_BlockCache extension

Install methods:

Just copy to Magento repo

This installation manual explains how to use Cm_Cache_Backend_File based caching. If you have experience with Redis cache, you will understand how to do it for Redis.

  1. Make sure you run Magento 1.7 or newer
  • Install Modman
  • cd to your Magento root dir
  • test -d .modman || modman init
  • modman clone --copy --force https://github.com/magehost/magehost_blockcache
  • If you keep your Magento code in Git: Add .modman to your .gitignore
  • Edit app/etc/local.xml: inside <config><global> add/update:
    <cache><backend>MageHost_Cm_Cache_Backend_File</backend></cache>
  • In Magento Admin: System > Configuration > ADVANCED > Developer > Template Settings
    • Set Allow Symlinks to Yes
  • In Magento Admin: Flush Cache Storage
  • Log out from Magento Admin and log back in
  • Configure via: System > Configuration > ADVANCED > MageHost BlockCache
  • Test every different kind of page on your site
  • The first hit the page will be slow because we just cleaned all caches. If you hit the URL it should be faster, if caching is enabled for that kind of page.

Git submodule + N98

  1. Make sure you run Magento 1.7 or newer
  • cd to your Magento root dir
  • test -d .modman || modman init
  • git submodule add https://github.com/magehost/magehost_blockcache .modman/magehost_blockcache
  • modman deploy --force magehost_blockcache
  • Edit app/etc/local.xml: inside <config><global> add/update:
    <cache><backend>MageHost_Cm_Cache_Backend_File</backend></cache>
  • n98-magerun.phar dev:symlinks --global --on
  • n98-magerun.phar cache:flush
  • Log out from Magento Admin and log back in
  • Configure via: System > Configuration > ADVANCED > MageHost BlockCache
  • Test every different kind of page on your site
  • The first hit the page will be slow because we just cleaned all caches. If you hit the URL it should be faster, if caching is enabled for that kind of page.