Solved

How to use Experience Fragment in externals sites

Forum|Forum|3 years ago
June 29, 2022
3 replies
3141 views

Hi Community,

I need to use experience fragments in external sites such as Facebook. If you can provide some tutorials, that would be helpful. As mentioned in some tutorials, "Experience Fragments HTML rendering output processor" is not present in configMgr. Your response would be greatly appreciated.

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 DEBAL_DAS

1. Earlier after creating the experience fragments I just exposed those experience fragments as plain HTML from AEM.

Using the .plain. selector in the URL, you can access the plain HTML rendition as defined here -

Please refer this: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/experience-fragments.html?lang=en

2. Another application was making pull request to read the our experience fragments from AEM as html and get it displayed on their application.

3. We made necessary change at dispatcher level to allow experience fragments for that external application.

4. While accessing experience fragments from AEM we had encountered CORS issue and then we allowed that external application domain to prevent CORS issue.

arunpatidar

Community Advisor

Hi,

Please check this https://experienceleague.adobe.com/docs/experience-manager-learn/sites/experience-fragments/experience-fragments-feature-video-use.html?lang=en

Arun Patidar

V

VenkateshKA1Author

Hi Arun,

I have created Facebook configuration like below and when I give connect I am getting "Sorry, something went wrong." error.

When I give connect, I am getting below error.

In Facebook developer's Page, I created consumer account and added Facebook Login. It is still in development mode. Please let me know if I missed anything in this process. Added below screenshot for reference

arunpatidar

Community Advisor

Hi,

Not sure what could be the issue, just one thing I noticed that you are trying using localhost and without https, this could be an issue but it is just a pure guess.

Arun Patidar

DEBAL_DASAccepted solution

New Member

1. Earlier after creating the experience fragments I just exposed those experience fragments as plain HTML from AEM.

Using the .plain. selector in the URL, you can access the plain HTML rendition as defined here -

Please refer this: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/experience-fragments.html?lang=en

2. Another application was making pull request to read the our experience fragments from AEM as html and get it displayed on their application.

3. We made necessary change at dispatcher level to allow experience fragments for that external application.

4. While accessing experience fragments from AEM we had encountered CORS issue and then we allowed that external application domain to prevent CORS issue.

Debal Das, Senior AEM Consultant

J

johnnyf0202

Hello @debal_das, how were you rendering the experience fragments? Were you using <iframe>? Is it necessary having the plain selector in the URL to access the HTML?