Major new feature: Akeeba Backup for WordPress now integrates with WP-CLI. We have added support for the standard WordPress CLI management tool WP-CLI in this version of Akeeba Backup for WordPress. Akeeba Backup Core for WordPress users can use WP-CLI to manage and configure their backup profiles, including exclusion filters, as well as manage their backups. Akeeba Backup Professional for WordPress users can do all of that plus take backups through WP-CLI and manage the inclusion filters (include off-site directories and include additional databases). Moreover, our Proessional subscribers can use this in conjunction with Akeeba UNiTE to fully automate backing up and transferring sites between servers.
Alphabetic sorting of archives in the Discover page. When you are importing backup archive using the Discover page they will now be sorted alphabetically. If you are using a backup naming template similar to the one we ship by default this means that your backups will appear, more or less, organized by the time they were taken therefore making it easier for you to locate the correct file to import.
Site Transfer Wizard wouldn't work on Firefox. We have only been able to reproduce this issue on Firefox Quantum (version 57 and later). A side-effect of how Firefox handles button with an onClick handler which does not return false or cancel the click event would result in the cmponent's main page being shown after clicking the button to check the validity of the target site's URL. This feature works without a problem on other browsers, such as Chrome and Opera.
Bug fixes. We have addressed a few other low priority issues. Please consult the CHANGELOG.
A bug in the updater in version 2.1.0.b1 through 2.1.2 and version 2.4.0 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:
You will only need to do this once, upgrading to version 2.2.0 or later for the first time.
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), versions 2.1.0.b1 through 2.1.2 and version 2.4.0. 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:
akeebabackupwp.
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.
You will only need to do this once, upgrading to version 2.2.0 or later for the first time.
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, 7.1 and 7.2.
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.
HEADS UP! The next version family, Akeeba Solo and Akeeba Backup for WordPress 3.1, will no longer support PHP 5.3, 5.4 and 5.5.