I guess the solution given in above blog works fine for single field. What are the changes required for multi-field. Any idea?

Hi All, We have just migrated from classic UI to touch UI and we are currently using a datepicker field. The problem we are facing right now is that, our classic UI dialog have stored the value for date in YYYY/MM/DD format and we are trying to save in same format in touch UI using granite/ui/compon...

Hi All, After migrating to touch UI, we observed that few pages are getting infinite height added.This seems to be popular issue while migrating from classic UI to touch UI. It is I guess due to our CSS files have height defined for few elements in vh, position absolute +  height 100% which really d...

Hi All, In classic UI implementation we have below JS code which is including a config dialog on a page. <script type="text/javascript" id="cq-gen73"> CQ.WCM .edit({ "path" : "<content_path>", "dialog" : "<dialog_path>",...

Make use of : aem-AuthorLayer-Edit

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.

I am using AEM 6.4

Hi All, We have few mark up defined in our CSS library as below in CQ edit mode :   .cq-wcm-edit .formBuilder .section.hiddenField, .cq-wcm-edit .formBuilder .section.hiddenFieldMulti { display: block; }  I assume that .cq-wcm-edit only works with AEM classic UI. Any help on how we can migrate t...

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