Replies: 3 comments 2 replies
-
Today I upgraded one of my customers' store to v21-beta1 (on a staging environment obviously) and, from first tests, works great!! The upgrade was truly effortless, just ran shell/rename-mysql4-class-to-resource.php and removed all the decorate* functions from all the custom phtml files and it was done. This projects uses algolia, a one page checkout and many modules from amasty, aheadworks and many other vendors, not the easiest and simplest setup. wow |
Beta Was this translation helpful? Give feedback.
-
A new age is coming! |
Beta Was this translation helpful? Give feedback.
-
Does it include rwd2? Something fballian talked about in "openmage future" post? |
Beta Was this translation helpful? Give feedback.
-
🚀 OpenMage 21 is the next step in the evolution of our beloved M1 platform. 🚀
📢🔔 While V21 introduces breaking changes that require careful consideration during the upgrade process, these long-overdue modifications will ultimately bring significant benefits to your stores. In the long run, you can expect enhancements in performance, security, SEO scores, and more, making the transition worthwhile. 📢🔔
Changes you must know and that you have to check one by one
Check
app/design/frontend/base/default/template/contacts/form.phtml
in your theme and be sure that you've<?php echo $this->getBlockHtml('formkey') ?>
under the<form
opening tag, as shown hereIf you enabled CSRF in
System -> Configuration -> System
(which you should!) then it will be enabled for all your forms and the checkoutBe sure to check your CSS styles for the buttons in your frontend theme, you may need to adjust them slightly
_Mysql4_
classesThis will break many extremely old modules but it was long overdue and allowed us to remove 500+ obsolete files from the core. We provide the
shell/rename-mysql4-class-to-resource.php
migration script to fix the old modules, you will have to run it but make sure you'll do it in a test environment and thoroughly test everything before publishing to productiondecorate*()
js functionsCheck the phtml files of your custom themes for javascript code calling
decorate*()
(decorateList, decorateTable, decorateGeneric etc) and remove those calls since they will generate javascript errors on your browser's consoleThe new admin routing mode was implemented in Magento 1.4 for security reasons, together with "compatibility mode" (in order to allow some time to developers to update their modules). After these many years we are removing the compatibility mode and all extensions will have to follow the new admin routing mode or they will not appear in the backend.
scriptaculous/dragdrop.js
from frontendChanges you want to know about
Changes that probably won't affect you
enquire.js
and converted to window.matchMedia by @fballiano in RWD: removed enquire.js and converted to window.matchMedia #3208js/varien/weee.js
without prototypejs by @fballiano in Rewrotejs/varien/weee.js
without prototypejs #3670js/varien/accordion.js
without prototypejs by @fballiano in Rewrotejs/varien/accordion.js
without prototypejs #3669js/mage/adminhtml/scrollbar.js
by @fballiano in Removed unused file js/mage/adminhtml/scrollbar.js #3765js/mage/adminhtml/magento-all.js
by @fballiano in Removed unused file js/mage/adminhtml/magento-all.js #3764js/mage/adminhtml/image.js
by @fballiano in Removed unused file js/mage/adminhtml/image.js #3758js/mage/adminhtml/hash.js
using native javascript by @fballiano in Rewrote js/mage/adminhtml/hash.js using native javascript #3763js/mage/adminhtml/variables.js
without prototypejs by @fballiano in Rewrote js/mage/adminhtml/variables.js without prototypejs #3762js/mage/translate.js
without prototypejs by @fballiano in Rewrotejs/mage/translate.js
without prototypejs #3662This discussion was created from the release v21.0.0-beta1.
Beta Was this translation helpful? Give feedback.
All reactions