StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>For syntax errors, you need to enable error display in the php.ini. By default these are turned off because you don't want a "customer" seeing the error messages. <a href="http://php.net/manual/en/errorfunc.configuration.php#ini.error-reporting" rel="noreferrer">Check this page</a> in the PHP documentation for information on the 2 directives: <code>error_reporting</code> and <code>display_errors</code>. <code>display_errors</code> is probably the one you want to change. If you can't modify the php.ini, you can also add the following lines to an .htaccess file:</p> <pre><code>php_flag display_errors on php_value error_reporting 2039 </code></pre> <p>You may want to consider using the value of E_ALL (as mentioned by Gumbo) for your version of PHP for <code>error_reporting</code> to get all of the errors. <a href="http://docs.php.net/manual/en/errorfunc.constants.php" rel="noreferrer">more info</a></p> <p>3 other items: (1) You can check the error log file as it will have all of the errors (unless logging has been disabled). (2) Adding the following 2 lines will help you debug errors that are not syntax errors:</p> <pre><code>error_reporting(-1); ini_set('display_errors', 'On'); </code></pre> <p>(3) Another option is to use an editor that checks for errors when you type, such as <a href="http://www.nusphere.com/products/phped.htm" rel="noreferrer">PhpEd</a>. PhpEd also comes with a debugger which can provide more detailed information. (The PhpEd debugger is very similar to xdebug and integrates directly into the editor so you use 1 program to do everything.)</p> <p>Cartman's <a href="http://www.ibm.com/developerworks/library/os-debug/" rel="noreferrer">link</a> is also very good: <a href="http://www.ibm.com/developerworks/library/os-debug/" rel="noreferrer">http://www.ibm.com/developerworks/library/os-debug/</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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