What's new

Introduction of remote.php alternative endpoint. We observed that some hosts would not allow Akeeba Remote CLI and other JSON API consumers from using index.php as the remote API endpoint. We addressed this issue by creating a new endpoint called remote.php. Both endpoints can and will be able to be used with the JSON API. If one doesn't work for you, try the other.

BackBlaze support. On popular demand we added support for the low-cost and high reliability storage provider BackBlaze.

PHP 7.2 support. Our software now runs on PHP 7.2.

We updated the Dropbox API with the new "_v2" endpoints where applicable. Dropbox has been rolling out updated endpoints for several features. Our software is now using the new endpoints where available, ensuring forward compatibility.

Bug fixes. We have addressed known issues, mostly low priority ones. Please consult the CHANGELOG.

Updating Akeeba Solo

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:

• 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), 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:

• 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, 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.

Changelog

Bug fixes

• [LOW] Core version: CLI scripts were included
• [LOW] Core version: some post-processing options were displayed even though the code to make them work was not present.
• [LOW] Core version: too many backup type options being shown
• [LOW] Exclude Files and Directories page cannot display errors when AJAX fails
• [LOW] Fixed Javascript warnings in Transfer Site Wizard
• [LOW] Misleading message about PHP version when the update server could not be reached
• [LOW] PHP notice if the HTTP User Agent is not sent by the remote client
• [LOW] Programmatically triggering mouse events could fail in some browsers, e.g. newer versions of Firefox
• [LOW] WebDav post-processing: Fixed issue with hosts without a valid certificate file and SSL connections
• [LOW] You would see a confusing "None" database driver option during installation
• [MEDIUM] "Apply to all" filter button does not work due to a Javascript issue
• [MEDIUM] Autoupdate feature was not working
• [MEDIUM] Backing up to JPS with a static salt using the JSON API would always fail

New features

• BackBlaze B2 integration (Pro only)
• Introduction of remote.php alternative endpoint

Miscellaneous changes

• JSON API stepBackup: now enforcing the check for the MANDATORY parameter "backupid"
• PHP 7.2 compatibility: renaming Object class to BaseObject
• Update Dropbox API with the new "_v2" endpoints where applicable

Critical bugs and important changes

• Missing language strings (fixed in 2.4.2)