Support

Admin Tools

#15684 admin tools conflict

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 Wednesday, 10 April 2013 02:36 CDT

user972
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: 2.5.9
PHP version: 5.3.23
MySQL version: 5.1.68-cll
Host: Lypha
Admin Tools version: 2.5.3

Description of my issue:
When I installed from Akeeba backups, I got a message that "Koowa plugin rerquires mysqli" etc so I configured mysqli but then the whole front end disappeared, just revealing blank screen. I still had access to administrator back end.
After much trial and error and following your advice in a post, when I disabled system admin tools plugin, the front end reappeared. Then if I enabled again, front end was lost. I repeated the whole process on a second installation with exactly the same behaviours : demanding mysqli, which lost the front end until I disabled Admin Tools.
Much of the sites were working well, except for the same 2 main menu items and their submenus, which still delivered blank pages.
I further followed your advice and purchased and installed ACL manager. On installation it found issues but quickly resolved them all and now reports no problem.
There must be a problem that would cause Admin tools to not function correctly. I love this component and your Akeeba backup and they are important tools.
Could you please help me get it to work properly?
sites affected:
permaculture.com.au/college
permaculture.com.au/web
Thanks in anticipation

nicholas
Akeeba Staff
Manager
Hello Paul,

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. The only way to find out what is going on is doing some debugging on an affected site. Your site is the only one I know of to be affected by this issue. In order to find out what's going on you will have to enable the System - Admin Tools plugin when carrying out the following instructions.

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.

IMPORTANT: Sometimes the error won't show. Edit your configuration.php and find the line starting with public $error_reporting and set it to:
public $error_reporting = 'development';

This instructs Joomla! to enable maximum error, warnings and notices verbosity. In 99.9% of cases it will result in the error messages being shown on the browser.

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!

user972
Thank you Nicholas for your great advice.

Turns out the problems were because of a lack of memory allocation. Once I saw the repeating error messages I shared them with the server and the tech recognised the problem. Increased memory allocation through php.ini and now the site works fine again, with admin tools enabled.

Thanks again, very valuable helpful support.

nicholas
Akeeba Staff
Manager
You are welcome!

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!