Opened 9 years ago
Closed 5 years ago
#36981 closed enhancement (worksforme)
Add optional stack trace dump for WordPress deprecation notices
Reported by: | mark-k | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
When you have many plugins and complex theme, it is harder to pinpoint the root code which uses a deprecated function/parameter. An optional stack trace can make it easier, probably under some new defined flag.
Attachments (1)
Change History (3)
Note: See
TracTickets for help on using
tickets.
This was discussed in the APAC Core triage today.
Sorry about the length of time taken to respond, we've decided to close this as
worksforme
as stack traces are available due to the use of PHP'strigger_error()
function.I've attached a screen shot with a call to
get_postdata()
to demonstrate.To make use of these, you'll need to enable debug mode in wp-config.php