[DOCU-2401] Include changes in ContentMapModel that affect ?children built-in Created: 21/Feb/22 Updated: 12/Apr/22 Resolved: 12/Apr/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Ashraf Khamis |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Due to changes applied in MAGNOLIA-7156, ?children built-in changed from returning List<Node> to List<ContentMap> in Magnolia 6.2, which leads to errors in some cases where users had a specific conversion of the retrieved items to ContentMap from earlier versions. As suggested by customer in SUPPORT-14311, it would be really helpful if this change was properly documented so, they request adding a note about it in our docs (might be in upgrading to 6.2 section) |
| Comments |
| Comment by Ashraf Khamis [ 12/Apr/22 ] |
|
Created a FreeMarker built-in ?children in ContentMapModel section under https://docs.magnolia-cms.com/product-docs/6.2/Upgrading-to-Magnolia.html#_things_to_consider. Reviewed by Jonathan. |