Hi @Mariia_Lukianet. Thanks for your answer. Of course we updated cq:designPath-s of our pages, but they have value - /apps/settings/wcm/designs/{projectName}. Under default node we have just 2 nodes which allows 2 components for 2 templates.

.

Hi @Kiran_Vedantam,Thank you very much for the answer.For some reason we don't have "cq:designPath" in our templates.But it seems that anyway it goes to /etc/designs by default.Thanks, your answer is very useful.

Hello AEM Community,We have the problem which I can't understand fully:Was in 6.3:When we were working on AEM 6.3, we were using 2 static templates where some components were allowed:And it was working good. Now in 6.5:According to repository restructure we moved  /etc/designs/default to /apps/setti...

Hi @uponline. We abandoned this theme and implemented dynatrace only in clien side.

Hi, @Vijayalakshmi_S. Thanks for your answer. Is there any workaround to overlay/override behaviour in such way that it will work without "settings" folder. The situation is that we've migrated our configuration to use Sling Context Aware Configuration and its structure is logical without this folde...

Hi once again. We made some investigations and it turned out that every folder should have "settings" folder under it. If "settings" folder doesn't exist under some folder, chain is broken and you don't see it in UI. Can we overlay this behaviour somehow?

/

Hello Adobe Community, Wer're using AEM 6.5 and faced the problem that picker.html doesn't see the children under /conf/{someFolder}. E.g. this is the structure in crxde:And this is the result in UI (no children under these folders) (page properties, advanced):Console errors (not sure that they can ...

Thanks for your answer