You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2020. It is now read-only.
WordPress errors are currently turned off by default and have to be explicitly enabled with
--show-wp-errors=true`
The reasoning has been that WordPress is too noisy with errors, but I've ended up missing some critical errors while developing Mongoose (which was pretty embarrassing), and I've just had a situation on homeownership where I can see a significant warning (indicating a bug in this case) but Alex couldn't, because he's using the default settings.
Developing using the current default settings seems to be equivalent to developing with define('WP_DEBUG', false); and/or ini_set("display_errors", 0);, which seems to be generally recognised as a Bad Idea.
Might also be worth considering making --no-sql default to false if it's not already, but I'm don't have as clear an argument for that.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
WordPress errors are currently turned off by default and have to be explicitly enabled with
The reasoning has been that WordPress is too noisy with errors, but I've ended up missing some critical errors while developing Mongoose (which was pretty embarrassing), and I've just had a situation on homeownership where I can see a significant warning (indicating a bug in this case) but Alex couldn't, because he's using the default settings.
Developing using the current default settings seems to be equivalent to developing with
define('WP_DEBUG', false);
and/orini_set("display_errors", 0);
, which seems to be generally recognised as a Bad Idea.Might also be worth considering making
--no-sql
default to false if it's not already, but I'm don't have as clear an argument for that.The text was updated successfully, but these errors were encountered: