<MTMacroDefine ctag="a" name="comment_a" no_case="1">
<MTMacroAttr name="style" remove="1"><MTMacroTag rebuild="1"><MTMacroContent></a>
</MTMacroDefine>

Then for your CommentBody tag:

<MTCommentBody apply_macros="m/^comment_/">

1. It closes tags that don't need to be closed, like the image tag.

2. It closes tags after the closing closing paragraph tag added by MT, so that the order of tags is not standard, i.e., p b /p /b, rather than p b /b /p.

3. If there's a br tag in the line, it doesn't close the b tag.

I don't know if all this matters to the Web browser, so maybe it's not that important.

My website uses XHTML. So I was wondering if your plugin supports elements from other namespaces, like xml:lang.

Thanks for making this plugin!

 — minger

By the way, I just noticed you should also change any style, class, id attribute into a safer title attribute in the comments. This avoids defacements such as this one.
(OK, so b2 was vulnerable to such ridicule 0wnage too until tonight, but at least it doesn't come with a giant security issue in the comments form by default, eheh ;)

Now, it's true that the documentation could have been more clear about the dangers of using .php and .shtml as file extensions *with* static comments, but to say that this insecurity exists out of the box is completely false.

Another default in a new MT blog is that HTML in comments is not allowed. So by default, all HTML in comments is completely stripped out--this includes both valid HTML tags and PHP/SSI/JSP/etc.

So in order to make it insecure you actually have to change the file extensions *and* check "allow HTML in comments". I forgot to mention that last night.

Anyway, yes, Brad's plugin is great, and it definitely fills a need.

This would seem most similar to your santizer, and I think folding the easy-markup of WikiText into blogspace would open up blogging for a lot more people. We just need to look at the size of Wikipedia to see that everyday people have no trouble with WikiText, but there's no way we're going to get more than 10% of the population using inline HTML.

what do you think? doable? desireable?

I'm pretty sure it would be an easy fix that could tie in nicely with the checking for a close tag, but I'm a perl retard, and thus cannot implement it myself.

Just a suggestion :)

bradchoate/sanitize.pm did not return a true value at plugins/sanitize.pl line 28.

this is my code:

recognise this error?

thanks, nardo

"One more feature of the Sanitize plugin is that while it scans the HTML for tags, it keeps up with which tags have been opened and closed. By the end of the data, if there are any tags that weren’t closed, it will append closure tags for each of them."

Can this be refined a bit? I'm having a little trouble, which is easiest explained by pointing you to the second page of this support forum thread. It may be closing a tag for me prematurely?? Or do you think it's something else causing this?

Thanks! Love the new site, btw!

a href target

Additionally, you can include title as well, allowing someone to create a full link.

img src width height alt/

Or

img/ src width height alt