Context aware configuration | Issue with nested configurations

[janemartin]

Hi Team,

When we author an inner context aware configuration without first authoring the outer configuration, it gets saved as a folder in CRX although we have PagePersistenceStrategy enabled, and when published these changes don’t appear in the publisher. However, if we save the parent configuration before creating the child configuration, it gets saved as a cq:Page without any issues and works as expected. I have provided the detailed steps for more clarity on the issue:

• Open a new configuration that contains a child configuration.
• The parent configuration has no fields authored.
• Directly open the child/inner configuration.
• Author the inner configuration and save.
• Now open crx, the configuration is saved as a folder (sling:Folder)

Please note: If we author and save the parent configuration first, then proceed to author child configuration, it works as expected and node is cq:Page. Problem only exists if child configuration is authored first.

Environment: AEMaaCS DEV
Version:2024.6.16971.20240628T122619Z

Please let us know if any solution for this, or if this is the expected behavior. Thanks!

[stefanseifert]

i was not able to reproduce the problem - neither locally on AEMaaCS SDK nor on an actual AEMaaCS cloud instance.
are you a) using the latest io.wcm.caconfig.editor version and b) using the AEM Page persistence strategy from latest io.wcm.caconfig.extensions?

what i did to try to reproduce the problem:

• deploy our sample app: https://github.com/wcm-io/io.wcm.caconfig.sample-app
• open caconfig editor: http://localhost:4502/content/contextaware-config-sample/en/config.html
• delete existing "Sample Configuration Nested" configuration
• add new "Sample Configuration Nested" configuration
• before doing anything else, go to "Sub Config 2" via edit button
• enter a string in "Sub 2 String Param" field and save

the node is created as expected with

• /conf/contextaware-config-sample/sample/sling:configs/io.wcm.caconfig.sample.config.ConfigSampleNested -> cq:Page
• /conf/contextaware-config-sample/sample/sling:configs/io.wcm.caconfig.sample.config.ConfigSampleNested/jcr:content -> cq:PageContent
• /conf/contextaware-config-sample/sample/sling:configs/io.wcm.caconfig.sample.config.ConfigSampleNested/jcr:content/sub2 -> nt:unstructured

can you reproduce your problem with our sample app?