#5473 closed defect (bug) (fixed)
Suppress DB errors unless WP_DEBUG is true
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 2.3.2 | Priority: | normal |
Severity: | normal | Version: | 2.3.1 |
Component: | General | Keywords: | show_errors wpdb db mysql has-patch |
Focuses: | Cc: |
Description
WordPress should assume that it's a production environment and not show DB errors.
Attachments (2)
Change History (13)
#3
in reply to:
↑ 1
@
17 years ago
Replying to Viper007Bond:
Perhaps an alternate solution is to show them to administrator users regardless (
manage_options
?), and only to everyone if WP_DEBUG is on.
I think this might be a good idea, but it should probably be done at the WP_DEBUG level, if possible.
#4
@
17 years ago
When doing hide/show pair, this patch restores the show state to what it was prior to hiding. This way we don't have to check WP_DEBUG everywhere.
Patch also does an error_log() inside print_error() so that the error info is always available in the error log.
Note: See
TracTickets for help on using
tickets.
Not sure how I feel about this. Spitting out error messages told a lot of people their plugins didn't work with 2.3 and is a useful thing for site owners. With them hidden, it'd go missed by most and they wouldn't know why something wasn't working.
Perhaps an alternate solution is to show them to administrator users regardless (
manage_options
?), and only to everyone if WP_DEBUG is on.