{"id":378496,"date":"2023-04-27T07:49:34","date_gmt":"2023-04-27T07:49:34","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=378496"},"modified":"2023-04-27T09:05:05","modified_gmt":"2023-04-27T09:05:05","slug":"theme-fallback-mechanism-magento-2","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/theme-fallback-mechanism-magento-2\/","title":{"rendered":"Theme Fallback Mechanism Magento 2"},"content":{"rendered":"\n

What is Theme Fallback in magento 2<\/h3>\n\n\n\n

Theme Fallback is a mechanism that checks the source file genealogically. if a view file is not found in the current theme, the system searches in the parent themes and module files in magento 2.<\/p>\n\n\n\n

for example-<\/p>\n\n\n\n

If we have a child theme, if the instance needs a source file first it will check in the current child theme and use it, if not found in the current child theme after that parent theme. <\/p>\n\n\n\n

In this tutorial, we’ll override the template, layout, and static file<\/h3>\n\n\n\n

first, we create a custom child theme <\/p>\n\n\n\n

to create a theme check – create a custom theme in magento 2<\/a><\/p>\n\n\n\n

In this blog we’ll change a product page, using template overriding we’ll change the attribute to a custom text, using layout overriding we’ll remove the product page breadcrumb, and using static file overriding we’ll change the store logo.<\/h4>\n\n\n\n
\"main\"<\/figure>\n\n\n\n

Template overriding:<\/h3>\n\n\n\n

The fallback mechanism flows for templates :<\/p>\n\n\n\n

    \n
  1. Current theme templates:\u00a0<current_theme_dir>\/<Vendor>_<Module>\/templates<\/code><\/li>\n\n\n\n
  2. Parent themes templates <parent_theme_dir>\/<Vendor<\/code>>_<Module>\/templates<\/code><\/li>\n\n\n\n
  3. Module templates:\u00a0<module_directory<\/code>>\/view\/frontend\/templates<\/code><\/li>\n<\/ol>\n\n\n\n

    To create a template overriding, we need to create a folder named <vendor>_<module>.<\/p>\n\n\n\n

    so we’ll create Magento_catalog, then create a templates directory.<\/p>\n\n\n\n

    <vendor>_<module>\/templates<\/pre>\n\n\n\n
    create a template file that you want to override with the same name and same folder structure in templates.<\/p>\n\n\n\n
    ex- we’ll override attribute text so we need to override attribute.phtml. so we need to create <\/p>\n\n\n\n
    Magento_Catalog\/templates\/product\/view\/attribute.phtml<\/pre>\n\n\n\n
    In this file, I have just written “simple text”<\/p>\n\n\n\n
    <?='custom attribute'; ?><\/pre>\n\n\n\n
    \"product-2\"<\/figure>\n\n\n\n
    Layout Overriding:<\/h3>\n\n\n\n
    In the layouts, the fallback mechanism is not working. The system collects layout files in the following order<\/p>\n\n\n\n
      \n
    1. Current theme layouts: <theme_dir>\/<Vendor>_<Module>\/layout\/<\/code><\/li>\n\n\n\n
    2. Parent theme layouts : <parent_theme_dir>\/<Vendor>_<Module>\/layout\/<\/code><\/li>\n\n\n\n
    3. All module layout files are in sequence, defined in\u00a0app\/etc\/config.php<\/code>\u00a0.For each module:\n