[MGNLRSSAGG-149] Feed subscriptions component does not work Created: 04/Feb/14 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia RSS Aggregator Module |
| Component/s: | None |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.2.x |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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 |
|
The template feedSubscriptions.ftl retrieves the author list using the method getItems available on the model FeedSubscriptionsModel. This method returns a Colloection<Node> which does not expose the "getters" used in the template such as getAuthor. Thus, on line 22, the following statement throws an exception.
[#list authorsList?sort_by('author') as entry]
The fix consists in converting the Collection<Node> into a Colllection<ContentMap> using cmsfn.asContentMapList: <link rel="stylesheet" href="${ctx.contextPath}/.resources/planet.css" type="text/css"/> [#-------------- INCLUDE AND ASSIGN PART --------------] [#-- Assigns: Definition parameters --] [#assign authorsList = cmsfn.asContentMapList(model.items![])] [#assign linkAuthor = content.linkAuthor!false] [#assign maxResults = content.maxResults!5] |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |