Download Our Latest Software

Akeeba Backup for Joomla! 7.3.2 Stable

Released on: 2020-09-18 06:10 CDT

What's new

Removed update notifications inside the component. This feature has been removed as an anachronism. Starting with Joomla 3.2 all extension updates are handled by Joomla itself, using core Joomla code we have no input on. This applies to both update detection and installation. Joomla also provides extension update notifications inside its control panel. Our software was simply relaying the same information back to you which was potentially confusing and misleading. There is no point maintaining a feature that confuses our users and isn't even necessary anymore. As a result we decided to remove it altogether. This also removes the similarly confusing "Reload update information" button from the component's Control Panel page which was simply asking Joomla to reload its update information. The Joomla way to do this is going to Extensions, Manage, Update and clicking the "Purge Cache" and "Find Updates" buttons, in this order.

Normalized the default backup description under all backup methods (backend, frontend, CLI, JSON API). We realised that each backup origin had a different default description, implemented with a different code path. This was both unreliable and confusing for the user. Now all default backup descriptions are set to "Backup taken on DATE-AND-TIME (METHOD)" which is far more reasonable. The date and time is expressed in the explicitly defined backup time zone if one has been selected. If you have not selected a backup time zone it will be expressed in the user's time zone specified in the currently logged in user's profile (backend backups only) or the site's server time zone specified in Joomla's Global Configuration. In the unlikely event that you have not selected either time zone it will be expressed in UTC. The abbreviated time zone name is printed next to the date and time for clarity.

Bug fixes and minor improvements. Please take a look at the CHANGELOG below.

Joomla! versions supported

We only officially support using our software with the latest Joomla! release branch, 3.9. We strongly advise you to run the latest available version of Joomla! for security reasons. Older versions of Joomla! have known major security issues which are being actively exploited to hack sites.

We offer limited support for Joomla 4.0 which is currently in Beta. Akeeba Backup will run on it, back it up and restore it just fine as of Joomla 4 Beta 3. Please note that since Joomla 4.0 is still in beta it may undergo potentially breaking changes between now and its final release. Joomla 4 specific issues are addressed when we are notified about them or observe them ourselves but they will not be treated as urgent until at least Joomla 4 Release Candidate 1 is released by the Joomla! project.

PHP versions supported

We only officially support using our software with PHP 7.1, 7.2, 7.3 or 7.4. We strongly advise you to run the latest available version of PHP on a branch currently maintained by the PHP project for security 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.

At the time of this writing we have only done some preliminary PHP 8 compatibility testing for the backup engine, PHP 8 being in alpha. We expect to be able to fully support PHP 8 around 2-4 weeks after Joomla implements full PHP 8 compatibility. PHP 8 itself is scheduled for release on November 26th. Our prediction for full PHP 8 support is before the end of January 2021, as long as Joomla adds support for it by end December 2020.

Please note that earlier PHP versions including but not limited to PHP 5.3, 5.4, 5.5, 5.6 and 7.0 are no longer supported and our software no longer works on them.

Changelog

Bug fixes

  • [HIGH] WebDAV fails to upload because of the wrong absolute URL being calculated
  • [LOW] pCloud was erroneously listed in the free of charge Core version (it requires a paid subscription and was thus unusable)
  • [MEDIUM] Restoring a JPS backup archive through the integrated restoration was broken if it contained charactes other than a-z, A-Z, 0-9, dash, dot or underscore.
  • [MEDIUM] The Resume and Cancel buttons in the backend backup didn't work due to a typo in the JavaScript

Miscellaneous changes

  • Normalized the default backup description under all backup methods (backend, frontend, CLI, JSON API)

Removed features

  • Removed update notifications inside the component