Hi,
I have created one custom component it has a feature drag an image from content finder and drop it in custom component.It works well without using cq:dropTargets node,cq:inplaceEditing and all those edit behaviour stuff's.
For adding the listeners node , cq:editConfig node is necessary . Coz listeners node comes under editConfig.
Is these nodes (inplaceEditConfig,dropTargets) are necessary for editing,drag and drop functionalities without these i able to drag drop and editing the content??
Thanks in advance
Solved! Go to Solution.
According to the AEM docuemntation - these define the drop target:
https://dev.day.com/docs/en/cq/current/developing/components.html#Configuring the Edit Behaviour of a Component
You should not be able to drag and drop and image without defining a cq:dropTargets node.
Views
Replies
Total Likes
According to the AEM docuemntation - these define the drop target:
https://dev.day.com/docs/en/cq/current/developing/components.html#Configuring the Edit Behaviour of a Component
You should not be able to drag and drop and image without defining a cq:dropTargets node.
Views
Replies
Total Likes
In my case it works as excepted without using drop target (CQ 5.4).
Don't know how its working ?
One important point we need to notice here is I have removed the editConfig and dropTargets node from existing "image" component in /libs/foundation/components/image.Then i dragged the image component from side kick to my web page and dialog got opened by double clicking the component.
I able to drag an image from content finder to the modified image component which i placed earlier in my web page.
So we can conclude that dropTarget is not necessary for dropping an image from content finder to component in this case the question will raise "what is the purpose of using this(dropTarget)" .
Correct me if I am wrong.
I hope my reply is clear.
Views
Replies
Total Likes
This link does not work!
Here is the link from 6.3 helpx- https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/components-basics.html
That is because this thread is 3 years old and doc team moved doc URLS.