Full Page Caching - Quick Configuration


Configuration

Back to User Guides

Quick configuration is the best way to see the power of the Full Page Caching in the least amount of time.

If you want to quickly target the 70-90% of your visitors that are not shopping or logging in, you can have the Full Page Caching configured in as little as 30 minutes.

Configuration steps:

  1. The warp.xml file has been added for you so you shouldn’t need to do much.
    In case you have other cms/xml pages you want to have cached automatically that are not found in the warp.xml, follow the next step.
  2. Add the XML code snippet bellow:
  3. XML code snippet
    <reference name="root">   
    	<action method="cachePage">
    	<expires></expires>
    	<disqualifiers>cart,loggedin,compare</disqualifiers>
    	</action>
    </reference><br>
    	
  4. To the layout files (app/design/frontend/[package]/[theme]/layout) listed below:
  5. XML Tip

    For anyone not familiar with Magneto and its use of XML, it’s worth noting that the code snippet from above should be added after each of the opening tags of each layout nodes from the table below.

    Xml Tip Example

    <cms_page translate="label"> 
    	<reference name="root">
    		 <action method="cachePage">
    		<expires></expires>
    		<disqualifiers>cart,loggedin,compare</disqualifiers>
    		</action>
     	</reference>
    	...
    </cms_page>
    	
    Page Layout File Layout Node
    CMS Pages cms.xml <cms_page>
    Layered Catalog Pages catalog.xml <catalog_category_layered>
    Product View Pages catalog.xml <catalog_product_view>
    Layered (no-children) Catalog Pages (optional) catalog.xml <catalog_category_layered_nochildren>

Why is the last page optional?

You colored INSIDE the lines when you were in school, didn’t you? Well, so did the Full Page Caching. the Full Page Caching caches every layout you specify and not a single one more. That last one is optional because not everyone has a category structure that uses that particular layout. It’s also worth noting that while our suggested layouts/pages in the table above cover non-comittal traffic on the front-end of your store, Warp can cache whatever layout you tell it to. For more information on caching more layouts/pages, refer to the full configuration.

Gotcha? Dynamic Content

If you have any content that will need to be unique for each user (recently viewed products, for example), then you will need to provide a full configuration with hole punches.

Memcached

When using memcached, make sure you use a separate memcached instance for your Cache and Sessions. If you use the same instance, you will have problems with clearing sessions whenever you clear cache because it uses the flush_all command. Users will see the cart drop and everyone will be logged out.

Redis

When using Redis, make sure you use a separate Redis instance for your Cache and Sessions. If you use the same instance, you will have problems with clearing sessions whenever you clear cache because it uses the flush_all command. Users will see the cart drop and everyone will be logged out.



Get more information about the Full Page Caching Extension for Magento®.

Find other Magento products at the CreativeMinds Magento Store.

Let us know how we can Improve this Product Documentation Page.

To open a Support Ticket visit our support center.