Read-Only (Locked) Elements

Making Elements Read-Only

There are three scenarios when XML editor might need to prevent user from modifying certain elements of XML:

Prevent editing of certain attribute
Prevent element from being removed from its parent
Prevent editing of element and all child nodes contained in it

All three scenarios could be enforced for certain class of elements (see lock attribute in model.xml) as well as only for specific element within provided XML.

To enforce one of these rules on specific elements within XML, developer could use special _lock attribute. Its value will identify how the element should be handled. Here is the list of available values: _lock attribute value Description attribute:<attribute_name> Prohibits editing of the specified attribute. For example:

<section product="UV Scanner"
        _lock="attribute:product">
    ...
</section>

content Prohibits editing of element along with attributes and child nodes. For example:

<section _lock="content">
    ...
</section>

inparent Prevents any action that could remove element from its parent. For example:

<section _lock="inparent">
    ...
</section>

any combination of values above Combines effect of multiple settings. Values should be coma or space separated. For example:

<section
      _lock="inparent,attribute:product">
    ...
</section>

At the moment editor would only enforce read-only policy for WYSIWYG and Outline editing modes. Using raw XML editing mode user can overwrite read-only customizations. This issue will be addressed in the future versions of the editor.

You can find examples of the _lock attribute effect in the Sample Documents section.