What's new in Magento 2.2?
•0 likes•1,426 views
Report
Share
15 months after 2.1.0, Magento has released version 2.2.0 with hundreds of bugfixes and some new features for merchants and developers. That's new: - 428 bug fixes - Magento Social - Magento Business Intelligence (BI / Advanced Reports) - Magento Shipping - Magento B2B - Improved Security - Signifyd fraud protection - Performance Improvements - Updated technology stack - Pipeline deployment - Functional Testing with Codeception More information on Magento 2 (in German): http://www.matthias-zeis.com/magento-2
Recommended
More Related Content
Similar to What's new in Magento 2.2?
Similar to What's new in Magento 2.2?(20)
Recently uploaded
Recently uploaded(20)
What's new in Magento 2.2?
- 1. What‘s new in Magento 2.2? Matthias Zeis 04.10.2017
- 5. End of Life 26.09.2019
- 6. What‘s new in 2.2?
- 7. Bugfixes & Improvements Features for merchants Features for developers
- 10. Magento Social
- 13. Magento B2B
- 23. Varnish Saint & grace mode Higher hit ratio
- 24. Bigger Carts > 300 cart items
- 26. PHP 7.1 PHP 5.6 Varnish 5 Varnish 3 MySQL 5.7 Redis 3.2 Solr
- 30. Matthias Zeis mzeis mzeis mzeis matthias-zeis.com Thank you! Questions? Slides will be online: http://www.slideshare.net/mzeis/ LimeSoda is hiring! https://www.limesoda.com/jobs/
Editor's Notes
- 15 Monate nach Magento 2.1.0 (23.06.2017)
- Disclaimer: einzelne Teile upgedatet, keinen bestehenden Shop aktualisiert!
- Open Source Verbindung Webshop und Facebook-Firmen-Account => Shop als Blätterkatalog auf Facebook bereitstellen, Weiterleitung in Webshop. Auch Facebook-Ads. Im Hintergrund Anbindung an „Shopial“. Basis-Paket 35 Dollar / Monat
- Advanced reporting Gekauftes Unternehmen RJMetrics Verfügbar für Open Source und Commerce Essentials- und Pro-Variante Essentials: 100 Dollar / Monat, bis 3 Mio Dollar Umsatz pro Jahr, 75 Reports
- Open Source Wird mit 2.2.2 verfügbar(?) „Intelligent multi-carrier shipping solution“ Anbindung an Shipping-Carrier (UPS, FedEx, …) Abwicklung des Fulfillments Versandkosten-Optimierung Inventory-Routing Erstellung der Etiketten https://magento.com/products/shipping Im Hintergrund: Kooperation mit „temando“
- Commerce Keine Zusatzkosten
- ^^
- Removal of unserialize calls Schutz gegen Cross-Site Scripting (XSS) Attacken
- Betrugserkennung Externes Service, aber direkt im Magento Backend nutzbar (für USA, Kanada, Europa) Commerce Only http://devdocs.magento.com/guides/v2.2/payments-integrations/signifyd/signifyd.html
- Indexing: besseres Memory-Management Verbesserte Laufzeit
- Saint & grace mode: Varnish kann weiterhin gecachte alte Seiten ausliefern, auch wenn das Backend nicht reagiert bzw. nicht schnell genug die neue Seite zurück liefert Weniger Cache-Invalidierungen, dynamische Inhalte (Edge Side Includes) für sich häufig ändernde Daten sind optimiert worden
- Redis nur für Commerce Solr: noch in der Code-Base von „Commerce“, aber nicht mehr supportet (ElasticSearch stattdessen) Composer (1.4.1), ZF2 (2.5), ZF1 (1.12.20) updated ZF1 less usage
- - Weniger Downtime: nur um statische Files und komplierten Code zu transferieren
- https://github.com/magento/magento2/tree/develop/dev/tests/acceptance Noch keine Details, wird man noch mehr hören, wurde erst kurz vor Releaser in Github aufgenommen Codeception, Robo, Allure
- Topics I didn‘t mention at all or not in detail: Theme migration Build & Deployment process
- it's not a simple update You don‘t get Magento 2 with the click of a button or a few commands It‘s a process which involves a lot of manual work. Use it as a chance for a make-over [Next]
- * Custom = your extensions, 3rd party extensions Tables * copy * ignore * rename Columns * copy * ignore * rename * transform value => handlers can be defined (null handler, custom handler, …)
- but it has issues – reserve time! As with every integration project: get real data as soon as possible
- Ubertheme Pro: easy to use, little configuration, does the job for standard data, supports delta Con: slow, hard to rewrite, not secured
- Go through the list of extensions and make basic decisions for every module
- if you do the extension yourself: do you want to migrate the extension or rewrite it from scratch?
- If you rewrite the extension from scratch: Try to use automated testing – base is better Follow official coding standards Document behaviour as it was in M1 so you know what should work how afterwards Maybe write platform independent code
- It has a good documentation!
- A few things that I learned here: [next]
- Installation: you could also do composer require, but there are no official versions yet (current: "0.0.1-alpha") Symfony Console Monolog No Magento 1 or Magento 2 installation needed
- <src>: Good for you if you extracted your code into Composer modules or the like Bring your code in order before doing the migration! See Sergii Shymkos presentation: remove unused modules, revert core modifications. Also interesting: remove core bugfixes irrelevant to M2