Incorrect Sidekick's behaviour

Avatar

Avatar
Level 1
ashutoshrastogi
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
ashutoshrastogi
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile
ashutoshrastogi
Level 1

22-06-2020

Hi,

If I am trying to edit a page (which already has Content Fragment "Based on Touch UI" ) in classic UI, then drag & drop "classic UI based" components from sidekick. then sidekick's behaviour is not proper.

FYI, while drag-drop sidekick splits in two parts (not behaving properly). Please see the below screenshot.

Screenshot-1.png
Any suggestions please ?
OR
We should not use classicUI based components on same page where touchUI based components are existing.

Any more updates on this please ??

Thanks in advance !!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile
ArpitVarshney
MVP

22-06-2020

Hi @ashutoshrastogi 

I would say you should drag/drop/edit the classic UI component in classic UI mode and touch UI component in touch UI mode.

Also, Adobe has already recommended everyone to move from classic to touch UI mode so I would suggest you move your components from classic to touch gradually but at least you can convert these dialogs from classic to touch which are pretty easy using dialog converter tool.

 

Regards,

Arpit

Answers (2)

Answers (2)

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

22-06-2020

Hi Ashutosh,

AEM provides a backward-compatible mechanism for the classic UI dialogs to co-exist with the new Touch UI interface.If we are in the new Touch UI user interface and we haven’t defined the new “cq:dialog” in the jcr, it’s possible to render the classic “dialog”.

 

Since Content fragments are not available in the classic UI, and so the given behavior. 

Capture.JPG

 

 

Thanks,

Vaishali

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

22-06-2020

I would recommend not to mix up Classic UI and Touch UI components. If you have some components which doesn't have a Touch UI dialog, just create the same and start authoring those also in Touch UI mode. It would be the best approach I would say.