New major version 7. Please consult our announcement for an overview of the new features and changes. It's just too much to include in these release notes!
ANGIE: Options to remove AddHandler lines on restoration. Have you ever restored a site on a different server only to find that it either not loads or downloads the .php file as text? That's because your site was using an AddHandler line to tell your old server which PHP version to use. These are server-specific and the new server did not understand it. Now you can remove these lines on restoration to prevent this kind of issue. You may still have to go to your hosting control panel and select the PHP version depending on your host and whether its default PHP version is simply too old to be usable.
Removed: pCloud support. Unfortunately there is a bug in their OAuth2 server which prevents users other than us from successfully authorizing our software. This means that there is no way to connect to pCloud and it has to be removed. To be clear: this is a bug in pCloud itself, not Akeeba Backup.
Bugfixes and improvements. We identified and resolved some high priority issues affecting beta 1. See the CHANGELOG below.
We only officially support using our software with PHP 5.6, 7.0, 7.1, 7.2 or 7.3.
We offer experimental support for PHP 7.4. That is to say, we have verified our software to run mostly correctly on the pre-release versions of PHP 7.4. We have not yet had the chance to do full verification against the stable version of PHP 7.4 which was released just a few days before our software.
We strongly advise you to run either of the two latest available version branches of PHP on a branch currently maintained by the PHP project for security and performance reasons. Older versions of PHP have known major security issues which are being actively exploited to hack sites and they have stopped receiving security updates, leaving you exposed to these issues. Moreover, they are slower, therefore consuming more server resources to perform the same tasks.
Kindly note that our policy is to officially support only the PHP versions which are not yet End Of Life per the official PHP project with a voluntarily extension of support for 6 to 9 months after they become End of Life. After that time we stop providing any support for these obsolete versions of PHP without any further notice. New version branches of PHP will be supported experimentally starting sometime during their Release Candidate phase and fully about 4 to 8 weeks after the first stable version of that branch is released.
We officially only support the latest WordPress 5.x release.
Our software should also work on WordPress 4.9 and ClassicPress 1.x since we do not rely on any features added in later WordPress versions.
We fully support single site and multi-site installations of WordPress. Multi-site installations can be converted on restoration from directory-based to subdomain-based or vice versa. You cannot restore a single site backup into a multi-site installation. You cannot restore / convert a blog of a multi-site network installation into a single site WordPress installation (in fact, there is no official WordPress method to do that safely).
We do not recommend using our software with WordPress versions earlier than 4.6 as some WordPress features we rely on for our software to function properly did not exist in these vintage versions. We generally strongly advise against running old, no longer maintained versions of WordPress for security and performance reasons.