Hi Peter,It works in fullscreen mode but not in the normal dialog mode.In Normal Dialog mode, We are unable to click on OK once we enter the columns & rows.

We added enabled the table plug-in in rich text editor. However, When we click on the table option in the dialog view the table popup opens and when we scroll down. Dialog starts flickering. Table plug-in works fine in full screen mode. this happens with the Core text component also.

We are currently authoring the Paths for the navigation component and the same in included in the editable template structure.For /US/EN we are good as we have the links that we need to configure.For /CA/FR, We need to have an additional link in the navigation.Now that we have the component dialog i...

I have gone through the video but doesn't talk about the editable templates challenge for multilingual sites. As explained above, When we have header and footer as part of structure. We will not be able to edit the values in the component dialog in the editable template structure as the same would b...

I have created map.publish as below for we retail on a vanilla instance.URL's are shortened. But when i try to load the page. everything loads except the resources rendered from etc.clientlibs. I added internal redirect to /etc.clientlibs too. But all the css/js gives a 404. Do we have any solution ...

Thanks Arun..We are using tagfield only but we are unable to restrict that to display 1 level. It displays Child tags also. Seems using the auto complete also we are unable to get the single level tags in the Dropdown.

Do we have ability in OOTB coral Tag field to display only 1 level of tags instead of their children or do we have a tags dropdown available ??

If you have fixed list of the tabs in the component. May be you can try adding a cq:template node in the component with a number of nodes having sling:resourcetype property to the experience fragment component. This way the experience fragment node is created when you drag-drop your custom component...

Thanks Pranav for the reply..It helpsI have follow-up question on this topic. Now we have included the cloudservice related script. It is also including the mbox.js with in AEM and calling it based on the clientcode that we provide. We see a difference in the mbox.js file that is in  this location /...

We are integrating with Adobe target with AEM 6.3. We are using the Experience fragments approach to personalize the content. However, We already have an mbox included in the template. When we add Target cloud service in AEM and load the page. mbox.js is throwing errors. I have read in one of the do...