How to make parsys containers available in content fragment component embedded using data-sly-resource | Community
Skip to main content
mpalme1
Level 3
June 25, 2020
Solved

How to make parsys containers available in content fragment component embedded using data-sly-resource

  • June 25, 2020
  • 4 replies
  • 3604 views

I have a component with htl that wraps a couple of components including a content fragment component like this:

 

<sly data-sly-resource="${'./contentfragment' @ resourceType='mysite/components/content/contentfragment'}"/>

 

 

And that works except that, in the page editor, the "in between" parsys containers of that resourced content fragment component are visible but components can't be added from the component drawer. If I drag them onto the page over the parsys, they don't drop.

 

 

 

 

Is there a way to make it so they can be?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Are you using core components? In that case I would ask on the Core Components github page.

4 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
June 27, 2020

Are you using core components? In that case I would ask on the Core Components github page.

arunpatidar
Community Advisor
Community Advisor
June 27, 2020

I don't think so you can author content fragment's content in the page editor. You can configure and browse content fragment which is created using content fragment model. Are you not able to configure content fragment when you include from HTL or the page parsys is become inedible because of CF?

 

Arun Patidar
mpalme1
mpalme1Author
Level 3
June 29, 2020
Well, I am authoring the content fragment in my assets library using the content fragment model as you said. In this case, I am trying to use the Content Fragment Component (this one: https://docs.adobe.com/content/help/en/experience-manager-core-components/using/components/content-fragment-component.html) to render the content of the Content Fragment. That component will include those "in between" parsys drop zones as described here: https://docs.adobe.com/content/help/en/experience-manager-64/developing/components/components-content-fragments.html#in-between-content. What I am trying to do works if the content fragment component is added to the page manually or via a workflow. However, if I add it using the data-sly-resource syntax above, the included "in-between" drop zones are visible but disabled.
kautuk_sahni
Community Manager
Community Manager
June 29, 2020
@mpalme1 Any update on this thread?
Kautuk Sahni
mpalme1
mpalme1Author
Level 3
June 29, 2020
@kautuk_sahni, i still have not found a solution