12 September 2011 Last updated on 16 January 2012

Akeeba Backup 3.3.9 just released

We are pleased to announce the immediate availability of Akeeba Backup 3.3.9, a bugfix release. This release addresses two bugs inadvertently introduced with Akeeba Backup 3.3.8, released yesterday.

An issue existed in Akeeba Backup 3.3.8 with the System Restore Points quota feature which caused all system restore points to be deleted immediately upon creation, rendering them useless. This release fixes this erratic behaviour and the System Restore Points feature is now back to operational status. It really is! We apologise about the problem introduced in yesterday's release.

Moreover, the last version, Akeeba Backup 3.3.8, had accidentally left the debug-level error logging turned on. As a result, even PHP Warnings and Notices which are normally suppressed would be logged, falsely alarming users that something could be wrong with their backups. These warnings and notices are expected and suppressed, i.e. they never make it to the browser or your server's error log. They are generated when Akeeba Backup tests for the existence or readable/writeable status of a file. The debug-level logging which was turned on would add them to Akeeba Backup's log file, misleading users that there was a backup problem. This release addresses this issue by disabling the logging of suppressed PHP warnings.

As always, you can download the free version, Akeeba Backup Core, from our Downloads page without any charge. If you are a Professional subscriber you can download the Akeeba Backup Professional release from the same page; just make sure you are logged in before visiting the download page. Alternatively, you can use the integrated Live Update feature of our software to update it automatically on supported server environments.

We no longer support Joomla! 1.6.x. Akeeba Backup 3.3.9 will only run on Joomla! 1.5.15 (or later) and Joomla! 1.7.0 (or later). If you try to use it with Joomla! 1.6 you might crash your site. If that happens, we will decline to help you as we officially do not support Joomla! 1.6. Joomla! 1.6 is an end-of-life product since August 2011. It contains known vulneraibilities. If you are still using Joomla! 1.6, first upgrade to Joomla! 1.7, then update Akeeba Backup. If you want to backup your Joomla! 1.6 site you can always use the (unsupported) Akeeba Backup 3.2.7 release.

Please note that Akeeba Backup 3.3.x requires PHP 5.2.7 or later to work. If you have an earlier version of PHP, please ask your host to upgrade it immediately. PHP 4, 5.0, 5.1 and 5.2 are end-of-life products, abandoned over a year ago by their developers, containing known security vulnerabilities. If you are stuck on a host using PHP 5.1.6 up to and including PHP 5.2.6, you can use the (unsupported) Akeeba Backup 3.2.7 release to back your site up in order to move it to a host with up-to-date software.

Since July 7th, 2011, support is provided only to subscribers. We have created a cheap (7.79€) subscription, FORUMACCESS, which gives you access to our Support Forum for eight days, with the same priority as all subscribers to any subscription level. If you are an AKEEBADELUXE or SUPPORT subscriber, you can get top priority, confidential support through our Private Ticket support system.

Do you want the best backup solution for Joomla! without spending a fortune? Akeeba Backup Professional can do that, with a flat cost of 40 Euros – or just 30, if you bought an ATPRO subscription the last three moths. An AKEEBAPRO subscription allows you to use the component on as many sites as you want, for as long as you want (even after your subscription expires) and receive updates and support for a whole year. For the price of a dinner for two you can get the best backup solution all your Joomla! 1.5 and 1.7 sites. Go Professional today!

Changelog

Miscellaneous changes

  • Improved readability of update notification email (thank you Brian Teeman!)

Bug fixes

  • The SRP quotas would remove the latest system restore point, rendering the feature useless
  • Suppressed warnings and notices would be reported in the log file, but they are expected to happen (they are file existence/read tests)