Sorry for the problem here Hans. Here's the scoop as best I can
explain it. Initially snippets were injected directly into the skin or
zone, depending on where the snippet var was found, fully processed,
but unescaped. This worked fine in the skins, because no further
processing was done. But in zones, if the output generated any kind of
recognizable markup, it ended up being double processed as BoltWire
ran through the rest of the markup table. My solution (recent release,
evidently in 3.13) was to escape snippet output when injected into
zones, but not skins. Thus the reason for the extra parameter.

Unfortunately, if those snippets were being used as a parameter in a
function or in your case a conditional, you have the escapedcode and
not the intended value. I hacked an unescape line in the BOLTMfunc to
fix that issue, and will do the same for conditionals, by simply
changing markups.php ~270 to this:

        $condition = BOLTstripslashes(BOLTescape($condition, false));

I don't like the feel of this though--as there may well be other
situations where we want something unescaped. But I'm not sure there
are other problem areas, so maybe this is best. I like at form inputs
and they seem to work, surprizingly.

I had thought of only escaping it if there were no line breaks but
that seems more shooting in the dark. As a line return is no absolute
guarantee you want it escaped, or the lack of it that you don't. Just
a good approximation. Our current approach, with the new patch assumes
everything should be escaped except in situations where you
specifically unescape it. It's a bit complex but we'll try this for
awhile and see if it doesn't hold us a ways.

Cheers
Dan

P.S.  When you use BOLTescape($content, false); the second parameter
actually unescapes the value.  That's the reason for the first line in
the snippets function.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to