Getting errors about several PHP directives not being supported anymore in PHP 5.4
Permalink
Hello everybody,
I installed the most recent version of concrete5 in our companys standardized Vagrant dev environment running a LAMP stack with PHP 5.4.
Problem is that I get a bunch of errors about PHP directives not being supported anymore, i. e. "Directive 'allow_call_time_pass_reference' is no longer available in PHP".
Appearantly this happens because we just copied our old php.ini from our old environment running PHP 5.3 to the new environment without editing it. However, our own Zend Framework 2 apps do not complain about these errors, nor do other CMS' that I tried in our Vagrant machine like Subrion, Contao or Wordpress.
I figured it has to do with the error reporting setting in concrete5 being too verbose, but disabling error output in the debug settings of concrete5 just hides the error messages, it doesn't suppress the errors and I still get message boxes like 'An unknown error occurred' instead of the actual error message. Setting error_reporting to E_ERROR in the php.ini seems also not to change anything.
What causes this sensitive error behavior of concrete5 and is there some quick fix to it?
I installed the most recent version of concrete5 in our companys standardized Vagrant dev environment running a LAMP stack with PHP 5.4.
Problem is that I get a bunch of errors about PHP directives not being supported anymore, i. e. "Directive 'allow_call_time_pass_reference' is no longer available in PHP".
Appearantly this happens because we just copied our old php.ini from our old environment running PHP 5.3 to the new environment without editing it. However, our own Zend Framework 2 apps do not complain about these errors, nor do other CMS' that I tried in our Vagrant machine like Subrion, Contao or Wordpress.
I figured it has to do with the error reporting setting in concrete5 being too verbose, but disabling error output in the debug settings of concrete5 just hides the error messages, it doesn't suppress the errors and I still get message boxes like 'An unknown error occurred' instead of the actual error message. Setting error_reporting to E_ERROR in the php.ini seems also not to change anything.
What causes this sensitive error behavior of concrete5 and is there some quick fix to it?
