Download Our Latest Software

Akeeba Backup for Joomla! 3.11.0 Stable

Released on: 2014-05-06 03:32 CDT

Release highlights

A better, more stable way to install and update the database tables. Previous versions were using the database installation and update code in Joomla! itself which was notoriously buggy and resulted in erratic behaviour. In this release we use our own database installer / updater for the base tables of our component. Unfortunately, due to the rules in the Joomla! Extensions Directory, we still have to rely on Joomla!'s code for the administrator menu item creation which may cause no menu item appearing under components on very few sites. We are aware of it, we know how to fix it, but we are not allowed to on penalty of being permanently banned from the directory!

Show the update information in the control panel page. In the previous version we introduced the integration with Joomla!'s own extensions updater. Unfortunately you could no longer see the update information in the component's control panel page. This version fixes it and allows you to force-reload the update information if you need to as Joomla! no longer lets you do that in the latest 3.x versions (for no good reason, really).

Better workaround for the misbehaving auto-complete feature of certain browsers (e.g. Safari). Some browsers would auto-complete passwords even when we specifically told them not to, by means of the autocomplete="off" attribute. Regrettably, Safari and some Firefox extensions ignored that with the effect of ending up with an ANGIE password when you didn't expect one to be set. This was frustrating to our users who thought it's a bug with our software. Thankfully, we found a good Javascript-based workaround! Also, whenever you are using an ANGIE password, Akeeba Backup will warn you – just in case your fingers slipped.

CLI script to receive update notification and, optionally, auto-update our software. You can use this script in a CRON job. It will send you update notification emails and, if you enable the option, automatically update our component to the latest version as soon as it's made available.

Backup progress is shown in the browser tab. If your browser supports setting the tab's icon we will show you the backup progress as a tiny pie chart in the browser tab icon. This is useful when you're running backups of several sites in different tabs and you want to see at a glance which ones are already finished.

...and a lot more minor improvements and bug fixes.

Changelog

Bug fixes

  • [HIGH] Accessing the component fails on Joomla! 3.2.x if the core database has not been updated
  • [LOW] A tilde in the PHP version could cause a cosmetic error (a warning printed out) during restoration. Functionality was not affected by this issue.
  • [LOW] Some languages do not include a translation for the new PLG_SYSTEM_AKEEBAUPDATECHECK_MSG string
  • [MEDIUM] ANGIE: Sometimes a fatal error is thrown on redirection
  • [MEDIUM] Blank page or 400 error message after updating from 3.10.1 or lower using Live Update
  • [MEDIUM] The CLI check script was not working under Joomla 2.5
  • [MEDIUM] WebDAV upload fails depending on whether you have a trailing slash in the base URL and a leading slash in the directory name

New features

  • Allow the user to forcibly reload the update information from the component's control panel page
  • Backup progress also shown on the browser tab's icon using Piecon
  • Database table installation, uninstallation and update is now handled by our own code instead of the unreliable JInstaller code
  • Display a warning when you set up an ANGIE password during backup
  • Show update information in the component's control panel page
  • Work around against certain browsers (e.g. Safari) and password managers auto-filling fields marked with autocomplete="off"
  • You can now change the date format of the Start column of the Manage Backups page
  • [PRO] Added CLI script to check for new versions and automatically update Akeeba Backup

Miscellaneous changes

  • Working around Safari browser ignoring web standards: it always auto-completes a password field even when web developers explicitly specify autocomplete="off"