What's new
Improved WordPress restoration. More restoration cases for multisite installations are now
supported, including moving a directory-based multisite installation to a different folder.
More stable.
Bug fixes. We fixed several issues affecting backups under rather uncommon conditions.
Updating Akeeba Solo to version 2.2.0 or later
A bug in the updater in version 2.1.0.b1 through 2.1.2 makes it impossible to update to the new version using the
built-in updater. You will have to do that manually.
Heads up! You must NOT uninstall Akeeba Solo before the update. Doing so may result in loss of your
backup settings and / or your backup archives. Instead, here's what to do:
-
Download the ZIP file for Akeeba Solo and extract it locally.
-
Upload all the files from the extracted archive into the folder on your site where Akeeba Solo is installed, using FTP or SFTP, overwriting your existing files.
-
Log in to Akeeba Solo to automatically complete the update process. There is no message when the process completes. You just see the main page of Akeeba Solo (this means the update succeeded).
You will only need to do this once, upgrading to version 2.2.0 or later for the first time.
Updating Akeeba Backup for WordPress to version 2.2.0 or later
Due to changes in the packaging format and / or issues in the updater, you cannot update automatically from Akeeba
Backup for WordPress versions 1.0 through 1.8.2 (inclusive) and versions 2.1.0.b1 through 2.1.2. You will have to do
that manually.
Heads up! You must NOT uninstall or deactivate the plugin before the update. Doing so may result in
loss of your backup settings and / or your backup archives. Instead, here's what to do:
-
Download the ZIP file for Akeeba Backup for WordPress and extract it locally. You will see an extracted
folder named
akeebabackupwp.
-
Upload the files from the extracted
akeebabackupwp folder into your site's
wp-content/plugins/akeebabackupwp
folder, overwriting your existing files, using FTP or SFTP.
Please note that the name of the folder on your site may be different than akeebabackupwp,
e.g. akeebabackupwpcore, akeebabackupwp (1) or something similar. It depends on how
you installed the plugin.
-
Log in to WordPress' wp-admin and access Akeeba Backup for WordPress to automatically complete the update
process. There is no message when the process completes. You just see the main page of Akeeba Backup for
WordPress (this means the update succeeded).
You will only need to do this once, upgrading to version 2.2.0 or later for the first time.
PHP 5.3.4 or later (incl. 5.4, 5.5, 5.6) or PHP 7 is required
Akeeba Solo and Akeeba Backup for WordPress are compatible with PHP 5.3.04 and later versions, including 5.4,
5.5, 5.6 and the newest versions of PHP, 7.0 and 7.1.
We'd like to remind you that this requirement refers only to our software. The sites which can be backed up by our
software may not support all of the aforementioned PHP versions. Please check the requirements of your site's
software before restoring it on a different host / server to avoid issues due to PHP version incompatibilities.
Changelog
Bug fixes
- [HIGH] Disabling decryption can lead to loss of current settings
- [HIGH] Editing two or more Multiple Databases definitions consecutively would overwrite all of them with the settings of the last definition saved
- [LOW] "_QQ_" shown during restoration instead of double quotes
- [LOW] ANGIE: restoring sites served by a server cluster could result in "random" errors due to session handling being tied to the server IP
- [MEDIUM] ANGIE: WordPress Replace Data step may have a To value "null" instead of an empty string
New features
- ANGIE for WordPress: better UI for the data replacement page
Miscellaneous changes
- [SECURITY] altbackup.php: verify SSL certificates by default. Use --no-verify command line option to revert to the old behavior.
Removed features
- [SECURITY ADVICE] ANGIE will no longer lock its session to prevent information leaks. Please always use the ANGIE Password feature.
Critical bugs and important changes
- [SECURITY] Improved internal authentication in restore.php makes brute forcing the restoration takeover a few dozen orders of magnitude harder.
- [SECURITY] Secret Word for front-end and JSON backups is now stored encrypted in the database (as long as settings encryption in the application's Options is NOT disabled and your server supports encryption).