No parse

[MangaD]

So I was wondering if it is possible to install a plugin for not parsing anything between [noparse] tags.

E.g.

[noparse]
@MangaD
test
http://www.lf-empire.de

[/noparse]

would result in:

@MangaD
[b]test[/b]
http://www.lf-empire.de
:)

PS: I modified the original a bit so it won't parse mentions, links and smilies as well.

Edit: Actually smilies have same problem as BBGeshi, not all are not parsed. But here it's possible to convert more characters to their codes.

[Silverthorn]

So I was wondering if it is possible to install a plugin for not parsing anything between [noparse] tags.

But... why?

Is it really that necessary?

[Hellblazer]

^ Lol i sense frustrations.

[A-Man]

lol.
I suppose for when you're trying to write something that might otherwise be parsed as a smiley or anything else.

Another use I could think of for this would be for the Commissions sub forum where text describing deals can be 'x-rayed' using those to find any hidden twists, if someone tried to be a sneaky :P. Not very convincing, probably.

[Hellblazer]

I suppose for when you're trying to write something that might otherwise be parsed as a smiley or anything else.

Over 90% of the cases, it will not be the case. If it is really required, we could rather just use some sorta alternative like using the 'code' tag or something. It already looks like the editor is too much buffed out, and adding more things that have more or less almost nil importance is another way to confuse everyone.

Another use I could think of for this would be for the Commissions sub forum where text describing deals can be 'x-rayed' using those to find any hidden twists, if someone tried to be a sneaky :P. Not very convincing, probably.

Oh please mate. That sub-forum did not even get a single sh*t by anyone till date, while there were huge controversies about it

[A-Man]

Over 90% of the cases, it will not be the case. If it is really required, we could rather just use some sorta alternative like using the 'code' tag or something. It already looks like the editor is too much buffed out, and adding more things that have more or less almost nil importance is another way to confuse everyone.

It shouldn't necessarily have a button for itself. The [hidden] and the [icode] are 2 tags which don't have buttons to use them. As for how often it's going to be used, I think as long as there is a legitimate case where it can be useful, then it could be there, if there is no harm. Especially since the plugin has been presented "on a golden plate".

Oh please mate. That sub-forum did not even get a single sh*t by anyone till date, while there were huge controversies about it

Yeah, LFE members are broke :\

[Hellblazer]

It shouldn't necessarily have a button for itself. The [hidden] and the [icode] are 2 tags which don't have buttons to use them. As for how often it's going to be used, I think as long as there is a legitimate case where it can be useful, then it could be there, if there is no harm.

Oh yeah, a no-button code would be fine for trolling noobs everyone who does not want to see it.

Especially since the plugin has been presented "on a golden plate".

Lel. xD

[Silverthorn]

Especially since the plugin has been presented "on a golden plate".

It's not the difficulty implementing it that is preventing me from doing it. It's the fact that I feel that it's pretty pointless. And, much worse, it contributes to one of the biggest weakpoints of MyBB, which is the parser. This parser's logic is ugly.

[Hellblazer]

Especially since the plugin has been presented "on a golden plate".

It's not the difficulty implementing it that is preventing me from doing it. It's the fact that I feel that it's pretty pointless. And, much worse, it contributes to one of the biggest weakpoints of MyBB, which is the parser. This parser's logic is ugly.

Yes, agreed. Useless plus dun' want to see the editor getting screwed up like the Wysiwyg did.

[MangaD]

Yes, agreed. Useless plus dun' want to see the editor getting screwed up like the Wysiwyg did.

This has nothing to do with the editor, though...