Hi Nupur_Jain Thank you so much. It worked. Will you be able to look at : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dialog-not-appearing-in-touch-ui/qaq-p/376726 as well. I guess that also requires similar solution.
As I can see that they are trying to hide some components being shown on page except edit mode. I understand that this is not a correct implementation but we are reluctant to modify the component. We are looking for a CSS solution to tackle this.
Hi @Nikhil-Kumar No error. We are not able to see the edit option in touch UI mode. I suspect because the code written in JSP is specific to classic UI
Hi @Nikhil-Kumar, Sorry I guess I have not provided complete details in question. I have that script written in my template JSP file. Component dialog is already migrated to touch UI but on page I am not able to see the option to edit.
Yes correct.Let me explain how we are doing it for normal AEM pages.We have base site under en local. We then use MSM to rollout the site to other locals. We then provide the rolled out local pages to clay-tablet for translation. We would like to achieve the same for content fragments if it is possi...
Hi Hamid,My issue is not with getting content fragment translated. It is working fine with me.My concern is how to rollout the content fragments like we rollout the content pages.