#48061 closed enhancement (fixed)
Do an action when a 404 is triggered
| Reported by: | johnbillion | Owned by: | johnbillion |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.5 |
| Component: | Query | Version: | |
| Severity: | normal | Keywords: | has-patch has-dev-note |
| Cc: | Focuses: |
Description
For debugging purposes it would be great to be able to determine what triggered a 404.
If a plugin manually calls $wp_query->set_404() it can cause much head scratching. If an action was fired within this method, it would allow debugging plugins to inspect the stack trace and determine what triggered it.
Attachments (1)
Change History (6)
This ticket was mentioned in Slack in #core by whyisjake. View the logs.
6 years ago
#5
@
6 years ago
- Keywords has-dev-note added
This received a call out in the Miscellaneous Developer Changes in 5.5 dev note: https://make.wordpress.org/core/2020/07/29/miscellaneous-developer-focused-changes-in-wordpress-5-5/.
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
In 47509: