Releases: PrestaShop/autoupgrade
v4.1.1
v4.1.0
New minor version following feedback with autoupgrade v4.0 and PrestaShop 1.7.4.2
Improvements
Automatic checks
Other
- #126: Remove a specific file only used for PrestaShop 1.7 upgrades
Bug fixes
- #127: Reset archive name when switching back on channel minor / major
- #136: Set the composer autoloader after the core
- #137: Fix a duplicated string (files to be removed)
- #141: Fix an issue with undefined class
Tools
, reported in #140 - #144: Reverting #136 as it makes the module failing on early versions of PS 1.6
- #145: Check a file
config/boostrap.php
exists before requiring it.
v4.1.0-beta.2
v4.1.0-beta.1
New minor version following feedback with autoupgrade v4.0 and PrestaShop 1.7.4.2
Improvements
Automatic checks
Other
- #126: Remove a specific file only used for PrestaShop 1.7 upgrades
Bug fixes
v4.0.0
v4.0.0-beta.5
Bug fixes
#103: Do not clean empty values in configuration table
#108: Show properly the selected archive for upgrade
Improvements
#105: Remove use of PrestaShop core during restoration
#109: Set NULL in backup when value is NULL in database
#110: Add check of PrestaShop release before starting upgrades
v4.0.0-beta.4
⚠️ Known issues
The 1-click upgrade module has currently issues to run an upgrade from PrestaShop 1.6 to PrestaShop 1.7.4.0 / 1.7.4.1. Others upgrades (1.6 to 1.6, or 1.7 to 1.7) end properly.
Improvements
#99: Syntax change for concatenated string.
#101: Add placeholders in configuration form.
Bug fixes
#96: Handle key generation with OpenSSL (Compat PHP 7.2 with PS 1.6).
#98: Check a prestashop
folder exists in zip before unzipping it.
#103: Fix for localized configuration data being erased.
v4.0.0-beta.3
v1.6.8
v4.0.0-beta.2
Follows feedback from v4.0.0-beta.1.
Includes the following PRs:
- #78: Update of displayed content
- #83:
- Fix in Readme content
- Add EOL in logs
- Make sure content is always generated in the autoupgrade subfolder of your admin context
- #84: Fixes an issue preventing the releases to be downloaded. Configuration data is properly initiated.
- #85: Add a check on backup step, where a full storage space wasn't properly detected.
- #86: Use only 1.6 method to disable non-native module. Using the core require the modules to be loaded, throwing errors when incompatible.