AEM 6.4 sp2 cq:actions doesn't work with editannotatecopymovedeleteinsert

Avatar

Avatar

henriquer230337

Avatar

henriquer230337

henriquer230337

07-11-2018

We installed sp2 in our 6.4 instance,

and some issues were found.

When using cq:actions editannotatecopymovedeleteinsert, the edit toolbar options aren't clickable like it was on aem 6.4.

Example (classic ui view)

Screenshot from 2018-11-07 16-27-50.png

The options in uppercase doesn't work

Separating by comma using:

editannotate,copymove,delete,insert

The edit and annotate stays as in the print above while the rest works ok.

Anyone also had the same issue? Or has some suggestion?

We don't have the intention of migrating to touch ui as of now.

Thanks

Replies

Highlighted

Avatar

Avatar

mickjleroy

Avatar

mickjleroy

mickjleroy

21-01-2019

I've also found that in 6.4 SP2 Classic UI, the "Drag components here..." area is missing. This is due to the "null" value in the "actions" array rendered by the WCMComponentFilter. Executing the same code without the "null" value renders the drag'n'drop area.

CQ.WCM.edit({"path":"/content/helloworld/jcr:content/par/*","type":"wcm/foundation/components/parsys/newpar","csp":"base-page|page|basicpage/par|parsys/newpar","editConfig":{"actions":[null,"CQ.wcm.EditBase.INSERT"],"disableTargeting":true}});

This is NOT reproducible in 6.2 without SP2 installed.

UPDATE:

After investigating this issue a little more, I managed to track it down to "/libs/wcm/foundation/components/parsys/newpar/cq:editConfig". This node contains an unexpected "cq:actions" value of "_clear", which the ComponentEditConfigImpl class doesn't know how to render.

newpar-editconfig-6.4-sp2.png

Removing this value fixes the issue.

Highlighted

Avatar

Avatar

Reto_Zigerlig

Avatar

Reto_Zigerlig

Reto_Zigerlig

30-01-2019

We had exactly the same issue with AEM 6.4 SP3. Fixed it with an overlay of the described node under /libs/wcm/foundation/components/parsys/newpar/cq:editConfig.

Highlighted

Avatar

Avatar

Parusharam

Avatar

Parusharam

Parusharam

07-02-2019

We are also facing the same issue. Raised a day care ticket with adobe. But I can suggest some workaround.

In the edit config node, update edit instead of editannotate in the cq :actions. it will work.