You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It successfully creates the tab and puts the "Add My Type" to the "My Tab", but it leaves the "Items Provides a collection behavior for your content item where you can place other content items." text on the "Content" tab.
I see that this text is generic and implemented in the ContentPart.Edit.cshtml but I have no idea on how to address this shape from the placement, nothing seem to target it.
Orchard Core version
2.0.2
To Reproduce
Create two content types: Inner (doesn't matter what parts), Outer (add a named BagPart containing Inner content items, the name should be Items)
Go to Design > Placements and create a Placement with shape type BagPart_Edit and the rule should be
I recall this! For namedpart don't use BagPart_Edit in placement, it will only move the Part and not the label. To move both label and the Part use ContentPart_Edit in placement with differentiator.
It seems that this issue didn't really move for quite a while despite us asking the author for further feedback. Is this something you'd like to revisit any time soon or should we close? Please reply.
Describe the bug
I have a content type with a named BagPart. I want to put the BagPart editor to a separate tab. I can do it with the following placement:
It successfully creates the tab and puts the "Add My Type" to the "My Tab", but it leaves the "Items Provides a collection behavior for your content item where you can place other content items." text on the "Content" tab.
I see that this text is generic and implemented in the
ContentPart.Edit.cshtml
but I have no idea on how to address this shape from the placement, nothing seem to target it.Orchard Core version
2.0.2
To Reproduce
BagPart_Edit
and the rule should beExpected behavior
Somehow move the generic text to the "My Tab" tab.
Logs and screenshots
The text was updated successfully, but these errors were encountered: