After publish the Experience Fragment It is fine in publish but getting extra container div in the target after export to target | Community
Skip to main content
ZeeshanKhan
New Participant
Mar 5, 2020 9:22 AM UTC
Solved

After publish the Experience Fragment It is fine in publish but getting extra container div in the target after export to target

After Create the XF from dynamic template and create the variation of the experience fragment.The Component is fine there is no container class in the publish view but when I export to target in the target i am getting extra container class above the component html structure that create the UI of the component distorted.Can anyone have an idea about why it is coming in the target.

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
aem65userAccepted solution
Level 2
Apr 26, 2020 12:36 PM UTC

The experience fragment transformer is using the script /libs/cq/experience-fragments/components/xfpage/body.nocloudconfigs.html while exporting to target. You can remove the container class there by overlaying in your custom template.

1 reply

aem65userAccepted solution
Level 2
Apr 26, 2020 12:36 PM UTC

The experience fragment transformer is using the script /libs/cq/experience-fragments/components/xfpage/body.nocloudconfigs.html while exporting to target. You can remove the container class there by overlaying in your custom template.

Translate