Frank_Picabia
-
Posts
4 -
Joined
-
Last visited
Posts posted by Frank_Picabia
-
-
Hi,
I'm getting an answer from "php-i | grep error" , and seeing this
error_reporting => 22527 => 22527But you said it should be this? I suppose if one adds up all those binary codes it comes to this?
-
Thanks for the response.
It's a Redhat Linux 8 system. There's a good number of ini files, but /etc/php.ini contains the line:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICTwhile
grep -r error_report /etc/php.d
produces no results.
-
We already know why there are deprecated PHP warnings while running an old piece of code under PHP 8.0
The PHP code with legacy issues will be updated by someone new about to be hired.For now, we just want php being run out of a cron to use the settings we have in php.ini:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICTThis isn't working. Every time the cron runs, it will email the deprecated warning.
* * * * * php /usr/local/cron.php >> /usr/local/cron.log
Someone claimed in an online forum that for PHP run at the command line,
as it would be for a cron, it doesn't have this control over error reporting.
I don't know if that is accurate.As a solution for the time being, I've added 2>&1 >> /dev/null
to the end of the cron line. But it would be better to use the php error_reporting
preference if we could.
How to suppress output from PHP on CLI while deprecated warnings are printed
in PHP Installation and Configuration
Posted
We never did find a solution to controlling the deprecation notices in PHP 8.0.
In the meantime, it was found we had a requirement to run the site on PHP 7.4 until some of the legacy pieces can be updated by the application administrator.