OOTB Navigation Component Behavior | Community
Skip to main content
sachinn20956098
sachinn20956098
Level 2
February 16, 2019
Solved

OOTB Navigation Component Behavior

  • February 16, 2019
  • 2 replies
  • 1384 views

I tried using the OOTB AEM 6.4 Navigation component (v1) , but i observed a confusing behavior of this component :

I added this component on page : /content/we-retail/us/en/men.html and authored the navigation root path as : /content/we-retail/ca/en. But the resultant navigation pages are taken from /content/we-retail/us/en/ instead of /content/we-retail/ca/en.

Any reason for this behavior?

Thanks

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

Could be a bug, but when you used the non-existing page in the same site but from another site, it works.

e.g.

Add navigation component on page : /content/we-retail/us/en/men/products.html and authored the navigation root path as : /content/we-retail/ca/en/men2. But the page /content/we-retail/us/en/men2 shouldn't be exist.

2 replies

smacdonald2008
smacdonald2008
Level 10
April 12, 2019

Sounds like a bug. It should reflect the value that you specified.

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
April 13, 2019

Could be a bug, but when you used the non-existing page in the same site but from another site, it works.

e.g.

Add navigation component on page : /content/we-retail/us/en/men/products.html and authored the navigation root path as : /content/we-retail/ca/en/men2. But the page /content/we-retail/us/en/men2 shouldn't be exist.

Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...