One of the most important tasks you need to remember after each major change (and before Magento upgrade) is to clean up your Magento cache.
This code snippet contains some code excerpts from this thread in magento forums.
01 |
<?php |
02 |
require_once 'app/Mage.php'; |
03 |
ini_set('display_errors', 1); |
04 |
umask(0); |
05 |
Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID); |
06 |
07 |
refreshCache(); |
08 |
09 |
function refreshCache() |
10 |
{ |
11 |
print( 'Refreshing cache<br/><br/>' ); |
12 |
try { |
13 |
Mage :: getSingleton( 'catalog/url' ) -> refreshRewrites(); |
14 |
print( 'Catalog Rewrites was refreshed successfully'. '<br/>'); |
15 |
} |
16 |
catch ( Exception $e ) { |
17 |
print( $e -> getMessage(). 'warning' ); |
18 |
} |
19 |
try { |
20 |
Mage :: getSingleton( 'catalog/index' ) -> rebuild(); |
21 |
print( 'Catalog Index was rebuilt successfully'. '<br/>'); |
22 |
} |
23 |
catch ( Exception $e ) { |
24 |
print( $e -> getMessage(). 'warning' ); |
25 |
} |
26 |
27 |
try { |
28 |
Mage :: getSingleton( 'catalogsearch/fulltext' ) -> rebuildIndex(); |
29 |
print( 'Search Index was rebuilded successfully'. '<br/>'); |
30 |
} |
31 |
catch ( Exception $e ) { |
32 |
print( $e -> getMessage(). 'warning' ); |
33 |
} |
34 |
try { |
35 |
Mage :: getSingleton( 'cataloginventory/stock_status' ) -> rebuild(); |
36 |
print( 'CatalogInventory Stock Status was rebuilded successfully'.'<br/>'); |
37 |
} |
38 |
catch ( Exception $e ) { |
39 |
print( $e -> getMessage(). 'warning' ); |
40 |
} |
41 |
try { |
42 |
Mage :: getResourceModel( 'catalog/category_flat' ) -> rebuild(); |
43 |
print( 'Flat Catalog Category was rebuilt successfully'. '<br/>'); |
44 |
} |
45 |
catch ( Exception $e ) { |
46 |
print( $e -> getMessage(). 'warning' ); |
47 |
} |
48 |
try { |
49 |
Mage :: getResourceModel( 'catalog/product_flat_indexer' ) -> rebuild(); |
50 |
print( 'Flat Catalog Product was rebuilt successfully'. '<br/>'); |
51 |
} |
52 |
catch ( Exception $e ) { |
53 |
print( $e -> getMessage(). 'warning' ); |
54 |
} |
55 |
} |
56 |
?> |
Below are the list of few type of cache that is mainly used with magento website
File System (Var/cache) Cache: This is the default cache available with magento itself . By this magento stores the cache data under Var/cache folder. As per previous article magento created different kind of tag group and associate cache data into that tag group.
Advantage of File System Cache:
its by default so doesn’t need to install anything
Disadvantage of File System Cache:
Because it uses cache data in file system then if site has huge traffice or huge data for which it require huge cache data to be stored into file then it will make the system slower
We are going to try to explain how Magento full page cache works by looking at the code, it’d be cool if we’d have talked with some of the folks at Magento to get a better information but hey you should always trust xdebug over humans’ words, right?
Our approach is very simple, look at the workflow and try to translate it into words. So we are doing some reverse engineering here… take the code and explain the logic back.
Two of the most requested articles I have been asked to write so far have been about magento’s full page cache and Magento’s SEO.
Today we are going to try to tackle the former and hope to get 2 things out of it:
This article is pretty ambitious and we may need to write a follow up to crush all doubts. Don’t hesitate to use the comment section or twitter for clarification.
