提问人：Ryansyah09 提问时间：11/14/2023 最后编辑：mickmackusaRyansyah09 更新时间：11/16/2023 访问量：31
CodeIgniter 4 应用程序中的多个弃用消息和致命错误 [已关闭]
Multiple deprecation messages and fatal errors in CodeIgniter 4 application [closed]
问：
Deprecated: Optional parameter $body declared before required parameter $userAgent is implicitly treated as a required parameter in C:\xampp\htdocs\e-arsip-ci4\system\HTTP\IncomingRequest.php on line 161
Deprecated: filter_var(): Passing null to parameter #3 ($options) of type array|int is deprecated in C:\xampp\htdocs\e-arsip-ci4\system\HTTP\Request.php on line 439
Fatal error: Uncaught ErrorException: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\e-arsip-ci4\app\Config\Events.php:33) in C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php:164 Stack trace: #0 [internal function]: CodeIgniter\Debug\Exceptions->errorHandler(2, 'Cannot modify h...', 'C:\\xampp\\htdocs...', 164) #1 C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php(164): header('HTTP/1.1 500 In...', true, 500) #2 [internal function]: CodeIgniter\Debug\Exceptions->exceptionHandler(Object(ErrorException)) #3 {main} thrown in C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php on line 164
Fatal error: Uncaught ErrorException: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\e-arsip-ci4\app\Config\Events.php:33) in C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php:164 Stack trace: #0 [internal function]: CodeIgniter\Debug\Exceptions->errorHandler(2, 'Cannot modify h...', 'C:\\xampp\\htdocs...', 164) #1 C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php(164): header('HTTP/1.1 500 In...', true, 500) #2 C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php(224): CodeIgniter\Debug\Exceptions->exceptionHandler(Object(ErrorException)) #3 [internal function]: CodeIgniter\Debug\Exceptions->shutdownHandler() #4 {main} thrown in C:\xampp\htdocs\e-arsip-ci4\system\Debug\Exceptions.php on line 164
为什么程序不运行？
答：
0赞
mbwmd
11/15/2023
#1
您必须更改 php 配置以抑制对前端/UI 的错误输出。它应该只记录到文件中。
查找display_errors并display_startup_errors或禁用它。php.ini.htaccess
在您的例子中：php 解析器将error_log输出发送到客户端，这也强制 Web 服务器向客户端发送响应标头。
这样可以防止应用程序设置其最初预期的响应标头，从而导致应用程序失败。
评论