Access to dynamic Reusable part. #4192
Conversation
| { | ||
| var shapeType = context.DisplayType != "Detail" ? "ContentPart_" + context.DisplayType : "ContentPart"; | ||
|
|
||
| var shapeResult = new ShapeResult(shapeType, ctx => ctx.ShapeFactory.CreateAsync(shapeType, () => Task.FromResult<IShape>(new ZoneHolding(() => ctx.ShapeFactory.CreateAsync("Zone", Arguments.Empty))))); | ||
| shapeResult.Differentiator(contentTypePartDefinition.PartDefinition.Name); | ||
| shapeResult.Differentiator(partName); | ||
| shapeResult.Location("Content"); | ||
|
|
There was a problem hiding this comment.
There was a problem hiding this comment.
Do you mean we should do a shapeResult.Location("DetailsAdmin", "-"); too here?
There was a problem hiding this comment.
I think that's ok here, a dynamic part is composed of fields, so the rendering depends on the field drivers where most of them are not rendered in SummaryAdmin.
E.g if a blog post has a dyn part, when displaying the blog in DetailAdmin, the related list part will be rendered in DetailAdmin but each blogpost will be rendered in SummaryAdmin.
The "problem" is when the blog itself has an additional field / part (dynamic or not), it will be rendered when displaying the blog in DetailAdmin. But i think that there is nothing to do here, this seems to be only due to the field drivers.
Most of the field drivers already do
.Location("SummaryAdmin", "")
Maybe we could add
.Location("DetailAdmin", "")
Fixes #4161, so that you can use
Model.Content.Named("Reusable1").It was working if the reusable part is created by code but not if created through the admin.
When created by code the differentiator is set to
partNameor{partName}-{shapeType}but when created dynamically it waspartTypeName(here the shapeType beingContentPart).So here, for a dynamic part i set the differentiator to
partName.Then i added some alternates, e.g based on the
contentType=>Article-Reusable1.