After publish the Experience Fragment It is fine in publish but getting extra container div in the target after export to target | Adobe Higher Education
Skip to main content
ZeeshanKhan
March 5, 2020
Répondu

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

Ce sujet a été fermé aux réponses.
Meilleure réponse par 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 commentaire

aem65userRéponse
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.