Item950: wysiwyg 'sticky' needs docco, and can we add a 'sticky' css class?

I could not find docco on how to use 'sticky' on WysiwygPlugin

also, I'd like to protect some div's - but to allow the user to wysiwyg edit the content of those div's - atm, wysiwyg is removing the divs - which then loses all the magic.

alternative idea - change START&ENDSECTION to render as a div with it's name as its css id - then I can do 90% of the styling i want (obviously when INCLUDEd you can't have the div's as that would break the tml, but in place - would be useful.

mmm, another similar issue - I have table's that wysiwyg is (happily) giving up on converting, but while all the table settings are intact, it is removing the class names. poo.

-- SvenDowideit - 02 Feb 2009

WysiwygPlugin has the (admittedly terse) advice:

If you edit using the plain-text editor, you can use the <sticky>..</sticky> tags to delimit HTML (or TML) that you do not want to be WYSIWYG edited.

You should be able to place <protected> braces around the <div> and </div> to defend them.

I like the idea of using %SECTION to render divs, especially as it gives a simple syntax for plugins authors to hang their extensions onto.

Dunno about the table, require testcase to pique my interest. I guess this is the bug you were intending to report?

-- CrawfordCurrie - 02 Feb 2009

Note that the FAQ has information about sticky, but the plugin topic needs improvement.

-- CrawfordCurrie - 21 Jun 2010