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?)? yes
Joomla! version: (1.5.23)
PHP version: (unknown)
MySQL version: (unknown)
Host: (CentOS, but it helps us help you)
Admin Tools version: (2.2.0 stable)

Description of my issue:
I was using 2.2.a, and trying to upgrade to 2.2.0 stable by using the live update.
I got the following error after the upgrade.
"JFolder::create: Could not create directory". I think this maybe some folder's privilege issue. In the meantime, it also displayed the components installed successfully which is a bit confusing. Then I click "back" button. I realised that I was block-out of my back-end, and also front-end even. Then I did the followings:

1. I followed the troubleshoot instruction by rename main.php to main-disable.php.
Then I can see my front-end page is back. The back-end login page also shows up. But after I input my user name and password of the back-end, I saw 500 internal error.
2. Again, I followed instruction to rename .htaccess and .htaccess.admintools to something else, but the problem remains.

I think this relates to the unsuccessful installation, but no idea how to solve this issue. I also tried to restore the backup from my server back-end, I can see the contents roll back, but admintool seems quite "robust" which doesn't change.

Please help!

Simon

Thank you for your quick reply.

I just realised another problem before I proceed your suggestions. Though the front page loaded, but all the links on that page doesn't work, I guess it's related to .htaccess since I renamed it.

"- Rename plugins/system/akeebaupdatecheck.php to .php-bak"
Doesn't help.
"- Rename plugins/system/akeebajupdatecheck.php to .php-bak"
I don't have this file
"- Rename administrator/modules/mod_atjupgrade (that's a directory) to mod_atjupgrade.bak"
Helps!
I can access to back-end. And tried to reinstall admintools pro. But the same error happens as when I upgrade. I noticed there is one error which I forgot to mention.
"Framework on Framework (FOF) ---- not installed"

After reinstall, all the errors come back. I lost access to front page and back-end.

You're superb! That solved problem.
After I restore .htaccess and .htaccess.admintools, all the dead links on front page also come back.

And I found my libraries directory and all the sub-directories belong to root:root, should I change to apache:apache? or leave it for security purpose?

You're right. That's a dedicated server only for me, even it hosts several sites, but all mine.
Because I need to upgrade admintools on other sites on this server, in order to avoid the same problem. For example, due to privilege issue, fof didn't get installed. Apart from root and apache, which group should I choose for a successful admintools upgrading? And also for avoiding potential errors of other software. Thanks

thanks you very much