AEM 6.1 Touch UI and cq:actions with 'editannotate' does not work | Community
Skip to main content
October 16, 2015
Solved

AEM 6.1 Touch UI and cq:actions with 'editannotate' does not work

  • October 16, 2015
  • 11 replies
  • 4904 views

I have AEM 6.1 and wanna find out, how it works with our custom components. I figured out that in Touch UI the 'Configure' button for components does not appear, if I have cq:actions in Edit Config with entry 'editannotate'. So I'm not able to edit the component. Is this a bug? Or not allowed?

We use cq:actions to have a text with the component name in the context menu (for Classic UI)  and we also want to enable annotations. Is there a solution to have both?

 

Thanks!
Anne

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

You need to have a resourceType to support the TouchUI

refer [1] to see how to create touch UI component

[1] https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html

11 replies

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
October 16, 2015

You need to have a resourceType to support the TouchUI

refer [1] to see how to create touch UI component

[1] https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html

October 16, 2015

I'm not sure if this answers my question. The component works in Touch UI, also the component's dialog, the only problem is, when I add cq:actions to Edit Config and use editannotate, the Configure button is not shown anymore. It also happens, if I take a plain AEM 6.1, seach for a libs/foundation component with cq:actions defined and add editannotate instead of edit (e.g. the forms/start component). So a missing resourceType isn't the problem I think.

smacdonald2008
Level 10
October 16, 2015

Sounds like you discovered a bug - please log a ticket.

Adobe Employee
October 16, 2015

anne-kathring54369943 wrote...

I'm not sure if this answers my question. The component works in Touch UI, also the component's dialog, the only problem is, when I add cq:actions to Edit Config and use editannotate, the Configure button is not shown anymore. It also happens, if I take a plain AEM 6.1, seach for a libs/foundation component with cq:actions defined and add editannotate instead of edit (e.g. the forms/start component). So a missing resourceType isn't the problem I think.

 

Hi Anne,

I just tried this in a AEM6.0 and 6.1 instance and it worked in the 6.0 instance. So does seem like bug.

The way it should work is that the annotate part of "editannotate" is ignored as there is now an overlay which is used for doing annotations[1]. So if you change editannotate to edit it will allow you to edit and annotate in the touch ui, which probably doesn't help you in classic ui if you are using only cq:actions "edit".

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/author/page-authoring/annotations.html

October 16, 2015

Hm, if I use editannotate, also in Touch UI I can not annotate the component.

EDIT: Sorry, I meant "If I use edit, ...."

OK, thanks for your answers, I will log a ticket to Adobe.

Adobe Employee
October 16, 2015

Hi Anne,

did you review the section on "Annotating a Component - Touch-optimized UI" in [1]. Are you not able to annotate the component using the method described?

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/author/page-authoring/annotations.html

October 16, 2015

Yes, I followed the instructions. I tested with /libs/foundation/components/form/text.

No cq:actions: editing and annotation is possible

cq:actions with edit: editing possible, annotation not

cq:actions with editannotate: no editing possible, no annotation possible

Level 2
December 21, 2015

Is this problem solved? I am also facing the same issue.

December 22, 2015

Adobe has reported this bug to development, with request number CQ-52808. But I don't know when this fix is included in a hotfix or service pack, I could not find it here: https://helpx.adobe.com/experience-manager/kb/aem61-available-hotfixes.html
Due to other difficulties with Touch UI we do not use it right now and therefore have no information about this bug.

Level 3
December 24, 2015

are they going to provide a hotfix for this or going to rollout along with 6.2 release ?