Display of inherited singleton configurations without property inheritance misleading


there is a similar problem for singleton configurations as we've solved in for configuration collection items.

steps to reproduce the problem:

  1. go to http://localhost:4502/content/contextaware-config-sample/en/sub-page/config.html#/io.wcm.caconfig.sample.config.ConfigSample

    • this configuration exists initially in the sample content of the sample app

  2. delete this singleton configuration

  3. open the configuration "Sample Configuration" again for the sub-page

  4. it looks then like

what is misleading:

  • mixed display of inherited and non-inherited properties, although property inheritance is not enabled

  • when property is edited and saved (e.g. in DAM path), and the configuration is loaded again only the new value is displayed, the other values not (until property inheritance activated)

it would be nice to apply the same handling as for config collections:

  • if the whole singleton configuration is inherited in one piece, the whole configuration block should be disabled, and a text displayed like "This configuration is inherited. Click here to break inheritance".

  • When this break modus is entered enable property inheritance is activated by default (but can be deactivated before saving).

  • the behavior should be as consistent as possible to that of collection items


David Ding
June 7, 2017, 9:19 PM

if the whole singleton configuration is inherited in one piece, the whole configuration block should be disabled

For this to work, I think it is necessary (or, at least, it would be helpful) for http://localhost:4502/content/contextaware-config-sample/en/config/_jcr_content.configData.json?configName=io.wcm.caconfig.sample.config.ConfigSample to include "inherited": true in the response. (similar to collection items)

Is it possible to do this?

Stefan Seifert
June 12, 2017, 10:24 PM

i'd already added this in this rev - but the sample app included a dependency to a old editor version, so it was not active without redeploying the editor bundle itself.
please try again with sample-app from develop branch.

David Ding
June 22, 2017, 8:59 PM
Stefan Seifert
June 23, 2017, 2:57 AM

works perfectly - thanks!
(i've also added an entry to the changelog - changes.xml)





Stefan Seifert




Affects versions