[MGNLMIGRATION-277] I am doing an upgrade from 4.4.6 to 4.5.8 and I get 'Error while installing or updating standard-templating-kit module'. Created: 08/Nov/13  Updated: 16/Sep/15  Resolved: 18/Nov/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: Migration Task
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Todd Posius Assignee: Robert Šiška
Resolution: Cannot Reproduce Votes: 0
Labels: migration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File magnolia-error.log     HTML File migrationReport(2).html    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

It has installed some of the modules, but there are about 56 left. I have included the migrationReport. Which shows the one error that occurs when the I have removed the theme.pop node. The reason I have removed that node is because I am also getting the following error if the theme.pop is set up. I have tried to import another pop or manually creating it, but everytime I get this error: Error while installing or updating standard-templating-kit module. Task 'Configure theme pop' failed. (ItemExistsException: a node with uuid 3053d5e1-aba7-4156-9552-85bd03102302 already exists!). The uuid is the same everytime. I am not sure how to get around this issue.



 Comments   
Comment by Todd Posius [ 13/Nov/13 ]

Here are the error logs from when we were trying to do the install with and without the pop node set up.

Comment by Todd Posius [ 14/Nov/13 ]

After looking at MGNLSTK-989, I was able to come up with a way to complete my installation. I modified config.modules.standard-templating-kit.config.themes.pop.xml in the magnolia-module-standard-templating-kit-2.0.9.jar . I removed the xml where the uuid for pop was getting set.

Comment by Todd Posius [ 14/Nov/13 ]

You can close this ticket.

Comment by Robert Šiška [ 18/Nov/13 ]

Hi Todd,

sorry I left you stranded here, but I couldn't reproduce the bug.
The bootstrap files are identical, but they should be replaced on update, not throw an error.

The only way I see this could happen is that STK module was being installed, not updated
and its files were already in the configuration.

Also, please consider using latest release of 4.5 branch as your migration target.

Robert

Comment by Michael Mühlebach [ 16/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 10:18:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.