Bug #79161 [Csd->Nab]: ini_set causes 500 error with no error text

Edit report at https://bugs.php.net/bug.php?id=79161&edit=1 ID: 79161 Updated by: requinix@php.net Reported by: martin dot barker at thisisbeacon dot com Summary: ini_set causes 500 error with no error text -Status: Closed +Status: Not a bug Type: Bug Package: FPM related Operating System: Linux ip-10-1-28-252 4.15.0-1051 PHP Version: 7.4.2 Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2020-01-23 16:51:59] bugreports at gmail dot com <?php ini_set("display_error", true); echo "durrrr"; ?> this is a completly useless comment * 1: display_error is wrong spelled * 2: display_errors don't change the error_reporting ------------------------------------------------------------------------ [2020-01-23 16:23:39] martin dot barker at thisisbeacon dot com Closed unable to replicate on another box ------------------------------------------------------------------------ [2020-01-23 16:11:35] martin dot barker at thisisbeacon dot com I would also say that not supporting or testing against one of the biggest applications to use PHP is a little lax in QA. The fact is a gave a test scenario that is very easy to follow and take a couple of mins to set up not using some small obscure system. ------------------------------------------------------------------------ [2020-01-23 16:06:19] martin dot barker at thisisbeacon dot com ok, <?php ini_set("display_error", true); echo "durrrr"; ?> ------------------------------------------------------------------------ [2020-01-23 15:46:23] sjon@php.net Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. additionally you could have a look at the error_log setting as it might provide more information. You should also try disabling any extensions to see if that helps ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=79161 -- Edit this bug report at https://bugs.php.net/bug.php?id=79161&edit=1