Databases
StackOverflow2013
Postsdbo
POphp white screen of death
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POphp white screen of death
    primarykey
    data
    text
    <p>I have browsed several other questions, and tried various solutions related to error reporting, including </p> <pre><code>ini_set('display_errors',true); error_reporting(E_ALL); </code></pre> <p>but I am still stuck with the white screen of death. This seems to happen only on pages when I use my own object oriented classes. However, the OOP scripts execute successfully, but I am unable to get the HTML to show. Occasionally, I can get it to catch an Exception but it is intermittent.</p> <p>For example, I have a this method:</p> <pre><code>public function getSubdomain() { $this-&gt;data-&gt;query('SELECT * FROM users WHERE email=:email'); $this-&gt;data-&gt;bind(':email', $this-&gt;email); $this-&gt;data-&gt;execute(); if($this-&gt;data-&gt;rowCount() == 0) throw new Exception('There is no account associated with this e-mail address.'); $curr = $this-&gt;data-&gt;single(); return $curr['subdomain']; } </code></pre> <p>^^ That will execute just fine and I can get it to print from the OOP class using <code>die($curr['subdomain']);</code>, but if I try displaying it on a page using PHP, nothing. No errors, so logs, no source code, absolutely nothing.</p> <p>I am using MultiViews with Apache, and my DB queries are done using a custom PDO class.</p> <p>I have run</p> <pre><code># php -l new.php </code></pre> <p>directly on the server and it reports</p> <pre><code>No syntax errors detected in new.php </code></pre> <p>When I run the exact same setup on WAMP locally, it works without a problem, but once I migrated over to my CentOS/Apache/PHP machine, all hell broke loose. MySQL is on a seperate server, but has no problems.</p> <p>I can provide much more specific code (both my own and conf files from the server) as needed, I just want to avoid anything arbitrary due to the nature of the question. Any suggestions on where to go from here (ie, different methods of error reporting, etc.)? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USbrokekidweb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POphp white screen of death
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POphp white screen of death
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POphp white screen of death
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have liberal error logging turned on?
      singulars
      1. POphp white screen of death
      1. USMachavity
    2. COEnable display_errors and _reporting in the php.ini, in case of syntax errors it's way too late in any script. Also peek at your webservers error.log for runtime errors. Add piles of debug output if unfruitful, else use an IDE with xdebug for stepping through.
      singulars
      1. POphp white screen of death
      1. USmario
    3. COMake sure you have logging enabled in your php.ini and outputting to an error log. Sending php errors to the browser is not always reliable. Use Chrome to see if the server is sending a 500 status code. If so, check the Apache log for errors. Make sure Apache error logging is enabled. I often get white screens from invalid .htaccess files.
      singulars
      1. POphp white screen of death
      1. UScgTag
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload