-
Bug
-
Resolution: Fixed
-
Major
-
6.2.10
-
None
-
None
-
Empty show more show less
-
UI FW 33
-
1
Steps to reproduce
- http://nightly.magnolia-cms.com/.magnolia/admincentral#app:pages-app:detail;/travel:edit
- move a component
Expected results
I can move the component
Actual results
An exception is thrown.
Workaround
Explicitly specify version of magnolia-pages-editor-widget to by in sync with pages app version.
Development notes
~/git/addon-packs/magnolia-addon-webapp [master] $ mvn dependency:tree -o ... +- info.magnolia.abtesting:magnolia-abtesting-ui:jar:1.1-SNAPSHOT:compile [INFO] | +- info.magnolia.ui:magnolia-ui-framework-jcr:jar:6.2.10:compile [INFO] | +- info.magnolia.pages:magnolia-pages-app:jar:6.2.9:compile [INFO] | | \- info.magnolia.pages:magnolia-spa-rendering:jar:6.2.9:compile [INFO] | | +- info.magnolia.resources:magnolia-resources:jar:3.0.4:compile [INFO] | | \- javax.servlet:javax.servlet-api:jar:4.0.1:provided [INFO] | +- info.magnolia.pages:magnolia-pages-editor-widget:jar:6.2.1:compile
The issue was revealed because of a binary incompatible change introduced by PAGES-337.
The other issue might be that the pages editor widget in AB testing is not marked as provided.
Managing it in CE pom sounds safer though as this mistake can be done by anybody else and potential issues are hard to find.
Acceptance criteria
