View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006007 | Composr | core | public | 2024-10-18 17:37 | 2024-10-19 20:01 |
| Reporter | Patrick Schmalstig | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0006007: Add archiving capabilities to anything with categories | ||||
| Description | Any type of content which support categories should have the ability to get archived. Archiving should be separate from turning off validation on content. Here's why: * Non-validated content is not "archived"; it means the content is not ready to be live (e.g. has not been "validated" as-in reviewed) * Using the validation addon to archive content creates a UI issue because the staff checklist will now count these items as needing validation (when really they're just archived and never intending to be public again). Add an option in addition to delete to "archive" an entry (if it supports categories). Here's what will happen: - If the categories are a tree, an "Archived" category will be created under root, followed by the original category structure of the content being archived. And the content will be moved into that category. The "Archived" category by-default will only have view permissions for staff. - If the categories are not in tree structure, simply an "Archived" category will be created, and the content moved to it. The "Archived" category by-default will only have view permissions for staff. Sitemap should not list anything under these categories. | ||||
| Tags | Roadmap: Over the horizon | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-10-18 17:37 | Patrick Schmalstig | New Issue | |
| 2024-10-18 17:37 | Patrick Schmalstig | Tag Attached: Roadmap: Over the horizon |
