Skip to content

Releases: OpenMage/magento-lts

v19.5.0-rc4

15 May 17:59
Compare
Choose a tag to compare
v19.5.0-rc4 Pre-release
Pre-release

You should absolutely know

Since the approval of our second RFC - release schedule OpenMage 19.x enters and "patch only" state, it will be maintained for two more years as promised but only significant security patches or regression fixes will be ported to v19, every other development (and we have many) will be focused on v20+.

We encourage everybody to upgrade to v20, it is our latest and greatest and deserves the bit of work necessary for the upgrade (ask your developer/agency, don't do it yourself).

Highlights

This is a big release, that's why we decided to move away from the 19.4.x versioning and go to 19.5.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 19.5.0. Tests are more than welcome now but be extra careful with production environment.

  • What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.
  • PHP 7.4 is now the minimum required version and 8.2 is now supported
  • M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • Support for Google Analytics 4 was added

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

  • Fixed session renew timestamp should be updated when customer changes password #2916
  • Fixed price filter when search by non-numeric value #3136
  • Added patch for Zend_Mail and "emails are displayed incorrectly" problem #3202

Full Changelog: v19.5.0-rc3...v19.5.0-rc4

v20.1.0-rc3

13 Apr 13:45
81702bc
Compare
Choose a tag to compare
v20.1.0-rc3 Pre-release
Pre-release

You should absolutely know

Since the approval of our second RFC - release schedule OpenMage 19.x enters and "patch only" state, it will be maintained for two more years as promised but only significant security patches or regression fixes will be ported to v19, every other development (and we have many) will be focused on v20+.

We encourage everybody to upgrade to v20, it is our latest and greatest and deserves the bit of work necessary for the upgrade (ask your developer/agency, don't do it yourself).

Release highlights

This is a big release, that's why we decided to move away from the 20.0.x versioning and go to 20.1.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 20.1.0. Tests are more than welcome now but be extra careful with production environment.

What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Also:

  • PHP 7.4 is now the minimum required version and 8.2 is now supported.
  • the M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • a great improvement to EAV config cache has been added to v20.
  • support for Google Analytics 4 was added.
  • possibility to set backend locale per every admin user was added.

Changelog

Full Changelog: v20.1.0-rc2...v20.1.0-rc3

v19.5.0-rc3

13 Apr 13:26
Compare
Choose a tag to compare
v19.5.0-rc3 Pre-release
Pre-release

You should absolutely know

Since the approval of our second RFC - release schedule OpenMage 19.x enters and "patch only" state, it will be maintained for two more years as promised but only significant security patches or regression fixes will be ported to v19, every other development (and we have many) will be focused on v20+.

We encourage everybody to upgrade to v20, it is our latest and greatest and deserves the bit of work necessary for the upgrade (ask your developer/agency, don't do it yourself).

Highlights

This is a big release, that's why we decided to move away from the 19.4.x versioning and go to 19.5.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 19.5.0. Tests are more than welcome now but be extra careful with production environment.

  • What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.
  • PHP 7.4 is now the minimum required version and 8.2 is now supported
  • M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • Support for Google Analytics 4 was added

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

Full Changelog: v19.5.0-rc2...v19.5.0-rc3

v20.1.0-rc2

14 Mar 13:05
Compare
Choose a tag to compare
v20.1.0-rc2 Pre-release
Pre-release

Highlights

This is a big release, that's why we decided to move away from the 20.0.x versioning and go to 20.1.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 20.1.0. Tests are more than welcome now but be extra careful with production environment.

What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.

Also:

  • the M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • a great improvement to EAV config cache has been added to v20.
  • support for Google Analytics 4 was added.

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

New Contributors

Full Changelog: v20.1.0-rc1...v20.1.0-rc2

v19.5.0-rc2

14 Mar 13:04
1e8fcd0
Compare
Choose a tag to compare
v19.5.0-rc2 Pre-release
Pre-release

Highlights

This is a big release, that's why we decided to move away from the 19.4.x versioning and go to 19.5.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 19.5.0. Tests are more than welcome now but be extra careful with production environment.

  • What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.
  • M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • Support for Google Analytics 4 was added

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

New Contributors

Full Changelog: v19.5.0-rc1...v19.5.0-rc2

v20.1.0-rc1

17 Feb 15:25
Compare
Choose a tag to compare
v20.1.0-rc1 Pre-release
Pre-release

Highlights

This is a big release, that's why we decided to move away from the 20.0.x versioning and go to 20.1.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 20.1.0. Tests are more than welcome now but be extra careful with production environment.

What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.

Also:

  • the M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.
  • a great improvement to EAV config cache has been added to v20.

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

New Contributors

Full Changelog: v20.0.18...v20.1.0-rc1

v19.5.0-rc1

17 Feb 15:18
Compare
Choose a tag to compare
v19.5.0-rc1 Pre-release
Pre-release

Highlights

This is a big release, that's why we decided to move away from the 19.4.x versioning and go to 19.5.x. Since a lot of changes could have some impact on current installations we decided to release some "rc" versions before the official 19.5.0. Tests are more than welcome now but be extra careful with production environment.

What's most important is the removal of all the 3rd party libraries (phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier and Zend Framework) form our repository, they are now imported via composer. This was an important step to clean up and modernise our code.

Also the M1 legacy themes have been moved to an external repository since it's old (and mostly unused) code.

Don't worry though, if you've always installed OpenMage extracting the zip file, starting from this release you'll find a new zip file attached to the release itself, we build this zip adding all of the old 3rd party libraries so that you will not have to migrate to composer or use composer at all.

Changelog

Read more

v20.0.20

02 Feb 15:02
Compare
Choose a tag to compare

This is a security update with a single fix regarding CVE-2020-27511, ReDos (Regular Expression Denial of Service) vulnerability in prototypejs (#3003).

v19.4.23

02 Feb 15:01
Compare
Choose a tag to compare

This is a security update with a single fix regarding CVE-2020-27511, ReDos (Regular Expression Denial of Service) vulnerability in prototypejs (#3003).

v20.0.19

26 Jan 13:58
Compare
Choose a tag to compare

This is an important security update release, it includes six security patches:

All of these updates should be totally backward compatible, except one, CVE-2021-21395 - GHSA-r3c9-9j5q-pwv4 - Reset Password not protected against well-timed CSRF in fact is a breaking change and you will need to take action after upgrading to this version of OpenMage.

Specifically, you will have to modify the customer/form/resetforgottenpassword.phtml file of your custom theme (in case you have customized it) and add this code <input name="form_key" type="hidden" value="<?php echo $this->getFormKey(); ?>" /> after the <form open tag. Please refer to this link in case you want to see how the patch works and copy/paste the simple solution.

In case your custom theme does not have the customer/form/resetforgottenpassword.phtml or in case you are not using a custom theme then you will not have to do the aforementioned procedure.