New major version. Please consult the News section on our site for important information about
Akeeba Backup 7. It's simply too much to include in the release notes.
New version numbering. All of our backup software follows a common version numbering. Therefore
this new version if 7, not 4.
PHP versions supported
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
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.
WordPress versions supported (only applies to Akeeba Backup for WordPress)
We officially support only 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 running our software on 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.
- [HIGH] Backing up PROCEDUREs, FUNCTIONs and TRIGGERs was broken
- [HIGH] Changing the database prefix would not change it in the referenced tables inside PROCEDUREs, FUNCTIONs and TRIGGERs
- [HIGH] Manage Backups: would not show Transfer Archive for qualifying backups not fully uploaded to remote storage.
- [LOW] Disabled menu items (e.g. Backup Now) page confused people; removed them to prevent confusion
- [LOW] Manage Backups: downloading a part file from S3 beginning with text data would result in inline display of the file instead of download.
- [LOW] Manage Backups: the Remote Files Management dialog's size was off by several pixels
- [MEDIUM] BackBlaze B2: upload error when chunk size is higher than the backup archive's file size
- [MEDIUM] Database only backup of PROCEDUREs, FUNCTIONs and TRIGGERs does not output the necessary DELIMITER commands to allow direct import
- Amazon S3 now supports Bahrain and Stockholm regions
- Amazon S3 now supports Intelligent Tiering, Glacier and Deep Archive storage classes
- Google Storage now supports the nearline and coldline storage classes
- Manage Backups: Improved performance of the Transfer (re-upload to remote storage) feature.
- Minimum required PHP version is now 5.6.0
- New OneDrive integration supports both regular OneDrive and OneDrive for Business
- Support for Dropbox for Business
- Windows Azure BLOB Storage: download back to server and download to browser are now supported
- pCloud support
- All views have been converted to Blade for easier development and better future-proofing
- Backup error handling and reporting (to the log and to the interface) during backup has been improved.
- Common version numbering among all of our backup products means this version is 7, not 4
- Manage Backups: Fetch Back To Server was rewritten to gracefully deal with more problematic cases.
- Manage Backups: The Remote File Management page is now giving better, more accurate information.
- Manage Backups: much more informative error messages if the Transfer to remote storage process fails.
- Removed AES encapsulations from the JSON API for security reasons. We recommend you always use HTTPS with the JSON API.
- SugarSync integration: you now need to provide your own access keys following the documentation instructions
- The Site Transfer Wizard is now only available in the Professional version
- The Test FTP/SFTP Connection buttons now return much more informative error messages.
- The backup and log IDs will follow the numbering you see in the left hand column of the Manage Backups page.
- The front-end legacy backup API and the Remote JSON API are now available only in the Professional version
- The integrated restoration feature is now only available in the Professional version