Helo,
for our project it would be nice to have a way to protect the HTML structure of the content and let restricted editors only have access to text elements within the content. Can this behavior achieved by ProdectedSource or ProtectedTags, or does it need some in depth coding? As we have realized we cannot recommend editors to understand publishing principals. We have dedicated editors, who are responsible for content look. Right now translators can break content look, and it is hard to teach them.
Any idea?
for our project it would be nice to have a way to protect the HTML structure of the content and let restricted editors only have access to text elements within the content. Can this behavior achieved by ProdectedSource or ProtectedTags, or does it need some in depth coding? As we have realized we cannot recommend editors to understand publishing principals. We have dedicated editors, who are responsible for content look. Right now translators can break content look, and it is hard to teach them.
Any idea?
Re: Need DOM tree protection. ProdectedSource? ProtectedTags?
Responsive tasks to be modified by such a plugin are the deletion keystroke handling (Delete, Backspace, CtrlBackspace), typing over selection, and dragging content.
Starting with the keystroke handlers I have found the corresponding commands are implemented in fckenterkey.js. May my plugin override FCKEnterKey.prototype.DoDelete for example by replacing DoDelete with my modified version?
If not, how can I cancel the delete keystroke event to stop damaging tags?