Breadcrumb component incorrect rendering | Community
Skip to main content
NageshRaja
NageshRaja
Level 5
January 27, 2026
Solved

Breadcrumb component incorrect rendering

  • January 27, 2026
  • 5 replies
  • 65 views

Hi Everyone,

 

I have an odd problem with the OOTB Breadcrumb component in our Production Environment.

To give an overview we have a page template that has Breadcrumb start level configured at 4.

Our site structure is /content/siteA/us/en/home/child1/actualPage
 

On author at the “actualPage” URL the breadcrumb is rendering correctly as “home”→ “child1” → “actualPage”

However on Production Domain URL the breadcrumb is rendering as “us” → “home” → “child1” → “actualPage”
 

The “us” url redirects to “en” and “en” further redirects to “home”, so the “us” breadcrumb links goes to the homepage. 
Also, the hide in navigation flag is set for all parent pages at “SiteA”, “us” and “en”.

This issue occurs only on our Production environment and not in Stage or DEV even after a content sync. Any pointers for this would be helpful!

 

Thanks, 

Nagesh
 

Best answer by NageshRaja

Hi @Everyone, 

We found the fix for it. Turns out one of the pods didn’t have the “hide in navigation” set to true for “us” page.
How that happened is something Adobe is investigating but for now republishing resolved the issue.

 

Thanks!

5 replies

giuseppebaglio
giuseppebaglio
Level 10
January 27, 2026

hi ​@NageshRaja,

can you check if in your Publish instance the properties are different from the values configured on Author?

From official documentation how properties works:

  1. ./startLevel - the level at which to start the breadcrumb: 0 = /content, 1 = /content/site, etc.
  2. ./showHidden - if true, show navigation items hidden via a ./hideInNav property in the breadcrumb.
  3. ./hideCurrent - if true, don't display the current page in the breadcrumb.
  4. ./disableShadowing - for redirecting pages PageA -> PageB. If true - PageA(original page) is shown. If false or not configured - PageB(target page).
    NageshRaja
    NageshRajaAuthor
    Level 5
    January 27, 2026

    Hi ​@giuseppebaglio, The properties on author and publish are same. This has already been validated.  

    chaudharynick
    chaudharynick
    Level 4
    January 27, 2026

    Hi ​@NageshRaja 

    In the production domain URL, can you goto page properties of us page and check the “Hide in Navigation” checkbox and publish the page?

    NageshRaja
    NageshRajaAuthor
    Level 5
    January 27, 2026

    Hi ​@chaudharynick, This is already done and validated.  

    giuseppebaglio
    giuseppebaglio
    Level 10
    January 28, 2026

    Can you verify field showHidden is false?
    By looking at the method checkIfNotHidden used to filter result nodes the only two options used are:

    • component property showHidden
    • page property Hide in Navigation 
    gkalyan
    Community Advisor and Adobe Champion
    gkalyanCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    January 27, 2026

    ​@NageshRaja 

    It might be due to sling mapping or dispatcher rewrite rules and how breadcrumb component is resolving the paths

    Is this breadcrumb issue happening when you are hitting both full path and relative path with your domain in prod?

    domain.com/content/siteA/us/en/home/child1/actualPage

    domain.com/home/child1/actualPage

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    January 28, 2026

    Hi ​@NageshRaja ,

    The breadcrumb itself is fine. The difference between Stage/Dev and Prod almost certainly comes from URL => content mapping:

    • Sling mappings (/system/console/jcrresolver) and/or
    • Dispatcher rewrite rules

    are resolving the Prod request differently so the breadcrumb “sees” a different starting level and includes us.

    Try below steps:
    1. Check how the URL resolves on Prod vs Stage:

    On each env, request:

    Use request log (Developer Console => Requests) and compare the Resource line:

    • It should resolve to /content/siteA/us/en/home/child1/actualPage in all envs.
    • If Prod resolves differently or via /us first, that’s the issue.

    2. Compare Sling mappings

    • Go to /system/console/jcrresolver on Stage and Prod.
    • Compare mappings for:
      • domain root
      • /content/siteA
      • /content/siteA/us and /content/siteA/us/en
    • Make Prod mappings match Stage/Dev (or set a clean mapping like domain => /content/siteA/us/en/home).

    3. Compare dispatcher rewrites

    • Check dispatcher/src/conf.d/rewrites/*.rewrite.conf (or equivalent) for Prod vs Stage.
    • Look for special rules for /us and /en.
    • Align Prod rules with Stage/Dev, avoid extra /us or /en hops.

    4. Clear caches

    • After changing mappings/rewrites, flush dispatcher cache for the site and re‑test.

    Once the Prod URL mapping matches Stage/Dev, the breadcrumb with startLevel=4, showHidden=false will render as home => child1 => actualPage everywhere.

    Thanks,
    Amit

      NageshRaja
      NageshRajaAuthorAccepted solution
      Level 5
      February 4, 2026

      Hi @Everyone, 

      We found the fix for it. Turns out one of the pods didn’t have the “hide in navigation” set to true for “us” page.
      How that happened is something Adobe is investigating but for now republishing resolved the issue.

       

      Thanks!

      Terms & ConditionsAccessibility statement

      Loading footer...