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
ZeeshanKhan
March 5, 2020
Solved

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

  • March 5, 2020
  • 1 reply
  • 1779 views

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.
Best answer by aem65user

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

A
aem65userAccepted solution
Level 2
April 26, 2020

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.

    Terms & ConditionsAccessibility statement

    Loading footer...