Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Help icon in sidekick

Avatar

Level 4

When I click on help icon in sidekick it is displaying the page with Add content here message,But I want to redirect to https://docs.adobe.com/docs/en/cq/5-5/wcm.html.

 

 

12 Replies

Avatar

Level 10

Can you share screenshot of which Icon you are referring?

Avatar

Level 10

which version of AEM are you using, it is redirecting to me properly. 

Are you facing this issue for all instances or only one of your instance ?

When I click help button in siteadmin page or sidekick,I am getting the message as Add Content here in new tab.I have attached my screenshot.

Avatar

Level 10

Looks like some of your code is conflicting, 

Mine is working fine. Did you added some customization for this help icon?

Avatar

Level 4

I have attached my sidekick.js page.Can u suggest how toavoid this conflict.

Avatar

Level 10

Fews questions:

Which AEM version is yours?

Have you tried to customized anything in this file sidekick.js?

Are you seeing this in all browser?

Did you try creating new AEM instance and see the behavior?

Thanks

Avatar

Level 10

Does this path exist in your system?

/libs/day-docs/content/en/cq/current/wcm.html

Thanks

Avatar

Level 4

Yes,the same path.What I should do to change my path

Avatar

Level 10

AFAIK, this path does not exist by default in AEM ( m referring 6.1 )

First, AEM tries to find this path on your local aem instance, if it does not exist then it opens the links in adobe documentation. (which practically happens in my case)

But in your case someone has created this path so it opens the page from local Instance

Please check why it was created....there has to be some reason...

Avatar

Level 4

Is there any possible way to remove that path and redirect that page tho adobe documentation?

Avatar

Level 10

I am asuming you are aware why this path was created. 

Try deleting the path from /libs and see the behavior

Make sure you take backup prior deleting

You can delete that node unless you are not overriding the same.

Also, is this node exists on every new instance you are creating ?? as I also dont see that node as @edubey mentioned.