Enhance carousel component to support list component | Community
Skip to main content
S
SalmaSh3
Level 1
July 28, 2026
Question

Enhance carousel component to support list component

  • July 28, 2026
  • 1 reply
  • 34 views

Hi,

I have a carousel component under that authored the list component. My requirement is when I author list component each item in list has to be considered as individual item in carousel. So, from BE I am resolving the list items and rendering it on html. But after changing the HTL I am not able to see the list component under the carousel in editor and also authoring features are not working. Can anyone please tell me the reason why it is not working?

 

1 reply

Raja_Reddy
Community Advisor
Raja_ReddyCommunity Advisor
Community Advisor
July 30, 2026

Hi ​@SalmaSh3 

Let Carousel treat the List's referenced items as real per-item resources.
Instead of resolving XF paths in Java and pushing raw paths into HTL, structure it so each List item is included via data-sly-resource pointing to its actual XF/component path without forcing wcmmode:

html

<li data-sly-repeat.listItem="${listModel.items}" class="splide__slide">
    <sly data-sly-resource="${listItem.path @ resourceType='core/wcm/components/experiencefragment/v2/experiencefragment'}"></sly>
</li>

Remove wcmmode='disabled' entirely — let it inherit the current page's mode, so the Editor can attach normally. You'll need to accept that if this causes a double-toolbar visual glitch with nested XF components, that's a separate, smaller CSS/config problem to solve (often handled by hiding the inner component's own toolbar via cq-placeholder config, not by disabling wcmmode entirely).

Can you share the Sling Model method for listResolvedXfItems so I can confirm whether the paths it returns are real, addressable JCR resources or synthetic in-memory objects?

Terms & ConditionsAccessibility statement

Loading footer...