Contexthub not defined in AEM 6.4 | Community
Skip to main content
Level 2
February 5, 2019

Contexthub not defined in AEM 6.4

  • February 5, 2019
  • 3 replies
  • 8495 views

Hi Team,

Issue

Below are the steps to reproduce the issue

1. Open the asset share page and click on cart to download the assets.

2. On first attempt the assets will get downloaded from cart

3. Again open the cart and download the asset.

4. The asset will not be download and there is an error "contexthub is not defined .............contexthub.kernel.js"  on web console.

Trials

I read some article on this like

ContextHub is not defined following Download · Issue #237 · Adobe-Marketing-Cloud/asset-share-commons · GitHub

and changed the asset share commons version from 1.5.0 to 1..6.6 on my local instance but the issue still persist.

Observation:

The js which this issue referring is, contexthub.kernel.js which is included in a JSP under libs path.(will update the path here)

The difference from AEM 6.3 is, contexthub node is not available under etc.

Please let me know if anyone got the resolution to above issue

Thanks,

Ranjna

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

3 replies

Gaurav-Behl
Level 10
February 6, 2019

Per link that you shared, the bug is fixed and released. You may install latest package, clear internal cached libraries and test otherwise, open a ticket similar to the link that you shared.

Releases · Adobe-Marketing-Cloud/asset-share-commons · GitHub

HTH

ranjnaAuthor
Level 2
February 6, 2019

Hi,

I did install the asc 1.6.12 but it couldn't resolve the issue.

What i have observed that contexthub and contexthubsegmentation path in content/home/en node is pointing to old location in etc which is not available in aem6. 4.

So i changed the reference to new location(libs) but then i am getting some methods are not supported issues.

Should i follow any sequence while installing asc?

Where should i point the reference location from content/home/en node?

Any suggestion would be really appreciated

Thanks,

Ranjna

Gaurav-Behl
Level 10
February 6, 2019

As far as I know, the sequence of installation doesn't matter and it should point to /libs to utilize the updated features.

It would work with /etc as well but not sure if the behavior would be different.

Try this -

Use /etc path and add slingResourceSuperType to /etc path node and point it to /libs path. That might do the trick.

Community Advisor
February 6, 2019

Refer the following forum link - https://forums.adobe.com/message/10907246#10907246​ , this may help you.

Regards

Albin I

smacdonald2008
Level 10
February 6, 2019
Level 2
November 26, 2022

Hi @smacdonald2008,

Thanks for all your work supporting the community over the years.

I appreciate that you may want to move on and that supporting older content may be a lot of work but is there any chance you can disable the redirect on articles like this one? I got a tantalising glimpse of this answer before being whisked away to your new site!

Although a lot of it is 'legacy' and AEM has moved on, there's still plenty of useful information that was there.

Kind regards,

David

 

ranjnaAuthor
Level 2
February 22, 2019

i did overlay the part of ASC in my project so in this scenario ill have to do the changes in custom code after installing ASC updated package(1.6.12) and then there was a distortion in UI so i did fix that as well.  In the end , it did work out after combination of changes.

Thanks team for all your support