Support

Hi Robert,

1. There is a reason why I'm not going to do that. Joomla! 1.5 is going to be end of life in less than three months. After the end of August, the Joomla! project will ditch Joomla! 1.5. If you're still using it, you'll be open to security vulnerabilities. It's a good idea upgrading to Joomla! 2.5. If I start spending time on supporting a Joomla! release which is living on leased time (its end of life was initially scheduled for April 2012, one month ago) I will give you the false impression that Joomla! 1.5 is a platform suitable for live sites. It's not. It's a slowly dying dinosaur, much like Windows XP. Do yourself a favour, migrate your sites to Joomla! 2.5 before a security vulnerability after August 31st gets you scrambling to fix your sites. It wasn't an easy decision. It's one I had taken in January, after thinking about it for 6 months, and published it in my release announcements since. Initially the end of Joomla! 1.5 support was placed in April, in line with the original Joomla! project's announcement. When they moved the date to August, so did I.

2. The missing language string is because the old versions had the plugin name hard-coded in the XML, the new versions are using a translation string. This is not a bug, it's a missing language string from the language you're using. Regarding the issues in the plugin, please note that I haven't touched the code since 3.4.0 and that I do not support the plugin as I've written in capital letters in the component description :) What you described is one of the known issues of the plugin, one of those which can't be fixed. Uninstalling and reinstalling the plugin does reset the "aklazy" backup origin, eliminating the continuous backup. So does disabling the plugin, waiting for 10 minutes and visiting Akeeba Backup's control panel page. Is this a sensible way to deal with it? No. That's one of the reasons I stopped supporting this plugin.

If you want to schedule your site's backups, use CRON or if your server doesn't support CRON use webcron.org. Yet another reason I stopped supporting the lazy scheduling plugin: webcron.org is infinitely more stable than plg_aklazy could ever be. And it costs about 2$ per year per site in order to have daily backups. 2 bucks per year? That's dirt cheap! The coffee I drink every day costs at least twice as that. I'd say that Akeeba Backup support in webcron.org was the final nail to plg_aklazy's coffin.