Magento

Magento Fall-Back Hierarchy

Hello friends today I have write a article on Magento Fall-Back Hierarchy.

Magento is use fall-back hierarchy for rendering theme. Now a days it will also use the base package theme for rendering theme.

Lets take one example like in your magento custom theme folder there is one css folder custom.css  file. If any reason the magento will not got the custom.css file then it will check into custom theme default theme folder and if custom.css file fetch then it will render this css file otherwise it will go to the base package and find the custom.css file and render this file.  If in base folder the custom.css file is not found then it will shows the error message in console like “custom.css not found(404)“.

Step 1 : Magento first Look for requested file in

  • app/design/frontend/custom_package/custom_theme/
  • skin/frontend/custom_ package/custom_theme

Step 2 :If magento could not found, then look for requested file in

  • app/design/frontend/custom_package/default
  • skin/frontend/custom_package/default

Step 3 :If magento could not found, then look for requested file in

  • app/design/frontend/base/default
  • skin/frontend/base/default

Step 4 :If magento could not found, then it will rendering error will occur.

The Activity Flow of the Fall-Back Hierarchy

Fall-Back Hierarchy

Advertisements

Leave your comments

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s