AEM 6.5 static template - new component missing in Design mode in one environment only | Community
Skip to main content
F
fionas76543059
Level 6
March 23, 2026
Solved

AEM 6.5 static template - new component missing in Design mode in one environment only

  • March 23, 2026
  • 3 replies
  • 26 views

This is a weird one.  I created a new component. No problems with it in AEM Local or lowest environment Dev.   It was present in the Design mode. I could enable it on my page. I could then add it to the page in Edit mode.

 

However, in the Stage environment, the new component is simply missing. 

If I look in crx/de, the component is not there in the menu.

Anyone have any idea what might have happened?  Or what sort of error messages might help me debug?

thanks

Fiona

    Best answer by VeenaVikraman

    Hi Fiona,

    Since the component is missing in crx/de on Stage, this is almost certainly a deployment issue — the component node simply never made it there.

    A few things to check:

    1. Package Manager activity log on Stage — go to /crx/packmgr, find the package that was deployed, and check the install log. Partial installs can happen silently without the overall deployment appearing to fail.

    2. Reverse install test— pull the package that was actually deployed to Stage and install it on your local. If the component is missing there too, the package itself is the problem. If it shows up fine on local, something went wrong specifically during the Stage installation.

    3. Check the package version — is it possible the package version wasn't bumped before the Stage deployment? If the version number is the same as what was previously installed, the pipeline may have skipped reinstalling it altogether, leaving Stage on the older version without your new component.

    Most likely you'll find the answer in the install log. Happy to help further if you can share what you find there.

     

    Thanks

    Veena

    3 replies

    VeenaVikraman
    Community Advisor
    VeenaVikramanCommunity AdvisorAccepted solution
    Community Advisor
    March 24, 2026

    Hi Fiona,

    Since the component is missing in crx/de on Stage, this is almost certainly a deployment issue — the component node simply never made it there.

    A few things to check:

    1. Package Manager activity log on Stage — go to /crx/packmgr, find the package that was deployed, and check the install log. Partial installs can happen silently without the overall deployment appearing to fail.

    2. Reverse install test— pull the package that was actually deployed to Stage and install it on your local. If the component is missing there too, the package itself is the problem. If it shows up fine on local, something went wrong specifically during the Stage installation.

    3. Check the package version — is it possible the package version wasn't bumped before the Stage deployment? If the version number is the same as what was previously installed, the pipeline may have skipped reinstalling it altogether, leaving Stage on the older version without your new component.

    Most likely you'll find the answer in the install log. Happy to help further if you can share what you find there.

     

    Thanks

    Veena

      HrishikeshKagne
      Community Advisor
      HrishikeshKagneCommunity Advisor
      Community Advisor
      March 24, 2026

      Hi ​@fionas76543059 ,

      Your new component is missing in Stage because it was most likely not deployed or not synced properly to that environment. In Local and Dev it works because the component exists there, but in Stage the component node is simply not present under /apps. This is usually a deployment issue, not an AEM issue. Check if your latest code package was deployed to Stage. Also check the error.log for deployment or permission errors. Once the component is actually present in /apps on Stage, it will show up in Design mode again.

      Hrishikesh Kagane
        F
        fionas76543059Author
        Level 6
        March 24, 2026

        Thanks guys for the replies. I’ve looked at the author logs during deployment and I’m seeing lots of these, java.lang.OutOfMemoryError: Java heap space
        java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space

         

        So I guess this might be the source of my troubles….

        AmitVishwakarma
        Community Advisor
        AmitVishwakarmaCommunity Advisor
        Community Advisor
        March 24, 2026

        HI ​@fionas76543059 

        In Stage the component is not present under /apps/..., so it cannot show up in Design mode or the component browser. That means the code/content package with the component never actually landed (or installed correctly) on Stage.

        1. Confirm component is missing on Stage

        2. Re‑deploy the code/content package to Stage

        • Build your project from the branch where the component exists.
        • Deploy to Stage (Cloud Manager pipeline or manual package install if on‑prem/AMS).
        • In Package Manager on Stage (/crx/packmgr/index.jsp), ensure:
          • The package containing /apps/<project>/components/<your-component> is installed.
          • No warnings like "A different version seems to be installed". If you see that, click Install explicitly.

        3. Verify and enable in Design mode

        • After deployment, verify the component node exists under /apps/....
        • Open a page using the same static template on Stage.
        • Switch to Design mode and enable the component in the parsys as you did in Dev.

        Once /apps/... is present and that package version is installed on Stage, the component will appear in Design mode and be usable on pages, just as in Local and Dev.

         

        Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
          Terms & ConditionsAccessibility statement

          Loading footer...