[MGNLCAMPU-57] Cannot update Campaign Publisher Module from 1.0 to 1.1 Created: 18/Jan/17  Updated: 14/Mar/17  Resolved: 10/Mar/17

Status: Closed
Project: Campaign Publisher
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1.1

Type: Bug Priority: Critical
Reporter: Sebastian Bauch Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 5h
Original Estimate: Not Specified

Attachments: Text File magnolia-error.log    
Issue Links:
relation
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:
Visible to:
Frank Sommer, Gernot Fussan, Sergej Steinbach
Sprint: Basel 87
Story Points: 3

 Description   

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.

Generated at Sun Feb 11 23:57:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.