Experience Fragment Implementation Issue | Community

Level 4

Solved

Experience Fragment Implementation Issue

Forum|Forum|3 years ago
July 24, 2022
3 replies
855 views

Actually, after adding the experience fragment in a component, I am unable to open the touch ui dialog of the same component. What could be the issue? If I remove the experience fragment path through crxde then I am able to open the touch ui dialog.

Please help me to solve that issue!

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 Shiv_Prakash_Patel

Hi @ameen_dev ,

Are you including Experience Fragment directly in the component through sightly? If yes, please refer to this - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-i-can-include-xf-directly-not-through-parsys-in-aem/m-p/459589

Also, check the console for any issue related to this?

If still any issue, please elaborate on where are you removing the experience fragment in CRX/DE?

Hope this could help you !!!

Regards

Shiv

Shiv_Prakash_Patel

Community Advisor

Accepted solution

Community Advisor

Hi @ameen_dev ,

Are you including Experience Fragment directly in the component through sightly? If yes, please refer to this - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-i-can-include-xf-directly-not-through-parsys-in-aem/m-p/459589

Also, check the console for any issue related to this?

If still any issue, please elaborate on where are you removing the experience fragment in CRX/DE?

Hope this could help you !!!

Regards

Shiv

Shiv Prakash

Community Advisor

Community Advisor

Hi,

Check if you have proper element nesting i.e. opening and closing tab.

It happens when you miss or extra div in the HTL or XP component.

Arun Patidar

Adobe Employee

Couple of things you should do:

1. Check with some other experience fragment whether you are getting same issue or not.

2. Always, refer logs for any issues and if you don't find any relevant information in logs then enable the debug logs and then analyze.

I will hope, one of these step will help you to find the root cause.