Released on: Thursday, 26 March 2020 05:24
Possible exception when the user has erroneously put their backup output directory to the site's root with open_basedir restrictions restricting access to its parent folder.. This mostly affects old backup profiles, created before Akeeba Backup 5. If the output directory is on your site's root, the automatic security upgrade of your log files could cause a fatal error (unhandled exception). We've only seen one case but the conditions for triggering this issue are not implausible therefore we had to address it.
Impossible to use OneDrive for Business. The post-installation script was accidentally removing some of the files used by the Upload to OneDrive and OneDrive for Business post-processing engine. Even though you could see that option in the post-processing drop-down you could not connect your site to OneDrive. Even if you manually copied the tokens (e.g. by using Akeeba Backup for Joomla to retrieve them) the upload would still fail because of the removed files. This version addresses this issue.
We only officially support using our software with PHP 5.6, 7.1, 7.2, 7.3 or 7.4.
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.