Opened 10 years ago
Closed 10 years ago
#546 closed enhancement (fixed)
Errors should always be logged to the Error Console
| Reported by: | dstillman | Owned by: | simon |
|---|---|---|---|
| Priority: | major | Milestone: | 1.0 Beta 4 |
| Component: | export | Version: | 1.0 |
| Keywords: | Cc: |
Description
Bibliography, translator and export errors are generally caught, and a generic error is displayed to the user. That makes the errors pretty much impossible to debug when they happen to non-technical users.
In addition to the user-friendly error, these errors should always be logged to the Error Console, either by throwing them or with the explicit logging functions, so that we can have the user follow the instructions on the Reporting Bugs section to find and report the error.
Change History (1)
comment:1 Changed 10 years ago by simon
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
(In [1253]) closes #546, errors should always be logged to the error console
currently, errors that happen during detection (as opposed to translation) are not logged, since it might not be desirable to flood the error console if a site changes its layout in a way that produces errors in the detectCode. if there are any objections, this behavior is easy to change.