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] Large database records can cause an infinitely growing runaway backup or, if you're lucky, a backup crash due to exceeding PHP time limits.
• [HIGH] PHP Fatal Error if the row batch size leads to an amount of data that exceeds free PHP memory
• [HIGH] Resuming after error was broken when using the file storage for temporary files (default)
• [HIGH] WordPress multisite restoration: cannot log in if it's a directory-based multisite and you are restoring to the site's root
• [HIGH] WordPress multisite restoration: the path to the default site is not updated when restoring to a subdirectory making it impossible to access the site
• [HIGH] WordPress restoration: .htaccess RewriteRule has unnecessary path when restoring to a subdirectory, leading to routing issues.
• [LOW] FTP/SFTP over cURL uploads would fail if the remote directory couldn't be created
• [LOW] The Warnings pane was always displayed following resuming from a backup error
• [MEDIUM] Blank page if you delete all backup profiles from the database (a default backup profile could not be created in this case)
• [MEDIUM] Database hostname localhost:3306 leads to connection error under some circumstances. Note that this hostname is wrong: you should use localhost without a port instead!
• [MEDIUM] Database storage wouldn't report the lack of stored engine state, potentially causing forever stuck backups
• [MEDIUM] Errors always result in the resume pane being shown, no matter what your settings are
• [MEDIUM] Errors when reading the backup engine's state were not reported, causing the backup to seem like it runs forever
• [MEDIUM] Logic error leads to leftover temporary database dump files in the backup output directory under some circumstances
• [MEDIUM] WordPress restoration: .htaccess RewriteBase does not contain trailing forward slash when restoring to a subdirectory, may cause routing issues in some cases