1 amoun May 06, 2008 21:30
3 amoun May 06, 2008 22:09
Further:
Even if the div tag is read as html code and not text, which I don't hink it should, it should onlt then make a div inside the [code] block., which I assume is just another div.???
4 edb May 06, 2008 23:45
All Quicktags->code does is style the bit, so it still thinks a div is a div. Same with h3 or whatever: it thinks it is html. As you've discovered, converting < to < is the only solution (and by the way I don't think you need to convert > to > to post happily).
Try the code highlighter plugin? I don't have it installed anywhere to play with it because I don't really post code anymore, but I'm pretty sure it will handle stuff like that by design.
Also: here in the forums you can disable smilies for a post with code snippets in them that have "equals greater-than" and you don't have to edit the code snippet. It's a drag but (just like quicktags->code) all great advancements come with annoying little PITA bugs ;)
5 amoun May 07, 2008 01:37
Thank s EDB
I see. I thought the Quicktags->code did more than style.
I'll look for code highlighter plugin.
I can resolve the output by using < and > for the 'brackets', although the same can't be done on this forum.
However is that how it should be on b2evol? or is it a bug. I would have thought the idea of having the code option was so that tags and their brackets can be entered without it being interpreted as malicious code but not that their is a requirement to avoid the less than and greater than brackets.
Was there an instruction I missed?