At Magento Imagine in May of 2019, Adobe shared news about the upcoming release of Magento Open Source and Commerce 2.3.2. This included a “sneak peek” of what M2.3.2 entailed.
Magento Open Source & Commerce 2.3.2 was released on June 25, 2019, alongside of updates to additional versions of Magento:
– Magento Open Source and Commerce 2.2.9
– Magento Open Source and Commerce 2.1.18
– Magento Open Source 126.96.36.199
– Magento Commerce 188.8.131.52
– Magento 1.x SUPEE-11155 Patch
– These new versions include urgent security enhancements to block now public vulnerabilities, such as sensitive data disclosure issues, remote code execution vulnerabilities, and cross-site scripting, among other security concerns.
– According to another Magento Forum post by Lori, M2.3.2 will require libsodium version 1.0.13 or later. The latest version so libsodum support stronger encryption, and are required to install Magento 2.3.2.
– For those Magento 1.x users that choose to install the SUPEE-11155 patch, be aware that there are reports of some bugs and incompatibilities that may require you to make some adjustments, such as if you had previously installed the PHP 7.2 support patch for Magento 1.
As this is only an incremental release, we weren’t expecting anything too revolutionary, but here are some highlights of included features and improvements:
– An expansion of GraphQL API coverage to include the cart and checkout
– Caching for GraphQL queries
– Improvements to the loading speeds of storefront pages*
– Asynchronous operations in the Magento Admin
– Amazon Pay PSD2 Compliance
– Google reCAPTCHA module for PayPal Payflow checkout
– Storefront accessibility improvements
– The release of a migration module for Magento Commerce users switching from the Bluefoot CMS to the new Page Builder**
Overall, this release has a total of over 130 product quality improvements, over 75 security improvements, and over 200 submissions by the Magento community at large. This has led to what Magento is reporting as a “20% improvement to storefront page-load times… and up to 90% improvement in category browsing for merchants with large catalogs.”. Magento has also reported that “Several actions are now performed as asynchronous background processes, allowing administrators to continue working while tasks are being processed in the background.”
*Even with core improvements, Magento 2 is still an advanced platform that benefits greatly from speed optimization efforts. Consider running a Magento Speed Test, deploying a CDN like Cloudflare for Magento, and leverage caching tech like Varnish for your M2 store. If you haven’t migrated to Magento 2 yet, be aware of the differences in hosting requirements between Magento 1 and 2, and consider if you’d be better off with a Magento 2 optimized dedicated server(s) or cloud server(s) for your particular instance of M2.
**The Magento Page Builder module will only be available to Magento Commerce users for the foreseeable future, although members of the Magento team have publicly acknowledged that this will likely become available to Magento Open Source users in some capacity, at some point in the future.
months of additional investment, but in the end, we’re extremely proud of the capability. Ok, so PageBuilder is commercial software. We have talked rather directly about our desire to provide it as a paid extension for OS clients, and that is still very much the intention.
— Jason Woosley (@jasonwoosley_mg) May 17, 2019
While you’ve just read a lot about these releases, keep in mind that according to Github, the Magento 2.3.2 milestone was closed on May 8th of 2019, with a total of 356 issues closed. Bear in mind that, as always, you should undergo proper user acceptance testing prior to pushing any updates from your dev or staging server to your live website.
Also, keep in mind that M2.1 reached its End of Life on June 30 2019, and M2.2 goes end of life at the end of 2019.
… and, if this post wasn’t already full of spoilers, stay tuned for more news about Magento 2.4, which is expected to release in Q1 of 2020.