TESTING (BETA) VERSION

This is a TESTING (BETA) version. We recommend that you only use it on non-production sites.

What's new

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.

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.

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.

Changelog

Bug fixes

• [LOW] Add-on ANGIE language files would not be included in the backup archive
• [LOW] Leftover empty file after the end of the Configuration Wizard run
• [LOW] Restored WordPress sites would not work in wp-config.php erroneously contained a trailing closing PHP tag
• [LOW] The Transfer Wizard may select a chunk size which is too big for the target server
• [LOW] The kicktemp folder and the kickstart.transfer.php file were not removed after Site Transfer Wizard had finished
• [LOW] Using the Site Transfer Wizard may result in a "wordpress" folder being left behind on some servers with a broken FTP server (technically a bug with your FTP server; we had to remove a minor feature to work around it)

New features

• Rewritten user interface