Magento 2 is in development and it’s exciting to hear the idea’s and blueprints set out, main focuses are on improvement of performance, upgradability, maintainability and scalability.
One of the major focal points of the upgrade is to make it easier for developers to create modules and develop the magento store meaning it will be more cost effective for customers using Magento.
Secondly the modules that are on 1.* version’s of Magento will require to be converted into the Magento 2.* format. There are quite a few differences on the new platform that will require a qualified developer. The magento team are going to document this so your developer will know what to do.
The Big Changes That Are Happening to Magento 2
- Migration to jQuery
- Skin will be moved into themes
- New backend theme for improved usability
- Customising Email template no longer related to locale it is now managed in the module
- Indexing improvements
- Major change to class alias’s: Mage::getModel(‘catalog/product’) is now Mage::getModel(‘Mage_Catalog_Model_Product’) this has reduced the configuration up to 20%
- Removed some modules including payment gateways (these will most likely to be available as community extenstions
- Unlimited theme fallback
- Removed Mage_Oscommerce Mage_Xmlconnect Mage_Dataflow and Mage_Compiler
- getTableName will use the table name so getTableName(‘admin/role’) = getTableName(‘admin_role’)
- Autodiscovery of API resources instead of configuration
- Remove auto installation of modules, there will be a separate entry point for installation
- Simplified licence/copyright notice in file headers
- Theme configuration is now only one field in the admin area
- Profiler switch is not in bootstrap not in the admin area
- The session lifetime is no longer linked with the cookie lifetime
- Improved performance of the API along with version support
- Improvement of the navigation menu
- Introduction of container blocks
- Investigating Zend framework 2 to be used.
- Dismantling the Aminhtml module
- Group modules into components which is a set of modules that are related to each other
- Requirement of PHP version 5.3
The File Structure
- app/design/<area>/base is now app/code/<pool>/<module>/view/
- app/locale/en_US/template/email/*.html is now app/code/<pool>/<module>/view/email/*.html
- skin/<area>/base/default is now app/code/<pool>/<module>/skin/view/*
- Folder called “pub” is essentially going to be the new document root that will contain these cron.php get.php index.php pub/index.php pub/cron.php
- errors = pub/errors, includes = n/a, js = pub/js, media = pub/media, pkginfo = n/a, shell = dev/shell
From Customers Perspective How Does Upgrading Magento 2 Impact Me?
The biggest issue with any Magento upgrade is retaining the database tables. Magento have in the pipe line migration tool’s that will do this so you don’t loose your important catalog, customer and order information along with other useful data.
There is quite a lot of changes in Magento 2 that will need testing in conjunction with any custom functionality that you have.
Not all the details are out for the Magento 2 upgrade and the release date is most likely to be announced this year, if you are interested in the potential of having your Magento upgraded please contact us