Magento DevBlog

We are unveiling a new process to fast-track Marketplace extensions using our new open-source tool, the Magento Semantic Versioning Checker (SVC).  Check the article for details on installation and use of SVC.

At Magento, we feel happy and privileged to have a community so supremely dedicated to growing merchant experiences. Since launching our new Marketplace, within a few short years we are well past the 5,000 extension mark. However, it gives us a unique challenge because a lot of those extensions, for various reasons, are abandoned or cannot be supported well enough to be reasonably current. 

In this exciting edition of “What’s happening with Magento Marketplace and the Extension Quality Program?” we will talk about end of support life for 2.2 CE, shared package compatibility selection and Page Builder compatibility enhancements

The Magento Marketplace Team strives to enable you, the developer, to create Marketplace extension submissions (via Developer Portal) that pass the EQP submission review on the first attempt.

In an effort to encourage customers to use supported versions of Magento, the Magento Marketplace is implementing a new policy for extensions, themes and shared packages compatible with versions of Magento that have reached the end of their support life.

Do you have Magento 1 extensions listed on Magento Marketplace? Do you want to migrate those extensions to Magento 2? Then read on.

Magento Commerce has grown by leaps and bounds with the support of a loyal and very passionate developer community.  We continue to see strong demand from merchants for top quality extensions. The Magento Marketplace team is very happy to announce that in addition to allowing all developers to request a Magento Commerce development license we're now enabling you to request access to a Magento Commerce Cloud sandbox account. 

They say, “Feedback is a gift,” and the Magento Marketplace Product team agrees. They started hearing from developers in the Magento community that process flow and usability concerns were keeping them from submitting extensions to Magento Marketplace. The mission of Marketplace is to provide Magento merchants access to authentic, high-quality extensions and themes to enhance their ecommerce sites, so this issue had to be addressed head on.

Keeping in line with our efforts to improve the quality of all extensions on Marketplace, as of 1/2/18 we will be implementing Varnish cache validation during Technical Review for all M2 submissions.The Varnish test verifies products do not break Varnish caching when in production mode. 

In the effort of continuous improvement, the Marketplace Team is proud to announce the implementation of a new submission path for patch releases.

Start selling on Marketplace! Magento Connect to close September 15.

The Magento 2.2 launch is quickly approaching and that means that Magento Marketplace’s Extension Quality Program (EQP) will soon start accepting extensions and themes compatible with Magento 2.2, even before the product officially launches. 

You can buy extensions from the online Magento Marketplace (marketplace.magento.com) and they appear in your Composer repository for download (repo.magento.com), but how does this work behind the scenes? Why do I need to go through Marketplace to get free extensions, but not to get Magento Community Edition (CE)? And why does Magento Enterprise Edition (EE) appear only after I pay? This post describes the relationship between the Marketplace online store, the Composer repository, and the entitlements that link the two.