Welcome back to Atwix MageNews!
We’ve collected hot summer Magento updates from new releases to upcoming architectural changes and experience from conferences for you. Don’t wait, enjoy the post and don’t forget to share it with your friends!
We are starting 🙌
Not to Miss
Magento 2.3.2 Available
Magento has released a new patch version 2.3.2 including fixes and improvements to previous versions: 2.2.9 and 2.1.18.
Magento 2.3.2 started to depend on crypto library Libsodium version 1.0.13 and higher. Now, it’s needed to make sure that the server has the right version of the library before installing the new version of Magento.
This release includes 75 security improvements. Starting from 2.3.2 these issues will be assigned by indexed Common Vulnerabilities and Exposures (CVE) numbers.
Performance improvements are also included and here are some of them:
– after refactoring the way of concurrent access to the block cache storage, page response time under high load has been improved by 20%
Besides that, version 2.3.2 is packed with a huge number of quality improvements and fixes. Here are just a few of them highlighted:
– Braintree payment method became available for checkout with multiple addresses
– Amazon Pay integration complies with the PSD2 directive
– The checkout page now provides the ability to search addresses instead of listing addresses only on the Select shipping and billing address steps, which is extremely helpful if the customer has hundreds of saved addresses
– Module list in config.php became more determined and stopped showing a lot of changes when the module list is changed
– Magento supports Zookeeper as a Cron lock provider to prevent duplication of job executions
The latest versions of Magento Commerce and Magento Open Source are now available. Release highlights include security, performance, and productivity. More information: https://t.co/qN4QkB7kZz#MagentoCommerce #MagentoDevelopers pic.twitter.com/DfR3aJNQrI
— Magento (@magento) June 25, 2019
– [Magento DevDocs] Magento Open Source 2.3.2 Release Notes
– [Magento] Magento 2.3.2, 2.2.9 and 2.1.18 Security Update 1/3
– [Magento] Magento 2.3.2, 2.2.9 and 2.1.18 Security Update 2/3
– [Magento] Magento 2.3.2, 2.2.9 and 2.1.18 Security Update 3/3
– [Github] Make the module list more deterministic
– [Nexus] PSD2 (the second Payment Services Directive) explained in 3 minutes
– [Magento DevDocs] Configure the lock provider
New Magento Merchant Docs
Magento has rebuilt the MerchantDocs using the same stack technologies which are currently used for DevDocs (Jekyll-based static website generation). The new resource stores guidelines for Magento Open Source, Magento Commerce and B2B modules. The MerchantDocs will be also opened for community contributions soon.
— Magento DevDocs (@MagentoDevDocs) June 27, 2019
Magento Coding Standards on Marketplace
Magento is going to use Magento Coding Standards version 3 in Magento Marketplace Extension Quality Program starting from July. These standards will affect automatic static code checks that are applied on Magento Marketplace modules and bring two different levels of sniffs: warnings and errors which will be updated with different frequency. Check out new standards below and make sure your modules are compatible with them.
Magento kicked off a brand new glossary project where you can find list of terms and words that are used in Magento products. Magento powered the Glossary by GatsbyJs, using it as a JS static-website generator. And now this project is officially open for community contributions.
We have just released a brand-new version of the Magento #Glossary!
Our super slick new Glossary utilizes enhanced search functionality, an improved user experience, bundled terms based on subject matter, and a simplified interface.
Behold its glory! https://t.co/JyPb7O7Blo
— Magento DevDocs (@MagentoDevDocs) June 20, 2019
Goodbye, Magento 2.1
Magento 2.1 has reached its End-of-Support. Make sure you are updated.
As a result of v2.1 reaching end-of-support https://t.co/6ns7qhTmbA we are no longer accepting v2.1 PRs.
We will review existing v2.1 issues/PRs in the coming weeks.
Keep those non-v2.1 contributions coming! ✌️
— Magento DevDocs (@MagentoDevDocs) June 30, 2019
There were three big conferences in the Magento Community: Meet Magento Germany, Meet Magento UK, MageTitans NL and ES. We’ve collected all publicly accessible presentations for those who could not make it to the events.
– [thephp.cc] Stefan Priebsch – Personalization and Performance
– [SlideShare] AOE – Flamingo – Inspiring Commerce Frontend made in Go
– [Yireo] Jisse Reitsma – How Magento extensions will fit into PWA
– [SlideShare] Divante – How is Possible to Grow from On Site to Worldwide Ecommerce (Senetic Case Study)
– [Dropbox] Antonija Tadic – 10 tips to get the most of your dev team
– [SlideShare] Dan Coleman – From Bigamy to Polyamory: Managing Complex Agency Relationships
– [GoogleDocs] John Hughes – Stop refreshing the indexes
– [GoogleDocs] Willem Wigman – Building a React checkout for M2
– [Github] Ivan Chepurnyi – Building Cluster Application in Pure PHP for Magento 2
– [Yireo] Jisse Reitsma – How can we enforce better Magento extensions?
– [GoogleDrive] Michiel Gerritsen – Getting started with testing in Magento 2
PWA on Magento Commerce Cloud
Magento added a detailed instruction on how to install Magento PWA for the existing Magento Commerce Cloud projects.
– [Magento PWA Docs] Magento Cloud deployment
Replaced Unused Modules
Jisse Reitsma created a composer metapackage that can automatically disable Magento Open Source bundled modules which are rarely used. The approach is based on the integer_net investigation in that topic that we’ve reviewed in our MageNews April edition.
– [Github] Magento 2 removal of all optional modules
Magento has announced a technical vision for a new Storefront API. Performance is the main reason for this proposal. New API should support batch operations and should be stateless. In the near future, we will have Storefront API separated from Magento Admin APIs, they also may rely on different databases according to the current technical vision. Below you can find how the implementation of a new API can look like for Product Search API and other.
Designing new Storefront APIs for querying #Magento data we came to the necessity of getting Community feedback on should we introduce 2 dedicated APIs for Search (full-text search) & Filtration of entities data (i.e. product) or use 1 generic?
— Igor Miniailo (@iminyaylo) June 13, 2019
New Checkout Architecture
Magento Architecture team has started working on a new design for checkout workflow in GraphQl API. The idea is to try to separate the concerns of Shopping Cart, Quote and Order.
The Shopping Cart is going to be a container for products that the customer wants to buy and it will be dependent on the Catalog.
The Quote is going to know everything about totals and will be dependent on Shopping Cart. The Quote is going to still be used to create the Order. The Order is going to be dependent on the Quote.
This is how Magento design direction looks like. Find more information below:
#Magento people, should we invest more time and resources in the new Checkout Flow presented today?
Cart -> Create Quote(-es) -> Order(Quote)
– Cart depends on Catalog
– Quote depends on Cart and not Catalog
– Order depends on Quote and not Cart or Cataloghttps://t.co/A7q9GejMUd
— Igor Miniailo (@iminyaylo) June 19, 2019
Cron Should be Improved!
Cron feature also got its proposal to be improved. The proposal includes “out of the box” Cron job multi-threading which should increase the reliability of business-critical operations and make them less dependent on each other. The proposal also takes care of Cron user experience including job visualization, improved logging and alerting and more control over job executing like the ability to stop or retry failed jobs.
Find the proposal link below and don’t hesitate to jump into the discussion.
– [Github] Cron proposal
Upcoming Events. Don’t Miss!
Make sure to be the first for our August MageNews digest – subscribe to our blog to not miss a thing.
See you in a month!