#52335 closed enhancement (wontfix)
Automatic report Fatal Error
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 5.2 |
Component: | Site Health | Keywords: | |
Focuses: | Cc: |
Description
Hello,
As an Ubuntu error occurring crash with its system, I've just discovered their command "ubuntu-bug" which send and report crash log to their "Trac" located on https://bugs.launchpad.net/
Typically, when an apps crash, Ubuntu is writing a log in /var/crash
folder and the command $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
is sending and creating the bug report
I think, we should be able to do almost the same by checking if the Fatal Error is created by WordPress, maybe by searching "wp-include" or "wp-admin" in the path and automatically create a Trac ticket.
There's also a GDPR question because of sending private data.
Change History (2)
#2
in reply to:
↑ 1
@
2 years ago
- Keywords 2nd-opinion close removed
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed
Replying to Clorith:
I'm not sure if this is a good idea, it would lead to a lot of messy and (often times incorrect) information being pushed towards the ticketing system here.
There's also the concern that you need a WordPress.org account to create tickets, opening this up to just allow anyone to push tickets would be a potential outlet for abuse.
I agree with this assessment. Going to close out as a wontfix
.
I'm not sure if this is a good idea, it would lead to a lot of messy and (often times incorrect) information being pushed towards the ticketing system here.
There's also the concern that you need a WordPress.org account to create tickets, opening this up to just allow anyone to push tickets would be a potential outlet for abuse.
If a host or similar wanted to capture errors and function as a warden and file upstream tickets to trac for legitimate issues, this is already possible through the use of filters, like for example
wp_php_error_message
in a platform-dependent mu plugin or similar, or their own custom error handler.With this in mind, I'm going to suggest this ticket be closed, but will leave it open for a while to see if there's others opinions.