MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#254 — Need to log and report errors properly
Attached to Project —
MODx
Opened by Victor Brilon (vbrilon) - Wednesday, 08 February 2006, 03:30PM
Last edited by Mark Kaplan (mark2005) - Thursday, 16 February 2006, 10:46PM
Opened by Victor Brilon (vbrilon) - Wednesday, 08 February 2006, 03:30PM
Last edited by Mark Kaplan (mark2005) - Thursday, 16 February 2006, 10:46PM
| Task Type | Feature Request |
|---|---|
| Category | Core Distribution |
| Status | Researching |
| Assigned To |
Jason Coward (opengeek) |
| Operating System | All |
| Severity | Medium |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.1 |
| Due in Version | 1.0 |
| Due Date | Undecided |
| Percent Complete |
|
Details
We need to log and report on 404 errors.Currently the code does this in the log() function:
if($docid==$this->config['error_page']) {
exit; //stop logging 404's
}
So it ignores the 404s but even worse, it doesn't even know it's a 404 since any kind of error will land you on the error page and trigger this.
So we need to do this:
1) Separate the different kind of HTTP status codes into different functions
2) Keep track of the current status of the current request and
3) Log them into the DB properly and add them to the report view
This task depends upon
This task blocks these from closing
Comment by Jason Coward (opengeek) -
Thursday, 23 March 2006, 02:51AM
I'm going to handle the codes as part of a separate response object and will be refactoring error reporting and logging for 1.0 roadmap; I'll be posting and re-organizing for the 1.0 roadmap very soon