[MGNLMIGRATION-149] All ftl templates: Fix access to assets Created: 29/Oct/12  Updated: 01/Oct/13  Resolved: 06/Sep/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.1.4
Fix Version/s: 1.2.6, 2.0

Type: Improvement Priority: Neutral
Reporter: wolf bubenik Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: ToDo_for_1_2_1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLSTK-1028 Implement stkfn.getAsset(contentMap, ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

The ftl code generated by current version of migration scripts does not work:

[#assign [#--OLD image = stk.getAsset(content, "image", "ANY")! --] image = stkfn.getAsset(content, "image", "ANY")!]

I see two issues here:

  1. 'content' is a ContentMap, not a 'Node'
  2. the standard variation "ANY" does not exist any more

Thus a replacement like

[#assign image = stkfn.getAsset(model.node, "image")!]

should be used.



 Comments   
Comment by Philipp Bärfuss [ 08/Nov/12 ]

I think we should fix that in the STK functions which should also accept ContentMap.

Please create such a ticket.

Comment by Cesar Desales [ 14/Nov/12 ]

Philipp,

Just to clarify, what's the action required to tackle this ticket?

a) Open an STK ticket?

b) Perform the change in the Migration Tool?

Comment by Cesar Desales [ 04/Dec/12 ]

This issue is to be solved by implementing the required changes in STK: MGNLSTK-1028

Comment by Eric Hechinger [ 07/Dec/12 ]

Ticket moved to 1.2.x. Must be solved in the next release.

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