Hi all,
my app is showing exceptions (especially E_WARNING) in production env even thought i’ve disabled error reporting in php.ini and in grav admin.
Are there others occurrencies to disable Woops code exposing in production?
Hi all,
my app is showing exceptions (especially E_WARNING) in production env even thought i’ve disabled error reporting in php.ini and in grav admin.
Are there others occurrencies to disable Woops code exposing in production?
In the Admin panel under Configuration, System, you can set Display Errors to “Simple Error” which I believe will do what you want.
Or maybe fix the exceptions thrown?
I think that the problem relies in file_exists caching mechanism (used in Grav core files). I don’t want to monkey patch core files or add try catch around it.
Now i’ve added theme://languages directory so that it caches dir presence… meh