Do you want to keep track of Magento news but have no time for surfing the web?
We’ve taken care of this.
From this time on you can find the most important news of Magento 2 in one place (psss, you’re here already!).
Starting from Magento 2 beta and spilling over to Magento 2.3 version peppered with new features useful hints and tips – all this and much more info is gathered in one place. So, if you missed something important and couldn’t find it later, we’re happy to help you with this.
Stay tuned to get a greater understanding of e-commerce trends [will be updated].
DON’T MISS ANY IMPORTANT MAGENTO UPDATES!
BE UP TO DATE WITH OUR WEEKLY NEWS EMAILS.
WHAT’S NEW IN MAGENTO 2.3.1?
On March 26, we saw the release of a new v.2.3.1. What does Magento 2 changelog include?
Not everyone has enough time for diving deep into the latest Magento 2 release notes, therefore, we’ve gathered this shortlist with useful links you can go through in 60 sec.
Also, we want to admit that we’ve already checked most of our extensions for compatibility, as you could see it from our Monthly Updates post and integrated our Magento 2 Blog Pro extension with the Page Builder. Now you can apply numerous blog elements:
- blog post list;
- recent blog posts;
- blog posts tag cloud etc.,
for any place of a blog page using the drag-and-drop tool of Magento Page Builder (see how it’s implemented).
SO, WHAT’S INSIDE?
- 200+ functional fixes
- 500+ requests contributed by the community
- 30+ security enhancements
The community has greatly contributed to the platform version, thus, now you can use Inventory Management and GraphQL, Page Builder (Commerce only) and Progressive Web Applications (PWA) Studio (the last two are also released as independent products).
OPEN SOURCE & COMMERCE
LARGER ENHANCEMENTS FOR MERCHANTS
- Magento enhanced order creation workflow. Now there are no delays in editing billing/shipping addresses.
- Now you can upload PDP images larger than 1920 x 1200 and Magento won’t compress them.
- Enhanced the support for Elasticsearch. Now being enabled it returns only relevant products.
- Source Selection algorithm (SSA) option for distance priority, more info is here.
- Mass inventory transfers option was enhanced and now is stated to proceed faster.
The big option that differs Commerce from Open Source in this section is the Page Builder.
Finally, merchants can forget about delving too much into HTML and CSS with Page Builder integration. Find out what you can do with it here.
LARGER ENHANCEMENTS FOR DEVELOPERS
- New composer plugin for automating the upgrading process.
- PWA Studio – now you can use it. See more.
- GraphQL. See more. (Subscribe to our newsletter for not to miss our featured article from one of our Amasty leading developers!)
LARGER ENHANCEMENTS FOR SECURITY
- PRODSECBUG-2198 patch for critical SQL injection vulnerability. You can download the patch here.
- Though there were no confirmed attacks, Magento made 30+ security enhancements (as well as for v. 2.2.8, 2.1.17, 126.96.36.199, and 188.8.131.52).
Also, we should note the performance improvements that were primarily focused on handling customer accounts with 3000 addresses, infrastructure improvements, as well as enhancements related to bundled extensions and fixes.
To see a complete guide for the Open Source edition, please follow the link.
We are happy to inform you that the long-sought 2.3 version of Magento was released last week!
Here is what Magento says about the latest release:
2018 has been a big year for Magento, our merchants, and our community. We are excited to announce the latest version of the Magento platform to help continue that success into 2019. Magento 2.3.0 is here with new tools to help merchants fuel their growth while empowering developers to deliver on client expectations faster and more easily.
On our part, we can consume that a big part of the declaired features we covered have been successfully implemented. Now you can see all the details in the official release notes for your Magento Open Source 2.3.0 or Commerce 2.3.0.
AMASTY EXTENSIONS COMPATIBILITY WITH MAGENTO 2.3
Note: Before upgrading to the latest version, make sure you meet all the basic requirements. Also, as you know, Magento 2.3 goes with a number of significant changes that may influence the functionality of the 3rd-party solutions preinstalled on your platform. So, it’ll be a good idea to see the incompatible adjustments.
Here at Amasty, we’ve already tested the majority of our extensions and updated to work with Magento 2.3. We always try to provide our customers with advanced service and this case is no exception.
FRESH UPDATES ON MAGENTO 2.3 RELEASE
Magento keeps improving security and this time provides tools for control over caching and user verification.
Two-Factor Authentication for the Admin panel will include three methods:
- Google Authenticator,
- Duo Security,
- and Authy.
The second authentication stage can be configured to ask users to verify their login by means of SMS, Phone Call, Access Token, or One Touch.
One more security enhancement is the introduction of the Google reCAPTCHA service with its inbuilt mechanism for detecting malicious and SPAM-related activity. The reCAPTCHA tool will help merchants keep key pages secure from bots:
- Admin and User Login Pages;
- Registration Page;
- Contact Form;
- Forgot Password Page.
CACHE MANAGEMENT ACL
Magento 2.3 will also take on board a more advanced cache permissions module, which will let admins define the users that can both view and manage ‘Cache Types’. Magento has several cache types as ill-timed cache flush can damage the web store performance. Still, as the number of users grows a cache flushing policy is not enough to protect the web store from unintentional insider threats. Cache management now gets a more accurate approach and that is access restrictions.
So as not to wait for the Magento 2.3 release date you can access security functionality with Google Invisible reCAPTCHA for Magento 2 and 1. The module is designed with user convenience in mind so reCaptcha test appears only in cases of suspicious requests.
WHAT YOU SHOULD KNOW ABOUT MAGENTO 2.2.3 RELEASE
As you may know, Magento 1 security issues were addressed via security patches. Magento 2 doesn’t release the patches, instead the updates are coming with a new version of the platform.This release is all about security. Magento says that 35 security enhancements were added to 2.2.3 version.
Enhancements that help close cross-site request forgery (CSRF), unauthorized data leaks, and authenticated Admin user remote code execution vulnerabilities were implemented into the release.
You can see the list of enhancements here. Basically, you don’t have to do anything special about it – just install the freshest version to make your Magento 2 store safer.
WHAT’S NEW IN MAGENTO 2.2.2
- Advanced reporting
- Magento shipping
- Streamlined checkout
- Dotmailer integration
- Testing framework
The new feature provides access to order, product, and customer reports from the Magento 2.2.2 Admin (see Advanced Reporting for more information). Advanced reporting functionality is provided through integration with the Magento Business Intelligence (MBI).To use this, you will need three things:
- A real domain name.
- HTTPS with a valid certificate.
- Successful subscription to the Advanced reporting.
With the option you gain access to 20 reports and 3 dashboards about your store performance. Reports are updated daily and can be configured to show data for several different date ranges. Advanced Reporting is accessed via a link in the Magento Admin panel where the reports are delivered via a SaaS interface.
WHAT MERCHANTS SHOULD KNOW ABOUT MAGENTO 2.2 RELEASE
- Magento 2.2 Open Source (former CE)
- Magento 2.2 Commerce (former EE)
- Magento 2.2 Commerce Cloud (former EE)
PHP 5.6 SUPPORT IS OUT
Now PHP 5.6 is not supported for Magento 2.2. If you want to use this version, reconfigure your servers for PHP 7.1 use. And it’s not a bad thing – PHP 5.6 is dropping out of the web naturally, thanks to the new exciting opportunities of PHP 7.
NO DISABLING MODULE OUTPUT
The ability to disable module output has been removed from the admin area. If you disabled module output from Admin in a previous release, you must manually configure these settings. If you want to have the ability to disable the extension, learn how to do it here, or you can ask your developer to do this for you.
New release of Magento 2 includes the first third-party extension – Magento Social. This extension establishes a connection between your store and your corporate Facebook account and creates a page with products from your catalog. When shoppers click a product, they are redirected to the corresponding product page in your Magento store. You can read more about the extension and download it for free here.
Magento Social also allows you to create compelling and optimized advertisements in real-time. You can also automatically populate ads with product images and descriptions.
SIGNIFICANT SPEED IMPROVEMENTS
The new release includes substantial improvements to Magento 2 caching, image processing, and re-indexing, which basically means that your store will run much faster in general.
Here’s what Magento itself says about the new version:
We are pleased to present Magento Open Source 2.2.0 GA. This release includes hundreds of functional fixes plus a wealth of new features: a bundled extension, upgraded technology stack, performance gains from improvements in indexing, cart, and cache operation, and significant enhancements in platform security and developer experience. And check out the many community contributions! See Magento Open Source 2.2.0 Release Notes for more information.
AMASTY EXTENSIONS COMPATIBILITY WITH MAGENTO 2.2
As official Magento partners, we were privileged to have early access to Magento 2.2. In summer, we started to test and update our 70+ Magento 2 extensions so they become compatible with the new platform release.
Right now we are happy to say that the majority of Amasty extensions has been tested and updated to work with M2.2. Our main goal was to start the preparation in advance so we can provide our customers with M2.2 compatible extensions as early as possible.
MAGENTO 2.2 RELEASE: WHAT AMASTY EXPECTS
ALEXEY, CERTIFIED MAGENTO DEVELOPER
I do think that the Disable Output setting should be removed. It often confuses the customers, because they don’t see the difference with just disabling extensions, and it is causing a lot of issues. The number of support tickets we’re receiving on that issue is enormous.
What is more, I’ve seen a lot of confusion when it comes to changes in the production mode. Maybe it’ll be better to show a notification in the admin panel or at least an additional field to display the current mode. Very often the customers are making changes in the production mode and then don’t understand why they can’t see the changes on the website, or the site just shuts down.
Sometimes I really need a setting for disabling automatic logging out for cases when you log in under the same user, but in another browser. Now the automatic logging out is very inconvenient when you’re developing and testing the extension in several browsers, and I wish I could turn it off for a period of time.
And last, but not least – I’d really like to see more public methods in Magento 2.2, because it would give us more opportunities when it comes to changing their functionality.
PAVEL, MAGENTO DEVELOPER
Sometimes, when you dig deep into the code while building a complex extension, you can see things that are not quite perfect and are likely to be in the stage of development. For example, this functionality is not exactly what we see in the Magento 2.1 code.
That’s why I really expect that with the Magento 2.2 release we will see a clearer picture of where the code will be heading to in the nearest future. Also, it would be great to have the docs that are closer to the reality, and more examples from the github would be of great help to us, Magento 2 developers. The current github examples were updated a year ago, and only one of them was updated 6 months ago. A lot has changed in Magento 2 since then!
STAS, CERTIFIED MAGENTO DEVELOPER
Here’s the case I would like to see as solved in the new versions.
- Single-Store Mode is off, I’m going to change something on the website level, for example, disable the module output
- Turn Single-Store Mode off
- And we’re getting an unexpected result: the site’s behavior looks like output is off, but the advanced page will look like it’s on. The same applies to the other settings as well.
So, if Single-Store Mode is on, the platform should ignore the other settings.
As I know, currently we can add a condition to layout only using ifconfig, which is often insufficient. I think that it would be of great help to have something like ifclass=”Amasty/Model/Helper/SomeClass”, where the execute function could run any logic you want, returning true or false, and then the part of the layout with the ifclass could be added or removed depending on the result. Maybe this isn’t the best option when it comes to speed, but it’s just an idea of fixing the inconvenience.
A script for generating install data from a database table would be very effective when transferring extensions from Magento 1 to Magento 2 or when building Magento 2 extensions from scratch.
In general, here’s what I’m expecting from Magento 2.2:
- It would be great if the backward compatibility stays when going from Magento 2.2 to 2.3, and during similar upgrading.
- The current official documentation helps a lot, but I often see it could be more relevant and detailed, more of a CookBook.
- If the official Magento 2 guidelines say you shouldn’t use deprecated functions, then Magento 2 shouldn’t use them as well =) Being serious, I understand that it will be done in baby steps, because the platform is very complex and is heavily with each release.
- Of course, the speed is the area when there’s room for improvements.
LEONID, MAGENTO DEVELOPER
I’m really waiting for the possibility of adding the additional fields to checkout.
As for the PHP backend, everything looks great. We can add our own layoutProcessor, where we have the complete tree of checkout page elements, which are set from layout.xml and are loaded from the database. And we can be good with just checkout_index_index.xml as we have lots of settings for the checkout page elements.
But when it comes to saving, I’m often facing troubles. Each field has settings from JS when it comes to saving, and the only loophole I found is to use customAttributes for addresses. It’s strange to see such a great number of options and variants in the backend, and only restrictions from the JS side.
As with Magento 2 we’re getting certain code standards to follow, still some Magento 2 extensions are not quite following them.
Sometimes I find the code a little bit too hard to understand, and more detailed comments would really help. For example, EntityManager is a very useful thing, but it’s challenging to actually understand how it works – and I imagine how hard it is for developers which are not as experienced as the most of Amasty team members are.
Despite all this, I really like Magento 2 and eagerly waiting to see the new things than might come in Magento 2.2 release.
EUGENE, CERTIFIED MAGENTO DEVELOPER
In xml configuration, we can’t set validation classes for parameters with xsi:type=”text” (well, as for all the other, too). The only option available is required=”true”.
Something like this would be beneficial while creating, say, some widget options. I do hope this will be fixed in Magento 2.2.
<parameter name=”image_width” xsi:type=”text” visible=”true” validate=”validate-number” required=”true”>
<label translate=”true”>Image Width</label>
MAGENTO 2 UPDATES: SUMMER 2015
Find a vulnerability in Magento 2 and receive a prize from $100 to $5,000, plus you could boast of your discoveries after Magento 2 is released. Jokes aside, it’s a wonderful opportunity to work on a new and untypical project and contribute to the Magento community as well. And test your skills, too!
MAGENTO 2 MERCHANT BETA RELEASE: WHAT YOU SHOULD KNOW
- Magento 2 Merchant Beta is very close to what you will see in GA release later. It concerns both the look-&-feel and the functionality of the platform.
- Both the community and the Enterprise Magento 2 versions received features updates. Here’s a short list of major improvements with links to descriptions:
- Module version changes
- Performance improverments
- Multiple administrators
- Magento Admin improvements
- Checkout improvements
- Payment improvements
- Product attribute swatches
- Transactional emails
- Import and export
- Join directive
- Uninstall and backup
- The Magento Enterprise Edition codebase includes comprehensive scalability enhancements to the database, order management, checkout, catalog, and more. Improvements include asynchronous grid fulfillment, standalone database for checkout, compatibility with MySQL cluster, more concurrent admins for order, and product management and complete separation of store sub-systems.
- Magento team is engaged with a group of merchants and partners to test the Merchant Beta codebase via real-world implementations, so the GA release is all over ready and tested inside out.
- Magento team has conducted a webinar on the release, and the recordings will be available within a couple of days. We will update the post if anything new comes up! Until then you can see what the community members are talking about on Twitter. Stay tuned.
P.S. The PHP development team announces the immediate availability of PHP 7.0.0 Beta 1. This is the third pre-release of the new PHP 7 major series.
MAGENTO 2 RELEASE: FACTS AND RUMORS
Magento 2 was announced in 2010. The plans were to release it by the end of 2011, but now we have 2014 shutting its doors, and finally you can register for the Magento 2 Dev Beta webinar, while alpha version is available on github. It’ve been a long wait, some members of the community are not exactly happy with the things going all, but now it seems we have light at the end of the tunnel.
As <a class=”ProfileHeaderCard-nameLink u-textInheritColor js-nav
” href=”https://twitter.com/allanmacgregor”>Allan MacGregor once said on Twitter, Magento 2 is worth waiting. Although the new version of the e-commerce platform will definitely change the landscape, and both business owners and developers will spend time on transitioning, this release is a huge step ahead, which could strengthen Magento’s market share. The reasons of such a delay weren’t confirmed by any Magento or eBay employees, but these are the thoughts floating in the community:
- in 2011, Magento was acquired by eBay. It is very possible than many time and effort were spent on reogranization.
- Some people, including top management guys, left the company, which also might have brought some confusion into company’s processes.
- Consolidating the 3 development centers in Urkaine also took time and effort
- this is probably one of the most unpopular opinions, but the rumors where that the scope for Magento 2 was too broad to catch up with the other platforms.
Embarrassing that it took this long? Perhaps. My *assumption* is that bringing Magento, Inc. into the eBay fold took a bit of effort and time, the X.commerce platform took a lot of effort away, and eBay have redoubled effort to get M2 to market. It would have been nice to let the community and users of Magento know this, but that’s only possible in retrospect. With all this time left “open”, nothing has emerged to “disrupt” the Magento ecosystem, indicating to me that custom, powerful, OPEN ecommerce is still a hard problem which Magento 2 is likely to solve even better than Magento 1. Read more
Now let’s move to the things we already know about Magento 2.
That’s it for today.
Share your opinion and feel free to pose questions in the comments below at any time convenient.
Stay tuned for the latest news from the world of Magento!