Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:config:understanding_500 [2018/09/12 19:43] Jackson Zhang [Different level of Rewrite rules misplaced to the wrong level] |
litespeed_wiki:config:understanding_500 [2018/09/20 14:00] Lisa Clarke [PHP Code with wrong php configuration settings] Proofreading |
||
|---|---|---|---|
| Line 130: | Line 130: | ||
| It will bring the website to 500 immediately. | It will bring the website to 500 immediately. | ||
| This is only one example. Many times, wrong PHP syntax will lead to a 500 error. | This is only one example. Many times, wrong PHP syntax will lead to a 500 error. | ||
| + | |||
| + | ===== PHP Code with wrong php configuration settings ===== | ||
| + | |||
| + | Sometimes, a 500 error may be not easy to locate. If you move ''.htaccess'' to ''.htaccess.bak'' and move ''php.ini'' to ''php.ini.bak'', and the 500 error still happens, it might mean there is something wrong in the PHP code. That can be hard to find. | ||
| + | |||
| + | We experienced a case with WHMCS. Someone placed an incorrect setting in ''configuration.php'': | ||
| + | $display_errors = E_All; | ||
| + | |||
| + | ''E_All'' is an incorrect value for the PHP ''$display_errors'' setting. Rather, it is meant for the ''$error_reporting'' setting. ''$display_errors'' should be either ''true''/''false'', or ''on''/''off''. We changed it to ''true'', and that fixed the 500 error. | ||
| + | $display_errors = true; | ||
| ===== PHP Handler Not Set ===== | ===== PHP Handler Not Set ===== | ||