Timeline for Glass BeginEditFrame to edit children of a referenced DropLink field
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2017 at 13:51 | comment | added | Teeknow | @jammykam correct that does allow editing the current item but they need the parent item if they want to add items that will be siblings to those items | |
| Aug 24, 2017 at 18:41 | comment | added | jammykam |
You can have Glass target the children, if for example you render the Children in a foreach loop then you can BeginEditFrame(child, "Title", c => c.SpudField) as long as the Spud model has a [SitecoreId] set. This works for Edits, not sure about Inserts off top of my head... Looks like @Teeknow method would work though
|
|
| Aug 24, 2017 at 14:31 | comment | added | Teeknow |
You're not wrong with how it is set up. The rendering will use the current context item to determine what to target. This means if you populate the rendering's data source with the item potato then it should target the item you would expect. Otherwise you are stuck using an edit frame and passing it the id or path of the item you want to target.
|
|
| Aug 24, 2017 at 14:15 | comment | added | Richard Hauer | An interesting idea. Will investigate this further. I've since found out that the frame that comes up seems to target the DropLink field rather than its children, which makes sense I suppose, but isn't what we want. I'm a little surprised custom code is needed for this; seems like something most people would want to do at some point. We use this pattern all the time. | |
| Aug 24, 2017 at 13:48 | history | answered | Teeknow | CC BY-SA 3.0 |