Magento 2.x Features

By | June 8, 2014

As technology is getting update and so Magento is also getting update with new version Magento 2.x with New features ,components,Faster Scalability and More user friendly.

Component changes

  • Removed Some payment Method and bundled Community Modules
  • Removed/Ceased: Mage_Oscommerce,Mage_XMlConnect,Mage_DataFlow,Mage_Compiler

Functional Changes

  • Theme configuration: simple into one field
  • Enabling Profiler: handled by bootstrap
  • Customizing Email Template : no more relation to locale
  • Session Time out : Cookie lifetime(No more cookie life time)

File Structure Modularity
In Magento 1.x
app/deisgn/<area>/baase/default
skin/<area>/base/default
js/
app/locale/en_Us/template/email/*.html

In Magento 2.x
app/code/<pool>/<module>/view/<area>
same as above (no distinction)
same as above
app/code/<pool>/<Module>/view/email/*.html

File structure :Root Items
Was in Magento 1.x

  1. errors
  2. includes
  3. js
  4. media
  5. pkginfo
  6. shell
  7. skin
  8. index.php,cron.php,get.php
  9. bootstrap logic scartted across entry points

Was in Magento 2.x

  1. pub/errors
  2. n/a
  3. pub/js
  4. pub/media
  5. n/a
  6. dev/shell
  7. app/design/<appropriate theme>
  8. index.php,pub/index.php,pub/cron.php
  9. app/bootstrap.php

Frame work naming
Was in Magento 1.x

  • Mage::getModel(‘catalog/product’);
  • getTableName(‘admin/role’)
  • customer,checkout

Was in Magento 2.x

  • Mage:getModel(‘Mage_Catalog_Model_Product’) (real class name)
  • getTableName(‘admin_role’) (real table Name)
  • Mage_Customer,Mage_Checkout (Fully Qualify module names across the board )

Frame Work Configuration

  • Eliminated Excessive Section (up to 20% of all config.xml)
  • Move out some of the file to specialized files
  • simplified rewrites mechanism
  • Added merging mechanism that allows XMl-Schema validation (implemented for new types of configuration)

Frame Work Significant Other

  • Controller : formally separated routing of application areas
  • View: Unlimited theme fall back hierarchy
  • Introduced container (Structural elements in layout in addition to blocks)
  • Eliminating skins (only themes remain) eliminating packages physically from the file
  • Managing themes and design packages in entities in database
  • decoupling controllers from layout through universal “context” engine
  • Migrating to Jquery
  • Model service Layer
  • Improving Performance for API routing and granular loading of WSDL for only requested resources

User Experience

  • Information Architecture of the menus
  • Product creation flow
  • Taxes UX
  • Navigation ACL
  • Backend usability and UI

Magento tools

  • Migration tools to assists data and code from 1.x to 2.x
  • applications/ components /themes deployment (installation/ upgrade as new tools)
  • Zend Framework 2

Lot more to come…..

Leave a Reply