This conversation has been locked due to inactivity. Please create a new post.
This conversation has been locked due to inactivity. Please create a new post.
Views
Replies
Total Likes
You can try this to import experience fragment without the <body> and HTML tags,
<sly data-sly-resource="${@path='/content/experience-fragments/my-site/fragment-a/master, selectors='content'}"></sly>
For the CSS and JavaScript, in the XF editable template, page policies where you have configured the client libraries to be used, you should take those and again, refer them in the editable template page where your XF is being served.
I tried .content as well. But see adding the portion of source code below.
<link rel="stylesheet" href="/libs/cq/experience-fragments/components/xfpage/content.min.css" type="text/css"> |
It is not fully qualified path. In the consumer-side if this code include, may be virtually it won't load the page properly.
I need path like "https:localhost:4502/content/----/---/footer.js
You can try this to import experience fragment without the <body> and HTML tags,
<sly data-sly-resource="${@path='/content/experience-fragments/my-site/fragment-a/master, selectors='content'}"></sly>
For the CSS and JavaScript, in the XF editable template, page policies where you have configured the client libraries to be used, you should take those and again, refer them in the editable template page where your XF is being served.
Views
Likes
Replies
Views
Likes
Replies