bbcode error

[cotp]

I had posted a bbcode

Code: Select all

 [MYBBCODE]{text}[/MYBBCODE]

then I validated it and for some reason wanted to change it to smallcaps
So I pressed edit.

And then when I change it to

Code: Select all

 [mybbcode]{text}[/mybbcode]

I got the following message:

The BBCode tag name that you selected already exists.

My question is: is it possible to change the case after it has been created ?

Cotp

[Highway of Life]

A: Yes

[cotp]

I meant the case of the bbcode itself... Do you know how to dothat Highway of Life without having this error message ?

Thanks in advance,

Cotp

[Highway of Life]

First, I think it's a bug that it does not just allow you to change the case name...

But, there is an easy work-around:
Lets say you have [MYBBCODE]{TEXT}[/MYBBCODE]
you would first change it to:
[bling]{TEXT}[/bling]
save >
then change it to:
[mybbcode]{TEXT}[/mybbcode]

That'll do it for you.

Also, BBCode is not case sensitive, so you can use [MYBBCODE] or [mybbcode] in the posts, and they will parse the same.

Hope that helps.

[cotp]

Thanks for the hint Highway of Life

Why didn't I thought of it before

[naderman]

Because that's not what one should have to do, why don't people create bug reports if they find bugs?

[Nicholas the Italian]

Because creating workarounds is what distinguishes humans from machines? If programs are perfect, what are people here for... Just guessing...

[jimmygoon]

This type of bug is prevalant in TONS of software including, last time I checked, Windows... at least on some certain folders... but I agree it shouldn't be this way.

Its probably a matter of it running through the old "all-to-uppercase data a" CHECKED AGAINST "all-to-uppercase data b" stuff....

[Highway of Life]

I should have indicated in my first post, to post it as a Bug report, but I think I forgot to mention it, as my mind was preoccupied with figuring out the current work around.

If you come across something that seems like it *might* be a bug report, go ahead and report it... the devs will easily be able to tell if it has been fixed already, or if it's not a bug report.
In this case, it's always better to assume that it has not been reported, then assume otherwise.