Akeeba Backup 3.0.b1

We are pleased to announce the immediate availability of Akeeba Backup Core 3.0.b1 and Akeeba Backup Professional 3.0.b1, which bring us closer to the release of the first stable version of the 3.x branch of our software. This version addresses operational bugs on both editions and introduces new features, such as Live Help, integrated updates, split SQL database dumps, uploading backup files to remote FTP servers (Professional edition) and an alternative, more compatible, CRON script (Professional edition). You can download Akeeba Backup Core for free in our download section. If you are not an English speaker, you may want to take a look at the translations as well. We just added French and Dutch in this release! If you get stuck, you're welcome to post to our  Free Support Forum (a free user registration is, of course, required to post to the forum).Have you seen our documentation yet? If not, take the time to read it on-line, or download the documentation ZIP archive which contains a high-quality PDF file for off-line viewing or printing. Please, save trees; do not print the User's Guide.If you are a subscriber to the Akeeba Backup Professional edition, you can download the update through the My Downloads section after logging in. If you are not a subscriber yet, you may want to find out more about it and become one. This way you'll also be helping us raise the necessary funds to continue the development of this software.

Changelog

This is the short list of changes since Akeeba Backup 3.0.a5.1:

Bug fixes

• Misdetection of tables as VIEWs when the MySQL engine type was not specified
• Requesting all table rows could lead to MySQL client library memory exhaustion
• SET sql_mode was tried on MySQL 4 databases, causing an error
• MySQLi driver caused corrupt database backups
• ABI: Path to tmp and log folder would include /installation/../ in it.
• Extra databases were being dumped in Main Database Only mode
• The chunk size setting for the archiver engines was not being applied
• The backup type "All databases" wouldn't be recorded in the backup statistics table
• Trying to enforce MySQL 4 compatibility mode on MySQL 4.0 servers would cause backup issues (crashes, skipping database backup, etc)
• Empty prefixes on extra databases would cause all table names to be prefixed with akb_, making proper restoration impossible
• Newlines in the off-line message could cause the database connection information to disappear from configuration.php during restoration
• Backing up Kickstart in site's root will cause restoration problems. It is now automatically filtered out.
• Cosmetic bug: notice thrown when saving settings
• ABI: A failed database restoration would require all databases to be restored from scratch, if multiple databases were defined in the backup
• ABI: Databases not defined error, even though the databases.ini is present and readable
• The number of the step which just finished wasn't written to the log
• Some backup would be marked as "failed" or "pending" even though they ran to their completion
• Unchecking the "Dereference symlinks" options would trigger a warning message which would kill the backup process on many servers.
• Potentially uninitialized objects during backup under certain circumstances
• ABI: Lack of temporary data encoding could cause issues with missing configuration.php data during restoration
• The backup type wasn't being displayed in Administer Backup Files when the backup type was "files only"
• ABI: Database restoration would fail when magic_quotes_runtime was enabled
• Notices thrown in Administer Backup Files for CLI mode backups
• CLI mode backup origin was not written in the backup statistics table
• No description was registered for front-end backups