Released on: Tuesday, 27 July 2021 04:34
Exception when you do not have the package extension installed on your site.
This should actually never happen when installing an update. Installing an update manually or automatically actually installs the latest version of the package extension (pkg_akeeba). It appears that for very few sites the package extension disappears after installing an update(!) which triggers an issue in our code which attempts to fix this problem. Again, this is only triggered because either someone messed with the database (namely, the
#__extensions table) or because there's a Joomla bug.
Restoration: information about disabling the password protection. If you inadvertently applied an ANGIE password during backup, e.g. because your browser or password manager automatically filled one for you without you noticing it, you may find yourself in the unfortunate position of looking at a locked restoration script when trying to restore your site. Even though we do document what to do in this case it would appear that almost nobody thinks to read the documentation. So, we added the documentation in ANGIE itself. The lock screen will tell you which file you need to remove by (S)FTP or through your hosting control panel to disable the password protection.
Remove ROW_FORMAT during backup and restoration. InnoDB tables may include a ROW_FORMAT specifier which tells MySQL which internal data format to use for InnoDB table data. The internal row format has repercussions in how big each field in a table can be and how big all fields in a table combined can be. When restoring a site from or to an older MySQL version than the one you backed up from the inclusion of the ROW_FORMAT specifier may make it impossible to restore your site. Akeeba Backup now removes it to let you more easily restore a site using InnoDB tables (Joomla's default data format) across different MySQL server versions.
Joomla 4 changed the location of cacert.pem, breaking backup upload to remote storage. Joomla 4 stopped shipping the cacert.pem file as part of its HTTP package and, very prudently, moved to using Composer to provide the latest version of this file. The cacert.pem file's location was hardcoded in Akeeba Backup since there was no other way to know where it lived. The file is used to validate the TLS certificates of remote storage providers (other than FTP and SFTP). As a result, Joomla 4's recent change inadvertently broke upload to remote storage. We are now detecting if a cacert.pem file is available through Composer and prioritize using it. This makes Akeeba Backup compatible with both Joomla 3 (hardcoded file location) and Joomla 4 (using Composer).
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Please consult our Compatibility page. It explains our version support policy and lists which versions of our software are compatible with which versions of Joomla and PHP.