Property locked in the higher level configuration should not be editable in the deeper level configurations
Currently, if the property is locked in the 1st level, e.g. /content/site, it is still possible to edit the value in the deeper level configuration, e.g. /content/site/region. The value should only be displayed without the option to edit it.
fixed on master. locked properties are now shown as disabled in deeper configuration levels.