currently there is no possibility in AEM to activate context-aware configuration to publish instances if it is stored below /conf.
it would be nice if the configuration editor would provide a "publish" button to accomplish this. we need to sort out how the configuration editor detects the correct paths below /conf because this is an implementation//configuration detail.
thinking further a reference check might be useful which gives a notice if configurations higher up in the inheritance hierarchy have unpublished changes, and offer the option to activate them as well.
I think there was a misconception regarding what this issue is about!
It's not about publishing the configuration page itself, but it's about publishing the configuration (that is written in /conf, in the correct context root).
When I was scrolling through the branch's contents, without testing the code, it seems that it's activating the configuration editor page, instead of activating the underlying caconfig that was entered by the user?
that is the plan - but together with the CAConfig Reference Provider (already implemented in ) activating the (empty) editor page results in activating the config pages below /conf as well, when they are modified since last publishing.
you need to deploy the wcm.io caconfig extensions bundle for this.
What if the page strategy is not used?
I.e. the config is not saved in cq\:Page nodes.
thanks, it's works & merged!
it will only work when the "AEM page" persistence strategy is used.