3

I have a fresh Installation of joomla and civicrm: civiCRM = civicrm-4.6.2-joomla.zip

The Installation went well, however I just receive a white (blank) page calling civicrm from the admin_>Components->CiviCRM

the related link: http://mywebsite.com/administrator/index.php?option=com_civicrm

I have tried already certain suggestions from the old "CiviCRM Community Forums", but could not find a working solution. Database and PHP Version is >5.

May be someone can give me a hint where to start to investigate. Thank you!

B ert

System Information

PHP erstellt für Linux Thot03 2.6.32.12 #5565 Mon May 11 02:12:06 CST 2015 armv5tel Datenbankversion 5.5.42-MariaDB Datenbankzeichensatz utf8_general_ci PHP-Version 5.5.25 Webserver Apache PHP-Interface für den Webserver fpm-fcgi Joomla!-Version Joomla! 3.4.1 Stable [ Ember ] 21-March-2015 20:30 GMT Joomla!-Plattform-Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT Browsererkennung Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0

  • There's not quite enough info here to help. A WSOD could be caused by pretty much anything, and it's important to keep digging until you find some kind of error message. Check your server logs (apache and php) as well as the CiviCRM logs. – Coleman May 28 '15 at 18:05
7

A white screen (WSoD or "white screen of death") indicates that PHP is configured not to display errors, and has hit an error which it can't recover from. The result is an empty page.

Your next step is not to fix the error but to give yourself enough information to identify the source of the error.

Viewing errors in logfiles

The webserver can be configured to display errors to screen, but it also logs errors to files on disk. These files vary depending on your hosting environment, so you might consult your webhost's documentation to locate them. You might look for errors in some of these locations depending on webserver/php config -

/var/log/nginx/*err*log       # NginX webserver error logs
/var/log/apache2/*err*log     # Apache webserver & mod_php error logs
/var/log/*php*log             # PHP-FPM & PHP-CGI error logs
/var/log/php5/*log            # PHP-FPM & PHP-CGI error logs
/path/to/site/err*log         # Some hosting environments

And a CiviCRM specific file - location varies depending on hosting environment AND CMS -

path/to/site/path/to/civicrm/files/ConfigAndLog/CiviCRM*log

(The *s above represent a wildcard, not an actual filename. Eg the last entry might be public_html/error_log on Bluehost.)

Once you've located these files, you can download them to view, or you can use tools like tail or less +F to follow the files. I prefer to follow logfiles because you can watch the error appear each time.

Displaying errors to screen

You may prefer to display errors to screen. This is probably disabled on your site because it's a security risk to some degree - an attacker can see more information when errors are visible, so the default configuration is often to restrict visibility to people with server access (via the logfiles above).

To enable errors, either configure your PHP to display errors for your site via php.ini / .htaccess (see How can I get PHP errors to display OR add this code (you can add it in civicrm.settings.php or the top of the index.php of your host CMS).

<?php
  error_reporting(E_ALL);
  ini_set('display_errors', TRUE);
  ini_set('display_startup_errors', TRUE);

Making sense of what you see

Once you've taken one of the above approaches, try reproducing the actions which lead to a white screen. If all's gone well, you should see an error (on screen or in your terminal / SSH session).

This is where you can start debugging meaningfully. There's a good chance you're exhausting server resources (timeouts, memory exhaustion) or hitting some coding error, but once you have the relevant error message at hand you'll be much better equipped to track down the source of the problem affecting your site.

Further reading

Notes

If this is the first time you've looked, there may be other errors visible which don't relate to the problem at hand. You may need to discern what the actual problem is still.

If you're not familiar with UNIX, this may seem like a lot of effort. It's a lot of effort to guess your way through debugging a problem though!

  • We don't seem to have a WSoD page on SE (or I couldn't find it) so I've taken a stab at writing one. I'm not sure how we turn that into a community wiki page, it may be we should ask a more generic question and move the answer across there? – Chris Burgess May 28 '15 at 19:41
  • I'd vote this up 10 times if I could. I'm going to link to this from the Community Support Documentation: wiki.civicrm.org/confluence/display/CRM/… – Jon G - Megaphone Tech May 29 '15 at 17:53
  • I figured out that beside of a "successful" installation parts of the system where missing e.g. the media folders of civicrm... I had uninstalled the civicrm system with the joomla mechanisms, but so far i was not able to reinstall civicrm becaus now 10.10.10.11/si_backoffice/administrator/… brings up a white page. – B ert Jun 2 '15 at 11:47
  • I've re-posted this against a more generic question @ civicrm.stackexchange.com/questions/6399/… – Chris Burgess Sep 14 '15 at 3:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.