30 December 2010 Last updated on 16 January 2012

Akeeba Backup 3.2.b4 (beta) just released

We are pleased to announce the immediate availability of Akeeba Backup 3.2.b4 (Beta) bugfix release.

Beta software is considered stable enough to use on live sites. However, always test your backups after updating Akeeba Backup. If you find a bug, please report it in the forum. Please remember that a bug not rerported during the beta won't be fixed in the stable release.

This version mainly fixes bugs in JSON API used by Akeeba Remote Control 4 to remotely backup and download your backup archives. It also fixes low to medium priority stability bugs affecting setting up Akeeba Backup and restoring backups on Joomla! 1.6.0, the long-awaited Joomla! version which was released yesterday.

If you are a Joomla! 1.6 user, you can upgrade Akeeba Backup Core using Joomla!'s Extensions Updates page. If you are using Akeeba Backup Professional or Joomla! 1.5 you can always update using the integrated update feature inside Akeeba Backup's Control Panel. If all else fails, you can simply install the new version on top of the old one, without uninstalling it.

As always, Akeeba Backup Core is available free of charge from our downloads section. You can find its documentation in PDF format for off-line reading in the downloads section, or you can view it on-line. All users are strongly advised to read our Quick Start Guide, available as a PDF file from our downloads section.

Attention subscribers to the Professional release. There is a change in the live update system included in Akeeba Backup after version 3.2.b1. You will need to visit your My Subscriptions page, copy the "Download ID" found towards the bottom and paste it in the Component Parameters page of Akeeba Backup. Failure to do so will mean that you will be unable to upgrade to later versions in the future.

If you want the most powerful features, such as storing your backup archives on the cloud (Amazon S3, DropBox, CloudFiles, Microsoft Windows Azure), transfer them to a different server by FTP/FTPS, exclude extensions with a single click, apply powerful filters and have an integrated restoration feature, it's time to Go Professional. Subscriptions start at 40€ and give you access to free upgrades for a whole year, while allowing you to install and use the software on an unlimited number of domains and continue to do so even after the expiration of your subscription. What are you waiting for?

go_pro_sidebar

Changelog

This is a brief list of changes between Akeeba Backup 3.2.b4 and the previous 3.2.b3 release:

Changes

+ Greater verbosity level on the post-processign steps
~ ABI: The default database type is now MySQLi if your PHP installation supports it
~ Changed the Component Parameters icon in the Control Panel to load reliably across different templates

Bug fixes

# Professional version could no longer detect its encrypted settings
# JSON API would crash on invalid JSON data instead of reporting an error
# Command-line CRON mode would fail if the "Email on backup completion" option was enabled
# Some versions of PHP have a broken JSON implementation, causing communication with Akeeba Remote to be reported as "JSON Decoding Error". Worked around by using PEAR's Services_JSON instead.
# ABI: Restoration of Joomla! 1.6 sites would fail due to inability to load Super Administrator settings
# ABI: Blocked (disabled) Super Administrator accounts would still show up
# JSON API: Invalid segment numbers were never marked as such, causing the remote download to crash
# The Component Parameters button in the component's Control Panel didn't work on Joomla! 1.6
# The FTP browser wouldn't load on Joomla! 1.6 RC1 thanks to the ever-changing API...
# The FTP browser didn't list all directories under the selected FTP root due to a buggy regex. Changed to use a more naïve and reliable parsing method.
# Using the JPS archiver could trigger a PHP Fatal Error and cause the backup to crash under certain circumstances
# Profile number not remembered during remote (JSON API) backup, causing strange double backup and other artifacts when not using the default backup profile
# Backup would consistently fail when the engine wasn't given a profile ID, i.e. in JSON API backups
# Missing Javascript function trim() would cause the RegEx filters Save button not to work in Joomla! 1.6.0