Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

How to Disable Targeting?

Avatar

Level 2

Hi,

After clicking "start targeting" and deleting all but the default experience, I hover over the targeted component and a 'disable targeting" link is shown (see screenshot).  When clicking, however, I get the error "cannot disable targeting due to an unexpected error".  Am I doing this wrong.  Is there a workaround that I can use to restore the component back to it's non-targeted state?  Thanks for your help.

1 Accepted Solution

Avatar

Correct answer by
Administrator

Hi 

 

To Do this Globally :-

//

    The only way to do this without modifying some javascript code (always a bad idea!) is to overlay the parsys component and on the cq:editConfig set cq:disableTargeting to true.

    You'll need to modify the following nodes:

    foundation/components/parsys/colctrl/cq:editConfig
    foundation/components/parsys/cq:childEditConfig
    foundation/components/parsys/cq:editConfig
    foundation/components/parsys/new/cq:editConfig

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

 

 

You can disable at component level by setting cq:editConfig/cq:disableTargeting to true.

Reference Link:- https://forums.adobe.com/thread/1212664

 

 

To disable "target" option when edit the component you need to add property cq:disableTargeting="true" to cq:editConfig Node

//             cq:actions="[text:Button,-,edit,delete]"
               cq:dialogMode="floating"
               cq:disableTargeting="true"
               jcr:primaryType="cq:EditConfig"

Reference Link:- http://aemquickstart.blogspot.in/2015/11/how-to-disbale-target-option-on.html

 

I hope this will help you.

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

View solution in original post

4 Replies

Avatar

Correct answer by
Administrator

Hi 

 

To Do this Globally :-

//

    The only way to do this without modifying some javascript code (always a bad idea!) is to overlay the parsys component and on the cq:editConfig set cq:disableTargeting to true.

    You'll need to modify the following nodes:

    foundation/components/parsys/colctrl/cq:editConfig
    foundation/components/parsys/cq:childEditConfig
    foundation/components/parsys/cq:editConfig
    foundation/components/parsys/new/cq:editConfig

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

 

 

You can disable at component level by setting cq:editConfig/cq:disableTargeting to true.

Reference Link:- https://forums.adobe.com/thread/1212664

 

 

To disable "target" option when edit the component you need to add property cq:disableTargeting="true" to cq:editConfig Node

//             cq:actions="[text:Button,-,edit,delete]"
               cq:dialogMode="floating"
               cq:disableTargeting="true"
               jcr:primaryType="cq:EditConfig"

Reference Link:- http://aemquickstart.blogspot.in/2015/11/how-to-disbale-target-option-on.html

 

I hope this will help you.

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

Avatar

Level 2

HI Kautuk,

Thanks for the response.  I need a little more direction.  To restore the banner component back to it's non-targeted state, to which cq:editConfig node would I add the attribute? Also exactly what behavior should I expect following the edit?  Will a new icon be available in one of the dialog boxes that I can click to disable targeting on the component?  Again, my goal is to remove the targeting behavior from the banner component (see attached screenshot) without having to delete and re-create the component from scratch. I am a new AEM user, so the more detail you can provide the better.

Thanks

T Wayne

Avatar

Level 10

The blog posted here, as Kautul pointed out tells you which node to set: https://aemquickstart.blogspot.ca/2015/11/how-to-disbale-target-option-on.html?m=1. If you want to discuss, we can set up a connect session on Fri of this week. 

Avatar

Level 10

Easier resolution would be to delete the component and re-author it. While on one of the dev instance we can try to debug the actual cause.