Support for dumping MySQL EVENTs. You can now dump MySQL EVENTs on top of the existing support for TABLEs, VIEWs, PROCEDUREs, FUNCTIONs, and TRIGGERs. The database backup engine is also smarter, allowing you to dump TABLE/VIEWs, PROCEDUREs, FUNCTIONs, TRIGGERs, and EVENTs with identical names.
Improved database dump engine. The database engine got revamped. You can now back up MySQL Events. It is now possible to back up procedures, views, and triggers which have the same name as a table or view. Foreign keys constraints, as well as table references in views are now resolved more precisely using the database's INFORMATION_SCHEMA, and a dependency graph resolver. The result is a more accurate backup of large, complex databases with lots of interlinked tables and views at the expense of a slight overall speed decrease of the database backup.
More accurate information about PHP CLI in the Schedule Automatic Backups page. We are now automatically detecting the best path to the PHP CLI executable instead of using the generic /path/to/php placeholder. On most local and live servers this will now return a completely accurate command line you can copy and paste directly to your host's CRON management tool, or your SSH session, without having to ask your host what the path to the PHP CLI executable is. Yay, simplicity!
Multi-row select and row show/hide in the Manage Backups and Profiles pages. We have fixed an integration issue with Joomla which prevented this feature from working. You will now be able to select multiple rows at once by clicking on the first row and then SHIFT-clicking on the last row. For discontinuous selection you can use CTRL-click (Windows, Linux) or CMD-click (macOS).
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Critical bugs and important changes
- Could not work with MySQL 5.x and MariaDB 10.x
Akeeba Backup for Joomla! 9.9.7
Released on: 2024-10-22 06:40 CDT
- Improved database dump engine
- More accurate information about PHP CLI in the Schedule Automatic Backups page
- Multi-row select and row show/hide in the Manage Backups and Profiles pages
- Support for dumping MySQL EVENTs
- [LOW] Cannot transfer files to DreamObjects and Google Storage using the S3 API
- Edit and reset the cache directory (Joomla! 5.1+) on restoration
- Remove MariaDB MyISAM option PAGE_CHECKSUM from the database dump
- [LOW] Backup on Update showed in more Joomla! Update pages than intended
- [LOW] The [PROFILENAME] tag in backup completion emails returns no or wrong labels
- [MEDIUM] Some akeeba😛rofile CLI commands had non-functional options
- [MEDIUM] Tables or databases named `0` can cause the database dump to stop prematurely, or not execute at all
- Change the wording of the message when navigating to an off-site directory in the directory browser
- Disable migration from Akeeba Backup 8 on Joomla! 5.0 and later
- Improve database dump with table names similar to default values
- PHP 8.4 compatibility: MD5 and SHA-1 functions are deprecated
- Workaround for Joomla! 5.1 CSS in alert DIVs
- Workaround for PRE element styling in Joomla! 5.1
Akeeba Backup for Joomla! 9.9.4Stable
Released on: 2024-06-10 01:07 CDT
Option to avoid using `flush()` on broken servers. When sending raw data, such as file downloads, we use PHP's flush() function to indicate to the web server to start pushing the data to the user. We have found a stark minority of servers which are misconfigured, causing the web server software to crash when it receives data before PHP has done executing. If you are that single person we saw once in the past seventeen and a half years on that broken server, now there's a setting in the component's Options to disable this behaviour.
!-
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
-->
- Option to avoid using `flush()` on broken servers
- Alternate Configuration page saving method which doesn't hit maximum POST parameter count limits
- Improved support for Joomla! 5.1's backend colour schemes
- New style for the Backup-on-Update information
- Remove the deprecated, ineffective CURLOPT_BINARYTRANSFER flag
- [HIGH] Custom OAuth2 helpers: cannot use refresh tokens with non-alphanumeric characters (e.g. slashes, plus sign, etc)