Expand my Community achievements bar.

SOLVED

Component EDIT/Config not visible

Avatar

Level 6

Hi Team,

 

We are facing very weird issue. After every AEM restart, Component edit/config option as well as + options to add new components are not visible.

 

AEM:6.5.11/6.5.13

 

Problem Statement:

 

  1. First we deployed Project A with archetype 30, all working fine even after system restart.
  2. Deployed Project B with archetype 32, After every restart, Component edit/configure options are not visible. After restart, we again deploy Project B, problem gets solved most of the times, not always.

 

Note:

1) NO error in console and error.log.

2) Core component version is 2.19.0 , same in all projects.

 

WORK AROUND: Go to crx/de, edit any html file, just add/remove space and save. All works.

 

Any leads would be really appreciated.

 

Regards,

KTNR

 

 

 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 5

@arvindpandey  - why are you using different archetype for A & B...?  

 Project A works fine independently so can test Project B independently (w/o Project A)?

Different archetypes should not cause issue but need to check the where the problem..... to fix it

View solution in original post

6 Replies

Avatar

Community Advisor

@arvind Your project B bundle might be still loading in background and not started , may be w.r.t to RAM usage.

Avatar

Level 2

We are seeing this issue in SP 6.5.13.0. Appreciate any update on this 

Avatar

Level 5

@arvind  - Can you make sure all bundle are in active state after you restart and test in incognito mode of browser to rollout any client side issues.

Seems the workaround you doing navigating to crx/de and saving the files gives me hint about issue in package installation or wrt previous incorrect uninstallation of package in AEM.

Project A/B using same components should impact each-other.

Avatar

Level 2

HI,

 

YES, All bundles are active after restart. Checked in Incognito too.

 

PROJECT A n B are using different components all together.

 

Avatar

Correct answer by
Level 5

@arvindpandey  - why are you using different archetype for A & B...?  

 Project A works fine independently so can test Project B independently (w/o Project A)?

Different archetypes should not cause issue but need to check the where the problem..... to fix it