Support

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?)?
https://www.akeebabackup.com/home/news/56-releases/1461-admin-tools-2-2-2.html
Joomla! version: 2.5.4
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Admin Tools version: (unknown)

Description of my issue:

Following update to latest version of AdminTools Pro locked out of my site both Front End and Back End. Tried to follow instructions in ticket #11832 (manually removed files and renamed .htaccess with cPanel) but still locked out of site.

Please advise best course of action to recover site.

Thank you.

Looking through the site cPanel File Manager records, a number of .html and .php files are showing 0 bytes and have their 'last modified' date/time as of the update/time the site went down corresponding to the time the AdminTools update occurred. Is this significant?

Ideas/Questions: Would an overlay install of Joomla recover the problem or is it necessary to do a full backup recovery?

Ok, but I was well under 50% (only about 35%) of my Server Quota of 1000MB. Are you saying that you need more than '2x' disk quota size before you can successfully complete an update of AdminTools Pro? If so, then we need to find some other way of keeping these tools updated. The update process seems very fragile? Is this just me because I'm doing something wrong? I'd welcome any 'best practice' guidance you have to avoid this problem in the future. I'll be very reluctant to apply any further updates of AdminTools Pro until we better understand the nature of this problem/limitation and can avoid it happening in the future.

Nicolas - thanks for your prompt and helpful response. All is now working - I managed to recover all files/folders from a backup.

re. your questions/suggestions ...

yes, you're correct; I did choose the update option from 'Updates are Available'. I hadn't seen/noticed this option before. It so happened that the first update option listed was 'admintoolspro' and it was choosing this that prompted the website failure. I hadn't appreciated [read your release notes!] that this option shouldn't be used for updating Akeeba AdminToolsPro. I will remember in future!

as for ideas about what causes the problem the only relevant error log entries recorded at the time of failure were ..

[04-Apr-2012 13:50:38] PHP Fatal error: Call to a member function load() on a non-object in ../public_html/libraries/joomla/installer/adapters/file.php on line 220

in the administrator error.log and ..

[04-Apr-2012 13:44:41] PHP Fatal error: Call to a member function getValue() on a non-object in ../public_html/plugins/system/admintools/admintools/core.php on line 78

[04-Apr-2012 13:49:09] PHP Fatal error: Call to a member function mark() on a non-object in ../public_html/index.php on line 24

[04-Apr-2012 13:49:29] PHP Fatal error: Call to a member function mark() on a non-object in ../public_html/index.php on line 24

in the root error.log

I hope these entries might be of use in your investigations.

It seems unfortunate that such a simple user 'error' should give rise to such a dramatic failure in deleting files. Following the 'First do no harm' principle it would seem the update process should fail more gracefully.

I've given myself a bit of a fright. I will be more careful in future!:)

Thanks for your update and efforts in trying to reproduce this problem. I'll update the 'correct' way and open a separate ticket if I experience something similar in the future.