[noparse] tags bug

[PurplePoot]

If you post (in noparse tags) empty tags like [code]xxx[/code] (without the xxx), it automatically removes them even though they're in tags.

I don't know if this is hardcoded into vBulletin or what, but it's a bit annoying.

 

[Wolverabid]

Um...

[code][/code]

 

[PurplePoot]

Odd, it deletes them from me. It physically removes them from the message alltogether

EDIT:

[code][/code]

Hmm, it's working now. Odd.

 

[Samuraid]

There is a setting deep in the vBulletin PHP code that makes vB remove certain tags that have nothing in between them. Some of the tags are like that.

Ralle also may have been editing things...

 

[Rui]

The same happened with the

• tags, which I reported a month ago or so.
• Yes that space up there contained the [I]noparse|trigger|/trigger|/noparse[/I] stuff.

 

[Ralle]

Well, I haven't looked at this at all. Do you use the WYSIWYG editor?

 

[PurplePoot]

I use the super-basic one, without any extra junk (just a text box)

No idea what it's called.

 

[Ralle]

anyway.. Can you provoke the bug or is it gone?

 

[Wolverabid]

[TRIGGER][/TRIGGER]

 [plain][TRIGGER][/TRIGGER][/plain]

The noparsed trigger tags are sill bugged for me as well. When posting, they are not only not displayed, they also disappear from the post iteslf. The noparsed tags are often converted to all lowercsae characters as well.

[code=jass][/code]

 

[Ralle]

gaergaergaergaergaer[code=jass][/code]

 

[PurplePoot]

In the order:

quote,code,ljass,jass,trigger

Zomg, they're all gone now. This is creepy, I could do it the last few times I posted.

 

[Wolverabid]

Test

Test

[code=jass][/code]

[CODE][/CODE]

[TRIGGER][/TRIGGER]

It looks to me like the Chieftain exterminated (some of) the bugs on the site itself. You may want to investigate exterminating some bugs on your end if it's not working for you.

[EDIT] Include some text in your post BEFORE displaying the noparsed tags. It looks to me as if when the noparsed tags are the FIRST thing in the post, the FIRST ONE will disappear. However, as things stand right now I can easily work around it.

 

[PurplePoot]

(code included in noparse tags above)

[code][/code]

(code included again in noparse tags)

Blegh, it appears that's the problem.

 

[Hakeem]

Problem with the reg string probably.

 

[Ralle]

There's a difference if you use WYSIWYG editor and when you are not.