Bug: Set statements in verbatim are not ignored

Test case

Add the following to any preference topic, save and refresh:

<verbatim>
   * Set WEBBGCOLOR = red
</verbatim>

Environment

-- MattWilkie - 05 Mar 2004

Follow up

Apologies, but this is working as intended. If you'll note, the HTTP_EQUIV_ON_VIEW settings in TWikiPreferences occur inside a <verbatim> block, so they get displayed properly in view mode.

-- WalterMundt - 05 Mar 2004

Oh. I had assumed that verbatim was supposed to escape any and all processing of its contents. What else isn't escaped? Is this documented?

-- MattWilkie - 07 Mar 2004

Verbatim turns off all formatting, except that <'s and >'s are automatically escaped and the whole thing is placed in a pre block. Plugins that read topics directly can operate on verbatim contents if they wish, but plugins using rendering hooks will never see verbatim blocks IIRC.

Verbatim does not escape any settings, which includes both preference and access control settings.

-- WalterMundt - 07 Mar 2004

I wonder about this. It seems reasonable to me to assume that verbatim shouldn't set properties. One of it's main uses is showing code fragment and generally I'd think you wouldn't want those executed. I suggest we change this, possible with a option to allow this to be turned on. I've changed category from BugRejected to FeatureEnhancementRequest

-- JohnTalintyre - 08 Mar 2004

Fix record