Magento 2 is an open source eCommerce R&D project facilitating the improvement of Magento Core products.
With the new and improved features in Magento 2, developers will be able to offer more functionality to merchants and continue to grow with the platform.
Magento 2 is a prospective future version of the Magento e-commerce software, currently still in the development stage.
This is the first of many posts in the next few months that will provide further insight and updates about the progress, process, technical architecture
and strategy as well as many other facets that involve this important project and milestone for the Magento community.
Some of Features That Magento 2 Offers
• Magento 2.0 will run on PHP 5.3 and Zend Framework as 1.0. And it will support MSSQL, Oracle and some other database as well. This is a good news for Windows Platform Server. We can see that Magento keep growing and seek to support more and more popular platform soon.
• Performance is always an issue for Magento so it is recognized as resource hungry and not efficient. The team of Magento keep improving the performance of Magento version by version. With the 2.0, the performance of Magento will be at least 20% more faster than the latest Magento 1.x versions.
• The modules like catalog, customer, checkout, CMS, sales, etc will be components with high code coupling between each other. Now if you don’t want to use a certain module, you can simply disable it and write your own one.
Here is screenshot for Directory structure and Module Structure of Magento 2 and
• Previously Magento 1.x using module.xml file @ app/etc/modules/ to activate our module but in Magento2 it has been changed. Now we will use config.xml file to activate our module means adding active and codePool tags into your config.xml. Like:
<config> <modules> <Mage_Catalog> <version>126.96.36.199.20</version> <active>true</active> <codePool>core</codePool> </Mage_Catalog> </modules> .....
In Magento2 , factory method has been removed .The way you call models, helpers, blocks is fully different in Magento2 .Instead of factory names you need to use the full class name now as :
And Change in layout xml is introduced in Magento 2. Each module has it’s own layout.xml in module view folder. And Block type uses Class name of block instead of class alias as :
<block type="Mage_Catalog_Block_Product_Compare_Sidebar" before="cart_sidebar" name="catalog.compare.sidebar" template="product/compare/sidebar.phtml"/> <block type="Mage_Core_Block_Template" name="right.permanent.callout" template="Mage_Page::callouts/right_col.phtml"> <action method="setImgSrc"><src>Mage_Catalog::images/media/col_right_callout.jpg</src></action> <action method="setImgAlt" translate="alt" module="Mage_Catalog"><alt>Keep your eyes open for our special Back to School items and save A LOT!</alt></action> </block>
In Admin Magento 2 have some major changes:
• Introduction of Visual design editor. .
The Visual Design Editor is an easy to use, “drag and drop” interface for editing Magento Page Layout. Implementation of the Visual Design Editor means that modifying the arrangement/configuration of Containers and Blocks no longer requires specialized technical knowledge; many of these changes can be made easily in the Admin Panel by any site administrator.
The Visual Design Editor represents website pages and page types as collections of block elements: Blocks and Containers.
• All-new look & feel of backend UI — “Magento 2 backend” theme.
A block is a block-level HTML element on a page, which can be manipulated by the visual design editor. Regardless of whether the element has content or not, the design editor visually distinguishes it from other elements and provides necessary controls for manipulating it. In future: A block cannot contain other blocks.
A container, like a block, is a block-level HTML element which is visually distinguished and can be manipulated by the design editor. Containers don’t have own content, but consist of other blocks or containers. Containers represent area for “dropping”. Container stores information about sort order for elements within.