Released on: Thursday, 15 November 2018 07:41
WordPress data replacement is now faster and more reliable. We have rewritten the WordPress data replacement engine from scratch. It is now more than 10x faster and works far more reliably. This is a massive, under the hood change; you won't see any visible interface changes but you'll notice how transferring large, complex WordPress sites is now faster and more reliable.
Support for Application Keys in BackBlaze B2. You now have finer-grained control over your B2 integration, giving access only to specific buckets on each of your sites.
Always enable multipart uploads in Google Drive. Google Drive requires that uploading files over 5MB takes place using chunked uploads. Therefore we had to remove the option to disable chunked uploads. Chunked uploads also reduce the likelihood of the backup failing due to a timeout error so it's a win-win choice.
OneDrive, Google Storage (JSON API) and Dropbox: do not disable multipart uploads when the option to upload part files immediately after their creation is enabled. Previous versions would override your choice of chunked uploads when you had enabled the option to upload part files immediately after their creation. We discovered in our code review that this is no longer necessary. We now respect chunked uploads even in this case, allowing for larger part sizes (up to 2GB, depending on the service) with these remote storage engines.
Bug fixes. We have addressed several issues. Please consult the CHANGELOG.
Added new filter to exclude User Action Logs from the backup (Joomla 3.9+ only). Joomla 3.9 introduced the User Action Logs feature which is enabled by default. This feature generates a large volume of information which does not really belong to a backup. We create a filter, enabled by default, which excludes these records from the backup to prevent backup bloating and improve the time required to take a backup.
Removed platforms with minimal to no use: Drupal 7, Drupal 8, Grav, Magento 1.x, Magento 2.x, Moodle, OctoberCMS, PageKit, phpBB . These platforms are used by too few of our clients to justify our spending time to maintain an integration with them. You can still back up these sites using the generic / bespoke site type.
Providing the URL to Akeeba Solo during setup is now optional (Akeeba Solo will work on most servers without it). The past four years we were asking you to provide the URL where Akeeba Solo is installed. This is not required on most servers; they provide this information in the environment variables passed to PHP by the web server. We are now using this information instead of having you enter the URL manually. This makes transferring Akeeba Solo to a new server much easier, without the need to reconfigure it or set it up from scratch.
Support for PHP 5.3 has been discontinued. PHP 5.3 has been end of life since August 2014 and widely considered a security risk, unfit for production sites. Our software requires PHP 5.4 or later and is compatible with PHP 5.4, 5.5, 5.6, 7.0, 7.1 and 7.2. We currently offer preliminary support for PHP 7.3 which at the time of this writing is still in Release Candidate (testing) phase. We strongly recommend using PHP 5.6 or 7.2.
We'd like to remind you that the PHP version compatibility refers to our software. It is possible that the software you are using for your site does not support all of these PHP versions. You are responsible for ensuring compatibility of the server you are restoring to with the software of your site, including lower and upper limits of PHP and MySQL versions.
HEADS UP! We will be dropping support for PHP 5.4, 5.5 and 7.0 starting January 2019.