[MGNLUI-3220] Inability to restore the oldest version Created: 24/Sep/14 Updated: 05/Dec/14 Resolved: 28/Oct/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Zdenek Skodik | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support, versioning | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
If your node's version store is full and you're about to restore the oldest version, the system effectively deletes this version since the autocreated version of current content gets in, hence the oldest one gets out the queue. |
| Comments |
| Comment by Philip Mundt [ 28/Oct/14 ] |
|
Added Warning:
|