Support

 Installed Admin tools update 2.6.1 and when attempting to run PHP file scanner get a System Error 500 and obviously the scan does not complete.

Note that I had previously upgraded Backup to 3.10.2 and ran PHP scanner in version 2.6.0 without any problems. Then upgarded DocImport and ran scanner OK. The Admin Tools was the last I updated so suspect it may NOT be FOF update related. If that helps.

Other thing of note is that when installing these updates the Restore Point completes but then a blank page is presented (after all 3 updates) instead of going to the component page. Refreshing the blank page gives one the option of going to the Joomla Control Panel. Then one can get to the updated component page. The components do appear to have been successfully installed as far as I can tell (currently).

Just seen this is a duplicate of 19450. And there is a ticket for the white pages as well. So much for my searching!

I can confirm that the 2.6.12 update does indeed resolve the problem. Thank you.

I must say that I personally consider the removal of the Live Update feature a retrograde step. I know that you released the 2.6.2 update yesterday morning, yet waited deliberately until today to see when the Joomla update would tell me it was available. Despite purging the update cache and rechecking it still didn't tell me nearly 24 hours after the release. At least with the Live Update I knew reasonably quickly. I ended up downloading the update and manually applying it. [I did check and the update site details are in the DB.]

That said the question that needs to be asked now is 'what is the future for the live update feature generally?' Will it continue to be supported/developed? I personally use it for my developed extensions and I know I am not alone.

Thank you for the clarification. One of the good things about your software that I appreciate but which is probably not mentioned very often by many, is not that it just works, but that it works very well. Hence what I regard as a backward step removing it (Live Update) from your own software.

I can however understand the reasoning and wish you well trying to get Joomla itself to move forward on the 'problem'. [Possibly J3.5 perhaps.] If an update is only 'trivial' then it really doesn't matter how long it takes to be notified about it. If the update could be classed as 'critical', then in my book, speed is of the essence. Hackers and other undesirables are not usually known for their understanding in waiting before trying to exploit known weaknesses in software.

I am content that you can now close this ticket. I would do it myself but wish to ensure that you see this message first, and I'm not sure whether you monitor issues when they are closed by the raiser.