Support

Admin Tools

#16336 Blank front and back end

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 Monday, 10 June 2013 06:43 CDT

user76099
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: (Unknown) cannot access the site to check
PHP version: 5.3.2-1ubuntu4.17
MySQL version: 5.1.63-0ubuntu0.10.04.1
Host: www.churchlangley.org
Admin Tools version: Latest

Description of my issue:
After apply a few features of your software the front and back end are blank.

To try and resolve this i have changed all .htaccess files, change the name of all admintool folders and files to "name-disable", i have checked the database and all tables for admintools are blank.

Still the front and back end are blank please help.

nicholas
Akeeba Staff
Manager
Have you tried renaming the plugins/system/admintools directory?

If that doesn't help (which I believe it won't), can you try replacing the .htaccess file's contents with the contents of Joomla!'s htaccess.txt file, as shipped with a new Joomla! installation package.

If I have to take a wild guess, the blank page is likely caused: 90% because of an incompatible .htaccess setting, 9% because of a PHP issue (e.g. the libraries/fof directory becoming corrupt or having been deleted) and 1% due to a different issue that would require further debugging.

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!

user76099
Thank you for your quick reply,

I have renamed the directory and any other directorys i could fin which related to admin tools. still no joy.

I have replaced the contents of the .htaccess file with that of htaccess.txt. still no joy.

What would i be looking to change in the for directory?

Thank you

nicholas
Akeeba Staff
Manager
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.

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.

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!

user76099
[Mon Jun 10 11:39:35 2013] [error] [client 82.27.235.65] PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cgi/conf.d/imap.ini on line 1 in Unknown on line 0
[Mon Jun 10 11:39:35 2013] [error] [client 82.27.235.65] PHP Catchable fatal error: Argument 1 passed to AkeebasubsModelSubscriptions::_buildQueryColumns() must be an instance of FOFQueryAbstract, instance of JDatabaseQueryMySQL given, called in /var/www/vhosts/churchlangley.org/httpdocs/administrator/components/com_akeebasubs/models/subscriptions.php on line 558 and defined in /var/www/vhosts/churchlangley.org/httpdocs/administrator/components/com_akeebasubs/models/subscriptions.php on line 110

nicholas
Akeeba Staff
Manager
Your Akeeba Subscriptions version is way too old and no longer compatible with newer versions of the rest of our software. Please read this: https://www.akeebabackup.com/home/news/55-general/1502-troubleshooting-instructions-for-feb-2013-releases.html

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!

user76099
You are a star that worked a treat.

Im back up and working

nicholas
Akeeba Staff
Manager
Awesome :)

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!