[PAGES-209] Versioning Actions Disabled on Public Instances Created: 05/Nov/19 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 6.1, 6.1.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Chris Jennings | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
A client has found that versioning actions are available on public instances despite there not being any version history available. They request that actions related to versioning are disabled on public instances to remove the impression that version history is available to them on these instances. The attached screenshot shows how "Show versions", "Restore version", etc. are available on a public instance but generate an error message when used. |
| Comments |
| Comment by Roman Kovařík [ 11/Mar/21 ] |
|
If there is use case to use admincentral on public instances (and triggering versioning actions), please reopen. |