-
Bug
-
Resolution: Fixed
-
Critical
-
1.1
-
None
-
-
Empty show more show less
-
Basel 87
-
3
After the update from 1.0 to 1.1 there is the uuid conflict ( magnolia-error.log ).
In 1.0 Mgnl bootstrap the actions into the {{ /modules/resources}} and in 1.1 it bootstrap the same actions with the same uuid into /modules/resources-app.
*Workaround: *
- Start the instance with the magnolia-campaign-publisher-1.0.jar
- Duplicate the /modules/resources/apps/resources/subApps/browser/actions/selectCampaignAction,
…/browser/actionbar/sections/folder/groups/activationActions/items/selectCampaignAction and
…/browser/actionbar/sections/resource/groups/activationActions/items/selectCampaignAction
nodes to obtain new uuid for these nodes, remove the original one and edit the name on the original – if you still use this old resources app – or if do not, you can completely remove these nodes. - Go into the Tools → JCR → Browsing: campaigns and duplicate/remove the Black-Friday-sample, New-Year-s-Eve-sample and Xmas-sample campaigns you have there. Again remove the original files and edit the names of duplicates on the original.
- After these changes you can stop the instance a replace the old version with the new one.
Acceptance criteria