This is the first major release, which is dedicated to improving the Magento developer experience and embedding the development process in the popular PHPStorm IDE. Existing functionality was revisited and missing pieces were implemented to complete features.
Magento standards were taken seriously so that developers won’t see any failures during code review and submission to the Magento Marketplace. Developers don’t need to spend additional time reading and learning small details about Magento development. Your IDE will help with this by suggesting the correct way of doing it. The Magento PHPStorm Plugin includes a lot of shortcuts addressed to Magento Functional Testing, Require JS mapping, GraphQL, Plugin declaration inspection, code generation, and much more.
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 the5,000 extensionmark. 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.
Due to the Payment Service Directive PSD2 (see details on Magento devdocs) and the continued evolution of many APIs, a number of Magento core payment integrations risk becoming outdated and no longer security compliant in the future. To that end, many core payment integrations have been or will soon be deprecated and we are recommending a transition to their corresponding marketplace extensions.
Magento 2.4 became a perfect opportunity to proceed with backwards-incompatible changes that were waiting for years. WhenI was speakingat Magento Conferences aboutreplacing inheritance with composition, I was not aware that I was going to be a part of this history. One such change wasthis Pull Requestandits followupintroduced by Vinai Kopp. Althought this change wasveryexpected, these PRs were not merged.
At the begining of 2020 Vinai encouraged me tocontinue the workon Controllers decomposition using his contribution. With his continuous support and tremendous work of Lena Orobei - together we finally delivered one of the biggest architectural changes towardsdecomposition of Controllers.
Thanks to the collaboration between comwrap GmbH, Balance Internet and the Magento Community Engineering team, Asynchronous / Bulk API functionality was first delivered in Magento 2.3.0 as a new API that makes possible the execution of operations asynchronously using RabbitMQ (which is delivered out of the box with Magento since version 2.3.0 as well). Details and history of Asynchronous / Bulk API are described in a previous DevBlog post by Oleksandr Lyzun. In short: a user sends the same synchronous request but in response only receives a bulk_uuid. This request goes into the RabbitMQ queue and consumers in Magento process them in order. Using this bulk_uuid, users can monitor the request processing. One big benefit of bulk operations is that users can send different operations using only one request (e.g. create or update list of products).
2019 was a fantastic year for contributions and community involvement. During the year our contributors created over 8,000 pull requests across Magento GitHub repositories! Even more exciting is that over 8,500 were processed, meaning we made a significant dent in the backlog! We would like to extend a big thank you to all our contributors, maintainers and partners that did awesomework constantly iterating on Magento projects. We want to take some time and make some space in this post to look back at 2019 and highlight the amazing achievements of the community.
As a follow-up to the Squashtoberfest 2019 event we described a little while back, we wanted to share with everyone the list of our awesome contributors and winners from the event! We saw a ton of activity during October and are extremely grateful for everyone who contributed. A select number of you really went above and beyond and as a thank you we want to make and send you a limited-edition T-shirt commemorating the event and showing our gratitude.
Contributions to Magento Open Source or Magento Commerce are a powerful and effective way to strengthen the wider Magento community. Magento community involvement leads to the continuous improvement of the Magento framework; keeping it up to date with the latest development tools and best practices. We are grateful to all who participate in community projects to expand platform features and support the global community who use Magento.
Merchants running Magento Commerce 2.3.x shouldinstall the latest security update to helpprotect their stores frompotentialmalicious attacks thatcouldexploit avulnerability￼in Page Builder preview methods.This vulnerability could enable an unauthenticated usertoinsert a malicious payloadto a Merchant’s siteand execute it,which is whywe recommend installing this update.
This post describes changes made to the Mail library in Magento 2.3.3 and explains the actions that merchants and extension developers need to take to ensure that extensions that use Mail library compatibility with these changes.
We wanted to let all open source software enthusiasts know that we will be running our annual Squashtoberfest event during the entire month of October. Every year in October open source communities around the world get together to collaborate and contribute to their favorite projects. For the pasttwo years, contributors to Magento projects during October have had a chance to win some cool swag from us based on their contributions.
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
On 9/5/19, you will be able to select if your submission is compatible with Magento Commerce on Cloud or Page Builder and once approved, those options will show up in the product details on Magento Marketplace.
To provide enhanced security for customers using older versions of the Magento platform, we are backporting a fix from the security patch we released on June 25 (Magento 2.3.2, 2.2.9 and 2.1.18 Security Update) to additional versions of Magento Commerce and Magento Open Source.
Experience Manager and Magento are seamlessly integrated using the Commerce Integration Framework (CIF). CIF enables AEM to access a Magento instance and bind the catalog data via GraphQL. It also allows AEM Authors to use Product and Category Pickers and a read-only Product Console to browse through product and category data fetched on-demand from Magento. In addition, CIF provides an out-of-the-box storefront that can accelerate commerce projects.
For Magento v2.3.1 and 2.3.2, this article provides information about an issue with scope-related APIs for Asynchronous / Bulk APIs. We provide a patch to resolve this issue for Magento Open Source, Commerce, and Commerce Cloud instances.