Support

Why do older versions report there's an update available even if it's not supported? This has to do with the Live Update system in use by our software. Older versions of Live Update were not aware of Joomla! version compatibility of available versions of our components, therefore they would report any available newer version as an update you have to install. Changing that required a major change in Live Update and our update server. The change made it in Akeeba Backup 3.5.0 and our other components released after that date. Unfortunately older versions' Live Update code cannot be updated for obvious objective reasons. Releasing updates for older Joomla! versions is also not an option, as it would cause several issues on Joomla! 2.5 sites. Therefore you just have to make sure that you have the latest available release designed for your Joomla! version, as per our Version Compatibility page at https://www.akeebabackup.com/compatibility.html and ignore Live Update's prompts for updating Akeeba Backup.

Or you can simply fetch the liveupdate folder from Akeeba Backup 3.5.1 and put it in 3.4.3, except for the config.php file. But my point –if you read very carefully what I wrote– is not that I don't consider the change per se worth it. I consider the fact that it will BREAK ALL JOOMLA! 2.5 SITES USING AKEEBA BACKUP not worth it. I have to choose between two scenarios:

1. Sites with Joomla! 1.5, a version of Joomla! which will die in less than two months, will stop seeing the updates. Sites with Joomla! 2.5, the vast majority of my paying customers, will break because of this update.

2. Sites with Joomla! 1.5 will continue seeing an update. If they try to upgrade, it simply tells them that this is not possible (it doesn't kill the site). In two months this won't even be an issue. Sites with Joomla! 2.5, the vast majority of my paying customers, will continue enjoying updates which don't break their sites.

So, let's say you were me. Would you choose #1 which could very well be the end of your business, or #2?

Besides, I have been telling you guys –through my no-nonsense release announcements– that I would be ending Joomla! 1.5 support in April 2012. I decided to extend the support for two months and now I see that this was a mistake. I should have stuck to my original plan of discontinuing Joomla! 1.5 support in April.

I've thought about the patch idea and I almost implemented it. But, then, the majority of people using Akeeba Backup are non technical and hearing the term "patch" will make them pick up their pitchforks and torches ;) Really, there is a solution and is quite simple:

• Download Akeeba Backup 3.5.1
• Extract it locally
• Copy all the files from backend/liveupdate into your site's administrator/components/com_akeeba/liveupdate except the config.php file
• Go to Administrator, Akeeba Backup
• Click on the "Update Found" button
• Click the "Refresh update information". It will now say that you have the latest version.

The problem is, how many of my users feel adequately self-confident to carry out this trivial procedure? Last week I had to exchange 12 emails to explain someone how to delete a directory via FTP before trying to reinstall Akeeba Backup, despite the step by step instructions I had already given. I had to actually document every click and drag & drop operation. Sometimes it's not very fun being a developer :D