Doc #71340 [Com]: php_admin_value[error_reporting] in fpm/apache conf can be bypassed in user code

Edit report at https://bugs.php.net/bug.php?id=71340&edit=1 ID: 71340 Comment by: gpointorama at gmail dot com Reported by: gpointorama at gmail dot com Summary: php_admin_value[error_reporting] in fpm/apache conf can be bypassed in user code Status: Analyzed Type: Documentation Problem Package: PHP options/info functions Operating System: Any PHP Version: 7.0 Block user comment: N Private report: N New Comment: I can only say that is a shame that core php devs are totally unaware on how useful this feature is in general and how is used from an hosting provider point of view. And we are not convinced about your decision on how good breaking backward compatibility is and also the other performance motivations behind this change. Previous Comments: ------------------------------------------------------------------------ [2018-06-06 13:32:59] nikic@php.net I haven't been convinced by what has been said and it seems that @requinix concurs, so I'm switching this to a documentation issue. This backwards-incompatible change needs to be mentioned in the PHP 7.0 upgrading guide. ------------------------------------------------------------------------ [2018-06-06 11:19:14] admin at inwebse dot com Up. What with this problem? ------------------------------------------------------------------------ [2018-05-25 19:55:32] admin at inwebse dot com Up. Any progress? ------------------------------------------------------------------------ [2018-05-15 10:33:45] admin at inwebse dot com Any news? ------------------------------------------------------------------------ [2018-05-06 16:06:29] php at alternize dot com for anyone who thinks "php_admin_value[error_reporting]" should not be immutable: nobody is forced to use this. if you want to allow apps/users to change the error level, use "php_value[error_reporting]" and you're good. whoever sets "php_admin_value[error_reporting]" certainly has her/his reasons - there *are* valid reasons for doing so, some outlined in this bug's comments. ------------------------------------------------------------------------ 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=71340 -- Edit this bug report at https://bugs.php.net/bug.php?id=71340&edit=1