Magento 2.0 Developer Common Questions & Responses

Magento 2.0 Developer Webinar Questions & Responses (direct from Magento)

Q: Does Magento 2.0 also support HHVM/HipHop?

Our Magento 2.0 general availability release code is compatible with HHVM, which means our main and critical test flows pass successfully on Magento 2.0 installed with HHVM. Further support of this technology depends on community interest and HHVM’s performance relative to other technologies.

Q: Does Magento 2.0 also support PHPFPM?

Now that PHP7 has been released, we recommend you consider installing Magento 2.0 on this version to maximize your performance results. Official Magento support for PHP7 will happen in January 2016. PHPFPM, as one of the most popular ways to install PHP and connect to web-servers, is supported.

Q: Is there a planned official Magento 2.0 development vagrant box or some sort of virutal machine to help quickstart development?

We have an officially-published Docker image that demonstrates how to install and configure Magento 2.0 to achieve the best performance in production mode that can also be a good starting point for development. You can find this image on GitHub at:

Q: Do you have a suggested high availability, highly scalable architecture?

Not at this time, but we will share recommendations and best practices as they are developed.

Q: What are the actual application speed gains without Varnish?

In order to compare Magento 1.x against Magento 2.0 without Varnish we propose that you take a look at the checkout, shopping cart and cart operation performance results, as all these scenarios are not cacheable by Varnish and demonstrate Magento responsiveness when it comes to pure code execution.

Q: Can someone explain more about asynchronous order creation please?

This feature was introduced to resolve resource usage conflicts between order management operations on the backend and checkout operations on the storefront in periods of high load, as well as to speed up the order creation process on the last step of checkout.

With this mechanism, order data from the checkout flow is saved into one storage, while order management operations leverage other storage for read operations. Checkout orders asynchronously move to order management orders storage. This isolation means that the load on checkout does not affect responsiveness for order management.

Q: Will there be any possibility of deferring JS and CSS to the footer/bottom of the page?

Magento 2.0 already introduces lazy evaluation of JavaScript as a part of the JS bundling feature. This way, we reach the same effect of avoiding parsing and evaluation operations that can be reached by moving JS to the bottom of the page.

The styles portion of Magento 2.0 is not comparable to the size of JavaScript, thus deferred processing of styles by moving them to the bottom page is not expected to bring significant performance improvements. Styles and JavaScript can also be moved to the bottom of the page by layout definition.

Q: Is the JS/CSS minification going to be similar to the existing method in 1.13 where clearing JSS/CSS cache results in deleting the media/js and media/css directories completely rather than just the files? 2

In Magento 2.0, activation/deactivation of client side performance features (including minification and bundling) requires you to re-run the static content deploy process. Comparing to the Magento 1 flow, you don’t need to remove your directories manually and wait until minified files are generated during customer requests. Instead, we provide an easy-to-use CLI tool to run this process in one call and guarantee all client side content preparations will be done in advance before the first call from the client side.

Q: I saw that you guys added composer into Magento 2.0, does this affect the development environment in the way I can use composer and install other php packages or is it just a part of the main Magento framework in general?

You can use Composer as you would in any other project by adding necessary libraries through “composer require” or in the root “composer.json.” Magento’s use of composer is independent of other PHP packages which may use composer.

Q: I’m new in Magento (coming from other platforms such hybris), Most of the forums recommends learning Magento 1 first, then Magento 2. Do you think this is necessary or can I just start fresh in Magento 2?

We recommend starting from Magento 2.0 as this will give you a better understanding of core development principles. Magento 2.0 documentation has better coverage of use cases and workflows and uses many coding patterns that are not part of Magento 1. Additionally, there are also aspects of Magento 1 that do not carry over to Magento 2, so you would waste time learning some things you can’t apply in Magento 2.0.

Q: Where we can get documentation on how to use PHPUnit cases for our custom extensions development?

