Answers.Body: <p>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. </p>
  
  <p>Your next step is not to fix the error but to give yourself enough information to identify the source of the error.</p>
  
  <p><strong>Viewing errors in logfiles</strong></p>
  
  <p>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 -</p>
  
  <pre><code>/var/log/nginx/*err*log       # NginX webserver error logs
  /var/log/apache2/*err*log     # Apache webserver &amp; mod_php error logs
  /var/log/*php*log             # PHP-FPM &amp; PHP-CGI error logs
  /var/log/php5/*log            # PHP-FPM &amp; PHP-CGI error logs
  /path/to/site/err*log         # Some hosting environments
  </code></pre>
  
  <p>And a CiviCRM specific file - location varies depending on hosting environment AND CMS -</p>
  
  <pre><code>path/to/site/path/to/civicrm/files/ConfigAndLog/CiviCRM*log
  </code></pre>
  
  <p><em>(The <code>*</code>s above represent a wildcard, not an actual filename. Eg the last entry might be public_html/error_log on Bluehost.)</em></p>
  
  <p>Once you've located these files, you can download them to view, or you can use tools like <code>tail</code> or <code>less +F</code> to follow the files. I prefer to follow logfiles because you can watch the error appear each time.</p>
  
  <p><strong>Displaying errors to screen</strong></p>
  
  <p>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).</p>
  
  <p>To enable errors, either configure your PHP to display errors for your site via <code>php.ini</code> / <code>.htaccess</code> (see <a href="https://stackoverflow.com/questions/1053424/how-do-i-get-php-errors-to-display">How can I get PHP errors to display</a> OR add this code (you can add it in <code>civicrm.settings.php</code> or the top of the <code>index.php</code> of your host CMS).</p>
  
  <pre><code>&lt;?php
    error_reporting(E_ALL);
    ini_set('display_errors', TRUE);
    ini_set('display_startup_errors', TRUE);
  </code></pre>
  
  <p><strong>Making sense of what you see</strong></p>
  
  <p>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).</p>
  
  <p>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.</p>
  
  <p><strong>Further reading</strong></p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/1053424/how-do-i-get-php-errors-to-display">Stack Overflow: How do I get PHP errors to display?</a></li>
  <li><a href="https://civicrm.stackexchange.com/questions/376/where-should-one-look-for-logs-when-debugging-a-new-problem">Where should one look for logs when debugging a new problem?</a></li>
  <li><a href="https://www.drupal.org/node/158043" rel="nofollow noreferrer">Drupal.org: Blank pages or White Screen of Death</a></li>
  <li><a href="https://joomla.stackexchange.com/questions/299/what-is-an-efficient-way-to-troubleshoot-a-white-screen-of-death">Joomla SE: What is an efficient way to troubleshoot a White Screen of Death</a></li>
  </ul>
  
  <p><strong>Notes</strong></p>
  
  <p>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.</p>
  
  <p>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!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T19:41:17.640Z
Answers.Text: 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?
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-29T17:53:24.103Z
Answers.Text: I'd vote this up 10 times if I could.  I'm going to link to this from the Community Support Documentation: http://wiki.civicrm.org/confluence/display/CRM/Community+Support+Documentation
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T11:47:18.190Z
Answers.Text: 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 http://10.10.10.11/si_backoffice/administrator/index.php?option=com_installer&view=install brings up a white page.
Answers.UserDisplayName: B ert
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-14T03:05:33.797Z
Answers.Text: I've re-posted this against a more generic question @ http://civicrm.stackexchange.com/questions/6399/civicrm-is-showing-a-blank-page-white-screen-how-do-i-debug-this/6400
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T19:40:00.757Z
Answers.LastActivityDate: 2015-05-28T19:40:00.757Z
Answers.LastEditDate: 2017-05-23T12:38:59.763Z
Answers.UserDisplayName: Chris Burgess
Body: <p>I have a fresh Installation of joomla and civicrm:
  civiCRM = civicrm-4.6.2-joomla.zip</p>
  
  <p>The Installation went well, however I just receive a white (blank) page calling civicrm from the admin_>Components->CiviCRM</p>
  
  <p>the related link: <a href="http://mywebsite.com/administrator/index.php?option=com_civicrm" rel="nofollow">http://mywebsite.com/administrator/index.php?option=com_civicrm</a></p>
  
  <p>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.</p>
  
  <p>May be someone can give me a hint where to start to investigate. Thank you!</p>
  
  <p>B ert</p>
  
  <p>System Information</p>
  
  <p>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 </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-28T18:05:31.863Z
Comments.Text: 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.
Comments.UserDisplayName: Coleman
Tags: <joomla><wsod>
Title: Joomla Backend (Admin), CIVI White Page after installation
ThreadText: # Joomla Backend (Admin), CIVI White Page after installation
  
  (Asked by: username_0 on 2015-05-28)
  
  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!
  
  username_0
  
  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
  
  **Tags:** joomla, wsod
  
  > **Comments:**
  > **username_1**: 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.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-05-28. Score: 7 | Accepted answer
  
  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).
  
  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
  
  Stack Overflow: How do I get PHP errors to display?
  Where should one look for logs when debugging a new problem?
  Drupal.org: Blank pages or White Screen of Death
  Joomla SE: What is an efficient way to troubleshoot a White Screen of Death
  
  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!
  
  > **Comments:**
  > **username_2**: 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?  
  > **username_3**: I'd vote this up 10 times if I could.  I'm going to link to this from the Community Support Documentation: http://wiki.civicrm.org/confluence/display/CRM/Community+Support+Documentation  
  > **username_0**: 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 http://10.10.10.11/si_backoffice/administrator/index.php?option=com_installer&view=install brings up a white page.  
  > **username_2**: I've re-posted this against a more generic question @ http://civicrm.stackexchange.com/questions/6399/civicrm-is-showing-a-blank-page-white-screen-how-do-i-debug-this/6400  
  
  ---
  
  