View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002118 | Composr | actionlog | public | 2015-12-15 03:08 | 2022-08-15 02:14 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002118: Implement undo/undelete | ||||
| Description | The revisions system of v10 holds the data (in Resource-fs JSON form) that was just overwritten/erased, so add code to automatically restore this. Some of the code is already laid out for this. Mainly it is a matter of ensuring Resource-fs works robustly, particularly in terms of restoring to a path that may no longer exist (e.g. restoring a post to a topic that was itself later deleted - in which case a new 'shell' topic should auto-create). | ||||
| Tags | Type: Cross-cutting feature, Type: Usability (major) | ||||
| Time estimation (hours) | 8 | ||||
| Sponsorship open | |||||
| related to | 0001756 | resolved | Chris Graham | Set up official revisions system |
| related to | 0002119 | non-assigned | Extend revisions to all resource types | |
| related to | 0004718 | non-assigned | High quality staging server support (content push) |
|
|
Also necessary to consider how associated on-disk files would be handled. Are these all going to go into the action log as base64-encoded data? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-08 12:47 | Chris Graham | Tag Attached: Type: Usability | |
| 2016-12-08 12:50 | Chris Graham | Tag Renamed | Type: Usability => Type: Usability (major) |
| 2016-12-08 16:17 | Chris Graham | Tag Attached: Type: Cross-cutting feature | |
| 2021-11-18 01:11 | Chris Graham | Relationship added | related to 0002119 |
| 2021-11-18 01:11 | Chris Graham | Relationship added | related to 0004718 |
| 2022-08-15 02:14 | Chris Graham | Note Added: 0007455 |
