View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003334 | Composr | core | public | 2017-08-31 14:58 | 2018-02-10 00:25 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003334: Logging improvements | ||||
| Description | From the error log screen link to all other .log files (will need to proxy it to read content). Have an auto-refresh feature. Implement a tasks.log. Task hooks would be able to write to this log to show their current progress (using an API call that automatically handles timestamps and hook name). | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 3 | ||||
| Sponsorship open | |||||
|
|
Implemented tasks log. For now I am happy just leaving the other logs as a disk based mechanism. Users with advanced sites will typically be happy enough using a unix shell. Each log need manually setting up to start logging anyway (as described in the code book). |
|
|
Actually I have added supported for viewing any .log file that is there, and clearing, deleting, or downloading them. We already did viewing for the permissions log so it wasn't a lot of code. |
|
|
We can consider this done. I don't want to do auto-refresh. Manual refresh is easy enough, especially on the download links (which open a text dump that can be refreshed). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-08-31 14:58 | Chris Graham | New Issue | |
| 2018-02-05 00:56 | Chris Graham | Note Added: 0005436 | |
| 2018-02-09 23:55 | Chris Graham | Note Added: 0005485 | |
| 2018-02-10 00:25 | Chris Graham | Note Added: 0005486 | |
| 2018-02-10 00:25 | Chris Graham | Status | non-assigned => resolved |
| 2018-02-10 00:25 | Chris Graham | Resolution | open => fixed |
| 2018-02-10 00:25 | Chris Graham | Assigned To | => Chris Graham |
