Support

I'm getting the white screen on the backend that others have described.

All was working just fine.

I deleted a profile that I was using for a temp backup. That temp backup was giving me an error because of too large of files. So, I was going to just figure out a different way to back up those files.

I have just started using Akeeba Pro, so I installed Pro version over the previous version. Again, it was working fine.

I didn't care about losing my profiles, so I uninstalled via the Joomla extension manager and reinstalled. I've done this a number of times. Same results of a white screen in the admin side.

I went in and manually deleted the akeeba references in Administrator/components/, media/, plugins/. I also deleted the four reference tables in the database. Then I reinistalled the pro version. I still get the white screen.

Early on I did get this error: [24-Aug-2016 17:27:41 UTC] PHP Fatal error: Maximum execution time of 60 seconds exceeded in /home/kxnpocse/public_html/administrator/components/com_akeeba/BackupEngine/Configuration.php on line 486

But that error has not popped up again.

I removed .htaccess to see if there was a php issue.

I've run out of options, except for a system restore, but I don't want to do that because it will be complex, since I'm not doing a full file system restoration.

Thank you.

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.

Still no solution--white page is still blank. It spins and spins--timing out, I suppose. I'm using Rochen and I think you are as well. When I turn error reporting on. I get some non-fatal errors on other pages, so I am able to get errors.

Any thoughts?

Please clear your browser cache, that should have been the first thing I told you. Also, the Joomla! cache, PHP cache, host cache, etc.

There is an error on that page somewhere. Did you view that page with error reporting on? Is there anything in the server's error log?

Let's see if there is a Javascript problem:

It looks like you are experiencing a Javascript issue. Most likely this is due to malformed or badly written Javascript code added to the pages of your site by a third party plugin.

In order to provide support for your problem we need to know the exact Javascript error that is thrown. For this reason we would like to ask your to please attach a screenshot of the Javascript console of your browser, taken immediately after triggering the issue you want us to help you with.

Here you can find a friendly reminder on how to open the Javascript console:

• Chrome Press either CTRL + SHIFT + J (ALT + CMD + J under Mac) to open the "Console" tab of the Developer Tools.
• Safari Press CTRL + ALT + I (ALT + CMD + C under Mac) to open the Web Inspector. Note: This works only if the "Show Develop menu in menu bar" check box in the Advanced tab of the Preferences menu is checked!
• Firefox Press CTRL + SHIFT + K (ALT + CMD + K under Mac) then click on the "Console" tab

Please note that we need a screenshot, not a paste of the log text. We have determined that, in most cases, pasting the log text alters the sequence of the function calls, becoming useless for debugging purposes.

Thank you in advance for helping us help you!

Yikes. That was it. I should have tried that.

Thank you.

You're welcome!

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.