Support

Admin Tools

#12746 No more access to backend

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Friday, 22 June 2012 12:51 CDT

cornelius
Mandatory information about my setup:joomla 2.5.4

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Admin Tools version: (unknown)

Description of my issue: When updating from joomla 2.5.4 to 2.5.6 via Admintools an error occurred. Could not find a file in the Hathor template. Trying again another error occurred. I think I have to update manually?
Then the system found some other updates (akeeba backup). After hitting the update button a white screen appeared. Now its no longer possible to access the backend.
What to do?

nicholas
Akeeba Staff
Manager
Do not use the Joomla! update page to update the Professional versions of our components. It will not work and cause white pages.

Regarding the Joomla! update issue, there is no possible error message which tells you that a file can't be found when updating Joomla!. Maybe it said it can't write to the file? If this happens, you have a problem with the permissions on your site. Most likely you can use the FTP options when updating your site through Admin Tools to overcome those issues. If, however, you have mixed ownership of your files this won't be possible.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

cornelius
Hi Nicholas,
But i Did use the Joomla update page and now there is this problem of white pages. Is there a way to fix this?

nicholas
Akeeba Staff
Manager
You can try a few things.

First download the Joomla! 2.5.6 installation ZIP file and extract it locally. Upload everything except the installation directory to your site and retry logging in.

If that fails, you can manually uninstall Admin Tools and Akeeba Backup. For Akeeba Backup please remove the following folders and files:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction

For Admin Tools, please remove the following files and directories:
- plugins/system/admintools
- plugins/system/atoolsjupdatecheck
- plugins/system/atoolsupdatecheck (Joomla! 1.7 only)
- administrator/modules/mod_atjupgrade
- components/com_admintools
- administrator/components/com_admintools

Now you should be able to log back in to your site. If you are still receiving a blank page we'll have to do some more debugging.

A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):
ini_set( 'display_errors', true );
error_reporting( E_ALL ); 
Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:
php_flag display_errors On
php_value error_reporting 32767
and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

If you still get a white page, delete the php.ini files your created and choose a different host. If your host doesn't allow you to debug any PHP-related issues there is no point paying them.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

cornelius
Great response Nicholas.

nicholas
Akeeba Staff
Manager
No problem! Please let me know if following this advice doesn't work.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

cornelius
Updating Joomla manualy worked. I am now able to login again in the backend. Inside there were some white screens (module management). After hitting F5 button they dissapeared.
Thanks again.
Now there are some updates like JCE editor and Akeeba backup. What is the right way to proceed updating these components?
I have noticed that there were indeed some problems with file ownership. I have resetted the ownership. I wonder how they occur. The FTP-layer is on so that can't be the problem?
I have tried to update Akeeba backup. Getting a message that the zip-file can't be opend. Due to wrong file ownership. (apache) What to do to prevent this from happening. With other sites on the same server I am not having these problems.

nicholas
Akeeba Staff
Manager
You seem to have mixed ownership of your site's files. The easiest way to work around that is as follows:
- Take a full site backup and keep it somewhere safe
- Remove all files and folders from your site
- Extract the backup archive using Kickstart's FTP Mode. This is important. Do not use the "Write directly to files" method!
- During the restoration remember to enable the FTP options; this will turn on Joomla!'s FTP layer.
- After the restoration is over, give the tmp, logs, cache and administrator/cache directories 0777 permissions.
- Inside each of these four directories put a .htaccess file with the following contents:
order deny, allow
deny from all
allow from none

This disables web access to those directories. You may have to remove this .htaccess files from the cache directory if you have an extension which is badly written and expects this directory to be web accessible (e.g. WidgetKit).

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

cornelius
Hi Nicholas, You are such a great help.
Did it all. Except for the reinstall via kickstart. Backend all right. Installed Akeeba Backup again. Got a message that there was something wrong. But backup works anyway.
Installing admintools again there was this "Something went wrong Go back to te controlpanel" page. The zipfile now has got the right ownwer and still its not possible to install Admintools. What else can I do to get it to work?

nicholas
Akeeba Staff
Manager
Can you post a screenshot of the error message?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

cornelius
attached

nicholas
Akeeba Staff
Manager
That's a permissions issue. You can follow our installation troubleshooting instructions.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!