[MAGNOLIA-3155] Make nodeDataTemplate property work also for other controlTypes Created: 20/Aug/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: gui, templating
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Giancarlo Berner Assignee: Magnolia International
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:

 Description   

For a dialog property of controlType = file (Type = Binary), setting the 'nodeDataTemplate' value will work fine.
However, when I use a different controlType, e.g. uuidLink, the nodeDataTemplate setting as no meaning anymore.

Please add the 'nodeDataTemplate' feature to other controlTypes, especially uuidLink and Link. The reason is that in most projects the authors select images from the DMS rather than from disk. We need to have a possibility to render images through a 'nodeDataTemplate' for DMS fetched images.

Thanks!



 Comments   
Comment by Giancarlo Berner [ 14/Dec/07 ]

Sorry to have to upgrade to a major bug, but in 90% of our projects the requirement is to upload images from the DMS rather than disk. And since the beauty of the DMS is to have one image and resize/scale to whatever requirements asked for, we need the "nodeDataTemplate" property not only in the "file" control, but also at least in the "uuidLink" control.

The workaround is to have selectors and use Subtemplates, but it is not very flexible (e.g. different images with different image processing scripts on the same page).

Thanks!

Comment by Magnolia International [ 19/Mar/10 ]

Is this still needed and relevant with 4.x ?

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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