According to the documentation this AllowEditInvariantFromNonDefault setting should be added to Umbraco:CMS:Security, however according to the schema it should be added to Umbraco:CMS:Content. This is confirmed by PR #12960.
Anyway, you should now also be able to add a supportsReadOnly setting to the property editor, see documentation:
By setting this value to true you should be able to implement your own 'readonly' behavior, overriding the default overlay that Umbraco adds to property editors that don't implement this feature. This doesn't seem to work though, as in Umbraco still just adds an overlay. This new settings is not being recognized by the package.manifest schema, I don't know if that has anything to do with the issue.
Has anyone else fiddled with this new feature yet? And got it to work on a custom property editor?
New 'supportsReadOnly' feature for property editors in Umbraco 10.2+
I'm trying to wrap my head around the new
supportsReadOnlyoption for (custom) property editors.https://umbraco.com/blog/umbraco-102-release/#readonly
https://www.youtube.com/watch?v=3Z4Quq82FDE
I've upgraded to Umbraco 10.2.1 and enabled the 'Allow Edit Invariant From Non-Default' feature:
https://our.umbraco.com/documentation/Reference/Configuration/SecuritySettings/#allow-edit-invariant-from-non-default
According to the documentation this
AllowEditInvariantFromNonDefaultsetting should be added toUmbraco:CMS:Security, however according to the schema it should be added toUmbraco:CMS:Content. This is confirmed by PR #12960.Anyway, you should now also be able to add a
supportsReadOnlysetting to the property editor, see documentation:https://our.umbraco.com/documentation/Extending/Property-Editors/Package-Manifest/
By setting this value to true you should be able to implement your own 'readonly' behavior, overriding the default overlay that Umbraco adds to property editors that don't implement this feature. This doesn't seem to work though, as in Umbraco still just adds an overlay. This new settings is not being recognized by the package.manifest schema, I don't know if that has anything to do with the issue.
Has anyone else fiddled with this new feature yet? And got it to work on a custom property editor?
is working on a reply...