Support

Hi Luc,

As I've written in other threads, the version of Live Update included in Akeeba Backup 3.4.3 is not aware of Joomla! version compatibility, that's why it's detecting an update. If you want the emails to stop you just have to disable the Akeeba Backup Update Notification plugin. As I have already explained in at least four different threads over the last three days, I can not release a 3.4.4 version to solve that. Doing that would make sites with Akeeba Backup 3.5.0 to detect the update and try to install it, completely killing these Akeeba Backup installations.

Regarding Amazon S3, that's strange because that code has not been touched for five months. In fact, if you take a look at the error message it tells you that you have a problem in the TCP/IP level of the communications with Amazon S3, namely that Amazon S3 forcibly closes the connection during multipart uploads. That's an Amazon issue, not a bug. In fact, it's a well known Amazon issue and I've written a troubleshooting page about ten months ago. Please note that when I wrote those instructions the latest version was Akeeba Backup 3.2.7. It's not like I suddenly cocked up and introduced a bug. You just have to follow these instructions for a very well known problem on Amazon's side. Why did it get triggered now? No idea. On my site multipart uploads would work perfectly for 10 days in a row, then not work for a few days, then work again for a couple of days, then not work for a month, ... You get the picture. Since these results were obtained with the same site and same code, I can only assume that the problem is on Amazon S3's side and all you have to do is disable multipart uploads.

Also note that beta testing is here since four and a half years ago. But here's what happens. When I release an alpha or a beta and tell you that it's not meant for live sites you guys come back to me calling me some interesting things because I "broke your site". When I don't release the alphas through the regular update stream nobody bothers installing them. Even worse, many people see the bugs, uninstall the component, install an older version and do not report the issue. Then the stable comes out and they go "oh, I spotted such and such issue three months ago but I thought you'd have fixed it by now". So there you have it. How am I supposed to fix bugs if they do not get reported during the alpha and beta phases? That's why you usually see .0, .1 and possibly .2 releases in quick succession: because nobody reports bug when they should and I can only test my software on so many configurations :(