[MAGNOLIA-3850] @cms.setNode wraps calendars as strings. Created: 05/Oct/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | freemarker, taglibs |
| Affects Version/s: | 4.4.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Danilo Ghirardelli | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 |
|
Using the setNode tag in a freemarker page, nodeDatas of type (jackrabbit) Date are incorrectly exposed as strings and not as freemarker date.
Freemarker will say that a date element was expect in the second case, but a string was provided. On further inspection you will find that the calendar is stored in the map as an iso string. As a workaround you can re-parse that string and get back a calendar, but having the original calendar would be much better. The problem seems connected to the excessive wrapping (freemarker ones and the other provided by the setNode tag), but I wasn't able to find where exactly the problem arises. |
| Comments |
| Comment by Danilo Ghirardelli [ 05/Oct/11 ] |
|
I don't know if this issue belongs here to the generic "freemarker" or is more a part of stk, you can move it if it's in the wrong place. |
| Comment by Danilo Ghirardelli [ 10/Oct/11 ] |
|
Also Longs are "mapped" as strings, so you can't use them as numbers once the content is wrapped by setNode. |
| 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. |