4.2.3 changes the behaviour back to how it was in 4.2.1 and right back to 3.0.0.
It hides notices and warnings by default.
However, changing the bahviour in 4.2.2 is a simple matter of adding one line to the config.php file.
Customers have been adding lines to the config.php file for many years for all sorts of reasons - disabling hooks, increasing memory, enabling and disabling debug mode, to name but a few.
When I said "there's nothing to fix", I'm talking about the fact that many people don't understand that these are warnings and notices, not errors, (not knowing the difference is perfectly understandable since it LOOKS like an error to the untrained eye), and then when we give them the line to add to config.php they object, claiming we're "hiding errors" and demand we "fix them rather than hide them". All of this confusion is understandable, since we don't expect customers to have a working knowledge of php programming to be able to run the software, but the correct situation should always be explained in "layman's terms", in my view. Customers have a right to understand what we're asking them to do with their product, should they want to do so.
It hides notices and warnings by default.
However, changing the bahviour in 4.2.2 is a simple matter of adding one line to the config.php file.
Customers have been adding lines to the config.php file for many years for all sorts of reasons - disabling hooks, increasing memory, enabling and disabling debug mode, to name but a few.
When I said "there's nothing to fix", I'm talking about the fact that many people don't understand that these are warnings and notices, not errors, (not knowing the difference is perfectly understandable since it LOOKS like an error to the untrained eye), and then when we give them the line to add to config.php they object, claiming we're "hiding errors" and demand we "fix them rather than hide them". All of this confusion is understandable, since we don't expect customers to have a working knowledge of php programming to be able to run the software, but the correct situation should always be explained in "layman's terms", in my view. Customers have a right to understand what we're asking them to do with their product, should they want to do so.
Comment