[BLOSSOM-94] Migration module script scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle Blossom templates Created: 20/Jun/12  Updated: 02/Oct/12  Resolved: 03/Jul/12

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0.1

Type: Bug Priority: Major
Reporter: Tomas Brimor Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-291 Document inability of automated migra... Closed
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:

 Description   

Migration module script scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle Blossom templates.

We are using blossom for templates and the migrationscript does not update our metadata for our pages to the new blossom template ids.



 Comments   
Comment by Ondrej Chytil [ 22/Jun/12 ]

Thanks for reporting the issue Tomas, ticket is already in current changelog.

Comment by Tomas Brimor [ 25/Jun/12 ]

Any ETA on 1.1.2?

Comment by Ondrej Chytil [ 25/Jun/12 ]

We hope that it will be ready for release in the second half of July.

Comment by Tobias Mattsson [ 29/Jun/12 ]

Hello Tomas,

When upgrading to 4.5 you should also be upgrading to Blossom 2.0. The naming convention for Blossom templates changed between versions 1.x and 2.0. The previous convention was to use the path of the controller with leading and trailing slashes removed and slashed within the name converted to underscores. In Magnolia 4.5 template ids are in the format of <moduleName>:<path>, as a consequence the blossom convention was updated and you now specify the id explicitly on your controller. Like so: @Template(id="myModule:pages/news", title="News").

There's no direct correlation from the previous convention to the new one. Therefor it's not possible for a script to automatically convert between them. What you can do is write an update task that scans your pages and changes from the old names to the new ones you have annotated your class with.

I have added a page on the wiki with such an update task: http://wiki.magnolia-cms.com/display/WIKI/Migrating+content+when+upgrading+to+Blossom+2

Comment by Jan Haderka [ 02/Jul/12 ]

If it's not possible to automatically migrate, then there should be at least a warning printed out during upgrade alerting users to the need to change it manually.

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