Support

Akeeba Backup for Joomla!

#10867 – White screen after installing 3.3.13 on J1.5.25

Posted in ‘Akeeba Backup for Joomla!’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Sunday, 29 January 2012 03:19 CST
DavidBoggitt
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 1.5.25
PHP version: 5.3.9
MySQL version: 5.1.56
Host: Rochen
Akeeba Backup version: 3.3.13

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
Hi,

I noticed the recent hotfix on the JED, so I downloaded 3.3.13 and installed it (rather than upgrading) on several 1.7.4 site. This worked perfectly.

However, when I installed on a J1.5.25 site, it appeared to install perfectly (the usual notices came up), but when I then clicked again on Akeeba Backup, I got a white screen. Turning Error Reporting up to maximum simply gave:

Notice: Trying to get property of non-object in ../plugins/system/nnframework/helpers/parameters.php on line 106

This I guess is from the NoNumber! extensions and I'm not sure would cause Akeeba not to load.

Not quite sure where to go from here. I have tried uninstalling (which seemed to go fine) and then reinstalling but the same issue persists.

Many thanks,

Dave.
 
Sunday, 29 January 2012 03:22 CST
DavidBoggitt
Extra Note:
Reinstalling 3.3.12 worked fine, if this helps.
 
Sunday, 29 January 2012 03:23 CST
nicholas
Please try re-downloading and re-installing the package. The first 13 people to download the package got a broken version which doesn't work on Joomla! 1.5. The one which is on-line right now works fine.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Sunday, 29 January 2012 03:23 CST
nicholas
Hm, I just realised, 3.3.13, 13 people downloading it... Talking about unlucky 13!


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Sunday, 29 January 2012 03:24 CST
DavidBoggitt
:-)

Will the version I installed be ok on the 1.7.4 sites?
 
Sunday, 29 January 2012 03:34 CST
nicholas
Yes, of course. The problem was caused due to a missing bail-out if-block. In order to support Joomla! 1.7/2.5 extensions updater code, the Professional release has to go on and modify the update site record directly in the database. However, this is not possible on Joomla! 1.5 (which doesn't use this feature) and causes the error. The if-block which was missing detects the Joomla! version and doesn't run this code on Joomla! 1.5 sites.

Which brings me to my next point. Right now I'm trying to test all of my software on Joomla! 1.5.25, 1.7.4, 2.5.0, on PHP 5.2 and 5.3, on Windows, Mac OS X and Linux hosts. If you're counting this is 3*2*3 = 18 configurations. This has led to never doing full testing on all platforms, as it would take forever. The longer I test, the more support requests I receive, so the less time I have to test and even more support requests I receive, accentuating the problem to unfathomable proportions. So, starting with the next version of my software, I'm dropping support for anything except Joomla! 2.5. It's either that, or stop developing all of my software except Akeeba Backup and Kickstart.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Sunday, 29 January 2012 03:40 CST
DavidBoggitt
Nicholas,

I completely understand your point of view!

I do wonder though whether it might be possible to keep support going for 1.7.4 for a while? The reason is, is that I (like many other users I suspect) am keen to upgrade my 1.7.4 sites to 2.5.0 but I can't until the site extensions are upgraded too. All the problem forum posts I've read about upgrading point to this (unsurprisingly) as the main cause of failure.

There is bound to be some (but not much, hopefully..) delay with developers updating their extensions and then at some point in time when many users will (or can) upgrade then you can drop support for 1.7.4.

You are the boss though, of course :)

Best wishes,

Dave.

 
Sunday, 29 January 2012 03:46 CST
nicholas
Hi Dave,

Joomla! 1.7.4 and 2.5.0/2.5.1 do not have many differences from an API point of view. The only backwards incompatible change was a change in the Javascript which prompted the release of the (broken) Akeeba Backup 3.3.12, but has now been accepted as a bug and a fixed Joomla! 2.5.1 is scheduled for Tuesday. Oh, the joys!

So, even though I will be only officially supporting Joomla! 2.5, I don't expect anything to break in 1.7. I can't vouch for Joomla! 1.5 support though. I'm eager to drop it, as it's becoming a huge bottleneck in implementing new features in my software. 1.5 and 2.5 are a universe apart.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Sunday, 29 January 2012 04:10 CST
DavidBoggitt
That's interesting to know, thanks! I don't think anyone would blame you for dropping 1.5, especially as long as there's a version working for 1.5 so people can backup/restore their sites!

Best wishes,

Dave.
 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!