Unable to edit components in AEM 6.3 Classic UI | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Techaspect_Solu
Techaspect_SoluAccepted solution
Level 7
Nov 22, 2017 9:08 AM UTC

Hi Paresh,

We were successfully able to edit the component in classic UI in AEM 6.3. The possible reason behind your issue is, you might not define dialog for classic UI. Please do try defining classic UI dialog and then try editing your component in classic UI. You should be able to edit your component.

cq:dialog - dialog for the touch-optimized UI

dialog - dialog for the classic UI

NOTE: A dialog defined for the classic UI will operate on the touch-optimized UI.

On the other hand, a dialog defined for the touch-optimized UI will not operate on the classic UI.

Depending on your instance and author environment you might want to define both types of dialog for your component.

We hope this information helps!

Regards,

TechAspect Solutions

4 replies

kautuk_sahni
Employee
Nov 22, 2017 9:13 AM UTC

Adding to Techaspect

This is AsDesigned behavior because WeRetail isn't supported on Classic UI by design.

You will be unable to edit WeRetail site whereas sites made from the static template are editable as mentioned by Techaspect that WeRetail  do not define dialog for classic UI.  A dialog defined for the classic UI will operate on the touch-optimized UI wheras a dialog defined for the touch-optimized UI will not operate on the classic UI.

Translate
Kautuk Sahni
Techaspect_Solu
Techaspect_SoluAccepted solution
Level 7
Nov 22, 2017 9:08 AM UTC

Hi Paresh,

We were successfully able to edit the component in classic UI in AEM 6.3. The possible reason behind your issue is, you might not define dialog for classic UI. Please do try defining classic UI dialog and then try editing your component in classic UI. You should be able to edit your component.

cq:dialog - dialog for the touch-optimized UI

dialog - dialog for the classic UI

NOTE: A dialog defined for the classic UI will operate on the touch-optimized UI.

On the other hand, a dialog defined for the touch-optimized UI will not operate on the classic UI.

Depending on your instance and author environment you might want to define both types of dialog for your component.

We hope this information helps!

Regards,

TechAspect Solutions

Translate
kautuk_sahni
Employee
Nov 22, 2017 8:44 AM UTC

I can reproduce the behavior mentioned here. I have further asked the internal team to get back to me on this.

Translate
Kautuk Sahni
kautuk_sahni
Employee
Nov 22, 2017 8:23 AM UTC
Kautuk Sahni