Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

picker.html related to "cq:conf" property doesn't see children under /conf folder

arturl43391132
Level 4
Level 4

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:

arturl43391132_0-1601381058139.png

And this is the result in UI (no children under these folders) (page properties, advanced):

arturl43391132_3-1601381232799.png

arturl43391132_1-1601381102745.png

Console errors (not sure that they can affect it because I see these errors every time I open dialog but other fields work good):

arturl43391132_2-1601381174360.png

Does anybody have any idea what's the problem of it?

Thanks in advacne.

 

 

1 Accepted Solution
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @arturl43391132,

Config path browser lists the configs under /conf which has folder named settings.

Per the screenshot shared, if you are expecting child configs under es_cl, then those child configs should have "settings" folder within.

Cross check if you have one. 

Have created similar structure in my local for testing.

Screenshot for reference:

Vijayalakshmi_S_0-1601391456383.png

Vijayalakshmi_S_1-1601391539049.png

View solution in original post

4 Replies
arturl43391132
Level 4
Level 4
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?
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @arturl43391132,

Config path browser lists the configs under /conf which has folder named settings.

Per the screenshot shared, if you are expecting child configs under es_cl, then those child configs should have "settings" folder within.

Cross check if you have one. 

Have created similar structure in my local for testing.

Screenshot for reference:

Vijayalakshmi_S_0-1601391456383.png

Vijayalakshmi_S_1-1601391539049.png

View solution in original post

arturl43391132
Level 4
Level 4
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 folder. Thanks