-
Improvement
-
Resolution: Done
-
Major
-
6.2
-
None
-
-
Empty show more show less
-
Maintenance 51, Maintenance 52
-
8
It's possible that pages can end up in a state where the hasVersion mixin exists but the page doesn't have any versions.
'stories': 'jcr:mixinTypes': ['mgnl:hasVersion']
The stories page is an example of a bootstrap file that needs to be fixed (see MGNLDEMO-347) but I assume there are other ways versions can be lost (see Broken Version History). Can we provide a way to fix the problem through the UI or at least provide some message as to why the drop down is empty? I think it's confusing for the user and could end up causing other systems depending on versions to behave incorrectly.
Acceptance criteria
- is related to
-
MGNLDEMO-347 Stories page has a broken version history
- Closed
- relates to
-
MAGNOLIA-8048 Remove hasVersion mixin when there is no version
- Closed