Currently, there is support for Unit Tests on a per module basis, so you can include unit tests in your module. While this is not explicitly documented right now you can look at any core module as an example (e.g.,

Q: Hi! There is any improvement planned around the current resource setup system? Something more scalable like in Magento 1?

If you are referring to InstallSchema/Data classes, no improvements are planned in the near future. Current support allows flexibility in implementation of upgrades. Feel free to submit your proposals to Magento GitHub (please, include details of your use case).

Q: How can we test our module in Magento 2 with test cases?

We recommend using the Magento Test Framework for testing. Information can be found here: In addition, there are some helpful “How To” links on testing here:

Q: MTAF is it same for both?

No. The framework is different between the platforms.

Q: Are these figures for Community version or Enterprise Edition?

The results reported were for Enterprise Edition. 3

Q: Are these new benchmark speeds based on tests that include Varnish sitting in front of it?

Yes. They include Varnish which is part of our recommended application configuration and supported out of the box by Magento 2.0.

Q: Is there any way/tools available to convert Magento 1 extensions to Magento 2.0?

There are tools written by the community that can help and we are developing additional ones that will be available in Q1 2016. However, we encourage you to examine your extension closely to insure that it fully leverages the new features of the Magento 2.0 platform.

Q: Is there a way for me to know (from the marketplace) if an extension is suitable for me to extend a certain feature or function? I often need to extend Community Edition to just add one missing feature from Enterprise Edition but a customer won’t pay for an Enterprise Edition license for just that.

All of the extensions in the new marketplace will go through a vetting process by Magento, however it will be up to you to determine whether the extension fulfills your customer’s functional needs.

Q: Are there any improvements for LESS compilation?

We currently do not have LESS compilation improvements on our product roadmap but would welcome community generated pull requests on any aspect of our development tooling.

Q: How do we make a POST request to Magento 2.0 API using Java with or without Authentication? Authentication can be Token based or Oauth.

Please see the following articles in the developer documentation for more guidance in these areas. In general, our RESTful APIs are agnostic about what language or tool is used to generate the request provided that the request is well formed.

Q: Is there an eBay integration to Magento 2.0?

Not at present time. M2E is in the process of porting their extension to Magento 2.0 and there are also other services that will soon support syndicating products to eBay listings. Look for those on the Magento 2.0 page in Connect.

Q: What is the best time to move from Magento 1.x to Magento 2.0 for merchants?

Merchants new to Magento can start immediately on Magento 2.0. Existing Magento 1.x merchants should weigh their business goals, the benefits of moving to Magento 2.0 (like significantly better performance, scalability, enhanced platform flexibility, and an improved shopping experience), and the availability of key extensions when making their decision. Magento will continue to support Enterprise Edition 1.13 and 1.14 for 3 years from the Magento 2.0 GA date, so merchants have the flexibility to select an optimal time to upgrade. When you are ready to migrate, there are data migration and code migration tools available to help you with the process.

Q: Does the platform allow video overlays that fade out into a product image?

Not at this time.

Q: Can Magento 2.1 support MariaDB? 4

We do not support MariaDB per terms of our support contracts. However, we appear to be compatible with MariaDB at the moment. We welcome PR’s from the community to maintain this compatibility.

Will you in the future work on closer integration with Connect via the Magento Admin interface?

Yes we have work in our longer term backlog.

Does the data migration tool work for configurable products?

Yes, it works for all product types.

Where are the Magento Sample Models Located?

You can find the Sample Models at

Will Magento 2.0 be patched to support Elastic Search?

No. Magento 2.0 will not be patched. However, Elastic Search will be added as a Magento Enterprise Edition feature in 2.1 and will be enhanced in releases beyond 2.1.

Which of the presented features are Enterprise Edition vs Community Edition?

Of the features covered in the Magento 2.0 update section of the webinar, only the Queue Framework is a Magento Enterprise Edition-only feature. For the roadmap themes presented in the webinar, staging and preview and improved segmentation and personalization will only be available in Magento Enterprise Edition. Aspects of improved search, enhanced CMS, and improved promotions will be available in both Enterprise Edition and Community Edition.

Q. As a dedicated Magento development agency, how do I become partner?

Please work with the Magento Partner Program. There is information about the program available here:

Q: Where do I find the Magento Marketplace coding standards that you will be comparing me to?

The list of the rules is available at

Q: Is there a PHPCS ruleset available for validating Magento 2.0 extensions with the same checks applied when extension are submitted to the Magento 2.0 marketplace?

The list of the rules is available at

Q: Are pricing constraints going to be established for the new marketplace to keep lower-priced modules out?

There are no limitations on the price of extensions. Developers can choose a price that fits their extension and business plan.

Q: Are developers (not solutions partners) able to know who downloaded their module in the new marketplace?

We are going to provide the MageIDs of customers who purchased your products in the Marketplace. Although not available at Marketplace launch, we are building a feature that will enable developers to communicate via a Marketplace messaging system with customers who purchased their products in the Marketplace.

Q: Will the new marketplace allow for free modules as opposed to Magento Connect?

Free modules will still be available in the new Marketplace. All modules, free or paid, will be reviewed for quality. Those that meet our standards will be included in the Marketplace.

Q: Will there be a standardized way to ensure a module purchased from the Marketplace is being used legitimately (for example on a specific domain)?

We are working with Solution Partners and extension developers to understand how we can better protect their code, while still maintaining our open and flexible platform.

Q: will there be any code check for Magento 2.0 extensions before approval?

Each submitted extension is going to go through a technical review to ensure the code meets Magento standards. See more info here:

We have documentation to help you to create a correct package structure. The Quick Start technical guide to the Marketplace includes topics like Intro to Composer and How to Develop/Package components and is accessible at:

Q: Will it be possible to sell extensions through the new Marketplace, like on AppStore? Customer pays Magento and Magento pays to developer?

Yes. Developers will be able to sell via the new Marketplace.

Q: Will the Magento 1 extensions still be available in the Magento Marketplace?

Yes, they will be available in the Magento Marketplace. We will be inviting providers to migrate their extensions in phases to allow time to review each extension and provider.

Q: On the current Connect there are a lot of extensions which are essentially abandoned. For the new marketplace will there be support requirements which would remove the listing if these aren’t met?

Extensions available for sale in the Marketplace must be actively supported or they will be rotated out of the Marketplace.

Q: Can you explain in some more detail about the marketplace model that will be put in place? Will it be a commission based model for example?

There is no fee for submitting and listing products or services in Magento Marketplace. All product sales in the Magento Marketplace are subject to a 70/30 revenue share split, with 70% of the revenue going to the provider and 30% going to Magento. This shift to a new business model will allow Magento to continue to invest in marketing Magento Marketplace and increase extension providers’ app business.

Q: What is the release date for the new Marketplace?

We are planning the official launch of Marketplace in early 2016. More details will be available as we get closer to launch.

Q: Will there be a (limited) beta to the Marketplace for merchants, to critique ease of installation and evaluate the quality of code reviews? 6

We will have a limited beta release of the Marketplace before the general availability (GA) release of the Marketplace.

Q: Will the marketplace have other ways of uploading new versions of extension? For example through direct download from GitHub/BitBucket and using the tags/releases for the versions on the Marketplace?

Yes, we are going to work on this for future releases.

Q: How will quality and discovery be verified on the ioncubed version of the module that developers are allowed to upload?

Providers must first submit a non-encrypted version of their extension for the basic check. If the extension passes the basic check, providers may choose to list and sell an encrypted version of their extension. The extension may include a notation to indicate that it contains encrypted code. We cannot verify that the encrypted code is the same as what was submitted for review, but we will be tracking post-purchase feedback and any developers that post encrypted code that is different from the code submitted for review may be subject to suspension or termination of their ability to list extensions in the Marketplace.

Q: Is the Marketplace curation only for partners like it was for Connect?

Marketplace curation will cover all extensions, regardless of whether or not the extension was built by a partner.

Q: What’s new in Magento 2.0?

Magento 2.0 is our next-generation platform that offers a much more flexible and advanced architecture, enhanced performance and scalability, an all-new Admin UX and business tools, and an improved user experience with a new checkout, easy product video integration, and 2 new responsive themes. You can learn more about Magento 2.0 from our announcement blog post at

Q: Have you, or are you going to, work on a closer integration for content supplied through the Admin interface, and CDNs like Amazon CloudFront? E.g., if I upload an image in the CMS, will it replicate to a CDN automatically and use the CDN URI instead of the Magento URI?

This is currently not under active consideration, however we may explore options in this area within the next 6 months.

Q: When can Magento 1 to Magento 2 Migration script improvements & updates be expected?

We are always looking for feedback on the current tools for improvement. Code migration tools are under active development, due for release in 2.1. No significant data migration tool work is planned beyond what is already delivered.

Q: Can the built in Magento 2.0 product import deal with all types of products (downloadable, bundle, etc.)?

Yes it can.

Q: May I see a launched site list for Magento 2.0 please?

You can learn more about some of the merchants using Magento Enterprise Edition 2.0 at and in the 7

video posted at

Q: Hi! What’s the plan for B2B module?

Magento is already used by many B2B merchants and is the top platform for the Internet Retailer B2B 300 for 2015. We are looking to make it easier to implement Magento B2B sites in 2016.

Q: When will Magento 2.0 will be available with Elastic Search?

We anticipate that Elastic Search will be included in the Magento Enterprise Edition 2.1 release scheduled for the first part of 2016.

Q: Will there be any workflow improvements to the CMS, e.g. Editor, Reviewer, Publisher? Will static blocks be getting any of the flexibility you’ve mentioned coming to CMS pages?

We are reviewing CMS functionality in Magento for the 2.2 release, but have not finalized the exact feature list at this stage.

Q: Do you have a list of hosts that are “approved” or “certified” (especially for Enterprise)?

Check out the Magento Hosting Partners listed in the Magento Partner Directory at

Q: What options for Magento 2.0 development training will be introduced, other than the three slideshow sets? Will there be training courses?

We currently have 3 on-demand Magento 2.0 courses available (see Magento U at Planning for our 2016 course development roadmap is underway and we will share information on new courses in Q1.

Q: I want to know about the multi-warehouse inventory? It was not in Magento 1, will it be in Magento 2.0? M2?

Multi-warehouse inventory is not currently part of Magento 2.0, but we plan to add this capability to Magento Enterprise Edition in 2016.

Q: Any improvements regarding reindexing?

Performance and scalability have been improved across the board in Magento 2.0. Magento Community Edition 2.0 also includes improvements in the area of reindexing that are consistent with optimizations made in previous Magento Enterprise Edition releases.

Q: Hi I’m Magento Front End Developer – What about the External libraries integration, like Bootstrap and Fontawsome , etc.?

Magento 2.0 tries to be agnostic to various front end libraries to give full flexibility to developers. For this reason we are not planning to incorporate Bootstrap or Fontawsome into the core product.

Q: What about shared basket? Will be possible to share a basket over multiple stores again?

There are no known changes to the Magento 2.0 checkout that could seemingly prevent this. But, this is not a use case we have tested specifically for yet in Magento 2.0.

Q: Will the Enterprise Edition licensing fees be different for Magento 2.0 vs Magento 1? Have Magento 2.0 Enterprise Edition pricing details been announced? Will annual Magento Enterprise Edition costs stay the same? 8

Magento Enterprise Edition is available for an annual subscription fee that is tiered based on the amount of GMV that will run through the Magento software. You can work with a Magento sales representative to determine pricing for your business or client.

Q: Is the 1.x support end of life also true for security releases?

Yes, Magento will continue to provide security updates to Magento Enterprise Edition 1.13 and 1.14 for 3 years after Magento 2.0 general availability.

Q: How to migrate from Magento 1 to 2 ?

To migrate from Magento 1.x to Magento 2.0 you need to port all of your data and upgrade your extensions, themes and customizations to take advantage of new development approaches and technologies that offer a much greater ability to customize and scale your site. We created the Magento 2.0 Data Migration Tool to help you efficiently port all product, customer, and order data, store configurations, promotions and more to Magento 2.0. A white paper describing the tool and the data migration process is available online. Magento 2 Trained Solution Partners can help you update your themes and customizations and documentation is also available online at Code migration tools, which are helpful when you need to upgrade a large number of customizations, are available on GitHub. Magento has been actively working with the developer community to ensure widely-used extensions are updated and available for the new platform. You can see a list of available extensions in Connect.