对于那些使用nginx并且即使文件<?PHP echo 123;在我的情况下，我在nginx配置文件中没有这个必要的PHP选项:

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

fastcgi_params文件中没有这个选项，所以PHP不起作用，日志中也没有任何错误。

对于快速，动手故障排除，我通常建议在这里SO:

error_reporting(~0); ini_set('display_errors', 1);

放在正在进行故障排除的脚本的开头。这并不完美，完美的变体是你也在PHP .ini中启用它，并在PHP中记录错误以捕捉语法和启动错误。

这里列出的设置显示所有错误、通知和警告，包括严格的错误，而不考虑使用哪个PHP版本。

接下来要考虑的事情:

安装Xdebug并在IDE中启用远程调试。

也可以看到:

错误报告(PHP正确方式) 预定义ConstantsDocs error_reporting()文档 display_errorsDocs

打开错误报告是正确的解决方案，但是它似乎不会在打开它的程序中生效，而只会在随后包含的程序中生效。

因此，我总是创建一个文件/程序(我通常称之为“genwrap.php”)，它的代码本质上与这里流行的解决方案相同。打开错误报告)，然后它还包括我实际想要调用的页面。

实现这个调试有两个步骤;

首先，创建genwrap.php，然后把下面的代码放进去:

<?php
error_reporting(-1);
ini_set('display_errors', 'On');

include($_REQUEST['page']);
?>

第二，将你想要调试的程序/页面的链接改为通过genwrap.php，

例如:改变:

$.ajax('dir/pgm.php?param=val').done(function(data) { /* ... */

to

$.ajax('dir/genwrap.php?page=pgm.php&param=val').done(function(data) { /* ... */

我推荐Nette Tracy来更好地可视化PHP中的错误和异常:

尝试在实际的php文件中设置错误报告级别。或者，像其他人建议的那样，检查你的服务器设置——可能是php.ini中的一些东西，或者是关于你的主机的一些限制。不要仅仅依赖于。htaccess。此外，在排除故障时，print_r任何您认为可疑的变量。

这个答案是由冗余部门为您带来的。

ini_set() / php.ini / .htaccess / .user.ini The settings display_errors and error_reporting have been covered sufficiently now. But just to recap when to use which option: ini_set() and error_reporting() apply for runtime errors only. php.ini should primarily be edited for development setups. (Webserver and CLI version often have different php.ini's) .htaccess flags only work for dated setups (Find a new hoster! Well managed servers are cheaper.) .user.ini are partial php.ini's for modern setups (FCGI/FPM) And as crude alternative for runtime errors you can often use: set_error_handler("var_dump"); // ignores error_reporting and `@` suppression error_get_last() Can be used to retrieve the last runtime notice/warning/error, when error_display is disabled. $php_errormsg Is a superlocal variable, which also contains the last PHP runtime message. isset() begone! I know this will displease a lot of folks, but isset and empty should not be used by newcomers. You can add the notice suppression after you verified your code is working. But never before. A lot of the "something doesn't work" questions we get lately are the result of typos like: if(isset($_POST['sumbit'])) # ↑↑ You won't get any useful notices if your code is littered with isset/empty/array_keys_exists. It's sometimes more sensible to use @, so notices and warnings go to the logs at least. assert_options(ASSERT_ACTIVE|ASSERT_WARNING); To get warnings for assert() sections. (Pretty uncommon, but more proficient code might contain some.) PHP7 requires zend.assertions=1 in the php.ini as well. declare(strict_types=1); Bending PHP into a strictly typed language is not going to fix a whole lot of logic errors, but it's definitely an option for debugging purposes. PDO / MySQLi And @Phil already mentioned PDO/MySQLi error reporting options. Similar options exist for other database APIs of course. json_last_error() + json_last_error_msg For JSON parsing. preg_last_error() For regexen. CURLOPT_VERBOSE To debug curl requests, you need CURLOPT_VERBOSE at the very least. shell/exec() Likewise will shell command execution not yield errors on its own. You always need 2>&1 and peek at the $errno.