![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 14 years ago
Closed 11 years ago
#23062 closed enhancement (maybelater)
Issue warnings for deprecated and wrong behavior in pre-release builds
| Reported by: | nacin | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Bootstrap/Load | Version: | |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | Focuses: |
Description
Coming out of #22873 and the associated development chat:
_doing_it_wrong(), _deprecated_argument(), _deprecated_file(), and _deprecated_function() should issue an E_USER_WARNING up to and including RC1, and an E_USER_NOTICE otherwise.
Attachments (1)
Change History (8)
Note:
See TracTickets
for help on using tickets.
On the other hand, since these errors only show if you are running WP_DEBUG, maybe it's time to just bump them all to E_WARNING, always? You're either willingly displaying errors, or willingly logging them.
Or, we remove the WP_DEBUG requirement, and always issue an E_NOTICE, even when WP_DEBUG is not set. Then, trigger E_WARNING in development builds, which everyone (WP_DEBUG or not) will see.
Initial patch implements the original suggested behavior.