Not a beta. This is the same thing as the 3.0.0.b1 version but it's no longer called a beta. We realize that when y'all see a "beta" label you expect a half-baked, bug-ridden, hot mess of a release. Over here we call that a "work in progress branch" and we do not publish it, ever. Not even as a dev release. At the bare minimum we do an internal testing of 4 weeks before release, including running the new version of our software on our live sites for two weeks. That's what we call a “beta”. A stable includes another two weeks of public testing or, in case we're fixing a specific bug, two successful tests by two unrelated people on two different hosts. In the light of your expectations we are republishing our beta, plus a couple of minor bug fixes, as a stable to better reflect the published code quality.
New interface. We have rewritten the interface to our software using our brand new Akeeba Front-End Framework, a CSS framework specially designed for our software. Please report any issues you find on supported browsers (IE11+, latest versions of Google Chrome, Mozilla Firefox, Opera, Microsoft Edge, Safari).
PHP 7.2 support. Our software is tested on PHP 7.2 and marked as compatible with it.
Bug fixes. We have addressed known issues, mostly low priority ones. 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.