Released on: Monday, 21 October 2019 08:23
Database dump produces multiline queries, supports PROCEDUREs, FUNCTIONs and TRIGGERs even better. In the past, Akeeba Backup's database dumps generated single line queries for all data definition language and insert queries. While this works great for all tables and views and most procedures, functions and triggers there were some cases where the latter three entities were corrupt or impossible to restore e.g. when their definition included comments or required preservation of whitespace. The backup and restoration engines have now been updated to create and restore multiline queries, much like you'd get with mysqldump/mysql or phpMyAdmin. As a result the more complicated procedures, functions and triggers are now supported. IMPORTANT! Your database user must still be able to retrieve the definition of these databases entities to run a backup and define or overwrite them to restore the backup. These are limitations imposed by MySQL and controlled exclusively by MySQL privileges. Akeeba Backup CAN NOT magically override your database access control features – such a thing is impossible.
Preliminary work for PHP future 7.4 compatibility. This work is experimental since PHP 7.4 is still in alpha.
Akeeba Backup for WordPress: Prevent site display and show link to the restoration script when the installation folder is present and contains ANGIE. In the past we had a few users who were confused as to how the restoration of their database content is supposed to work because, apparently, they didn't read the text on their screen when extracting the backup archive. Moreover, we had users who left the installation folder on their site after restoration, despite a clear warning about the security implications of that on their screen. We can't force people to read their screens unless we also prevent them from doing anything else. This is exactly our solution now! The Akeeba Backup for WordPress plugin will disable access to the site if the restoration script is present, telling people to either run the restoration script to finalize their site's restoration or, if they already did that, to delete the installation folder.
Bug fixes. We regularly fix smaller and bigger issues. Please consult the CHANGELOG below and the full change history available from the software's main page by clicking the CHANGELOG button.
We only officially support using our software with PHP 5.6, 7.1, 7.2 or 7.3. We strongly advise you to run the latest available version 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.
We officially support only the latest WordPress 4.9 and 5.x release.
We have received reports that Akeeba Backup for WordPress has been installed on WordPress sites as old as 3.8. Backing up and restoring sites that old should be possible but it's not tested and not officially supported. It is a bad idea running an unsupported version of WordPress due to security and performance concerns.