Timeline for How to apply rendering to child items
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2019 at 18:52 | vote | accept | Rolan Christofferson | ||
| Nov 19, 2019 at 18:09 | comment | added | Rolan Christofferson | I agree. Simpler objects that don't need a whole rendering. Very new at this stuff. | |
| Nov 19, 2019 at 17:24 | comment | added | Richard Seal♦ | There are many reasons to use a multilist. Just not the use case you have I think. | |
| Nov 19, 2019 at 17:10 | comment | added | Rolan Christofferson | @RichardSeal If i remove the multilist, then what is the point of a multilist? I wanted the Menu item to know what sections it has, so maybe it could be used somewhere else, with its sections intact. | |
| Nov 19, 2019 at 16:53 | answer | added | Mark Lowe | timeline score: 1 | |
| Nov 19, 2019 at 16:35 | comment | added | Yogesh Sharma | If I understand correctly you want to add rendering to section item programmatically? Can you provide more detail here what you want achieve by doing this? may be someone can suggest more easy way to handle your requirement... any screenshot also if you have? | |
| Nov 19, 2019 at 16:31 | comment | added | Richard Seal♦ |
Change your architecture, remove the multilist, add a placeholder where you want the sections to go, create a Section component and allow the content editor to add them in via the Experience Editor.
|
|
| Nov 19, 2019 at 15:35 | history | asked | Rolan Christofferson | CC BY-SA 4.0 |