[MGNLDEMO-287] Demo stories containing wrongly versioning information Created: 22/May/18 Updated: 14/Sep/18 Resolved: 23/Aug/18 |
|
| Status: | Closed |
| Project: | Magnolia Demo Projects |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| 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 |
|
It seems that demo stories are bootstrapped containing versioning information which leads to "restore version" action to be enabled and therefore to thrown an Exception when loading the versions list as there are actually no versions stored. They should be loaded without mgnl:hasVersion information. Steps to reproduce in demo-author
Testing the same in pages app, it can be seen that restore version action is not available till a publication is carried out, so they are bootstrapped correctly. |
| Comments |
| Comment by Antti Hietala [ 23/Aug/18 ] |
|
Duplicate of |