[MAGNOLIA-2809] Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode Created: 03/Jul/09  Updated: 23/Jan/13  Resolved: 07/Sep/09

Status: Closed
Project: Magnolia
Component/s: templating, updatemechanism
Affects Version/s: 4.0
Fix Version/s: 4.0.3, 4.1.1

Type: Bug Priority: Blocker
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MAGNOLIA-2564 update: update template and paragraph... 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

 Description   

There are 2 conflicting tasks for templates:

  1. renamed path to templatePath - that is 100% correct
  2. move non-default template parameters to the parameters subnode. The bug is that this task consider path to be the property to keep, while these have just been renamed to templatePath.

Fixing this will require careful writing of update tasks for both 4.0.3 and 4.1.1

workaround: move the templatePath nodedata of your templates from the parameters subnode back into the template node itself.



 Comments   
Comment by Magnolia International [ 07/Aug/09 ]

Existing instances need to be fixed. This update task being registered for 4.0, just modifying the task itself won't fix any.

Comment by Magnolia International [ 01/Sep/09 ]

tests missing

Generated at Mon Feb 12 03:40:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.