- Status Closed
- Percent Complete
- Task Type Feature Request
- Category Backend / Core
-
Assigned To
pizza - Operating System All
- Severity Low
- Priority Very Low
- Reported Version Stable
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#115 - error reporting &| logging framework
Lots of pages dump errors to the screen, but that's no good.
What we really need is proper logging (and/or a logfile)
After that's in, we should have some sort of user-visible feedback for faied operations, but that can tie into the 403 error code thing.
Closed by pizza
2007-02-12 18:29
Reason for closing: Implemented
Additional comments about closing: It's done, and the first user is ported over.
2007-02-12 18:29
Reason for closing: Implemented
Additional comments about closing: It's done, and the first user is ported over.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
The beginnings of this are now in-place.
What I want for now -- an in-session array, $errors[], that we push crap onto.
We have a special 'errors' DIV that is only displayed if there are errors. Displaying errors wipes the DIV.