[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24121#action_24121
]
Hudson CI server commented on MAGNOLIA-2809:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#983|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/983/]
> Update task incorrectly moves 'templatePath' nodes of templates to parameters
> subnode
> -------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2809
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
> Project: Magnolia
> Issue Type: Bug
> Components: templating, updatemechanism
> Affects Versions: 4.0
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Priority: Blocker
> Fix For: 4.1.1, 4.0.3
>
>
> There are 2 conflicting tasks for templates:
> # renamed {{path}} to {{templatePath}} - that is 100% correct
> # 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
