Question: Image in Sig

[Blaine]

Is having image in your sig not allowed anymore, as i cant seem to add one i keep getting this error

BB code quote is not allowed

[NightWish]

The [QUOTE] bb code is not permitted in signatures. However, that has nothing to do with images. For images you need to use either this bb code:

[IMG]...Image URL goes here...[/IMG]

Or, for images uploaded to the forum as a Signature Picture, this one:

[SIGPIC][/SIGPIC]

[GHDpro]

Look closer at the error message. If you place just an image in your signature, I'm sure it'll work fine (as it does for most people).

The real problem is that (as the message indicates) using the [quote] bbcode in signatures is not allowed. The fact you currently are using it in your signature problably means the ability to disallow usage of the [quote] is probably a feature introduced (and set to "No" by default) with vBulletin 3.8.0, to which we upgraded last weekend.

I've now changed the usergroup permissions to allow the usage of [quote], [code] &[list] again.

[NightWish]

Actually, the the permission was deliberately removed quite a while before the upgrade; because we explicitly disallow some of those tags in signatures:

In addition, please do not use spoiler, indent or quote tags in signatures

The rules have always barred their use, but we hadn't configured the forum to take this into account. Before version 3.7 you didn't get a list that told you what you could and could not use in signatures (based on the forum settings); now you do. Blocking the use, rather than retroactively enforcing the rules with infractions, was both fair and less confusing (given the forum was telling people they could do something we didn't (and I assume still don't?) want them to do.

[GHDpro]

Er, oops, it seems I missed that. I've returned the settings back.

So, a final answer to the OP: you can put an image in your signature just fine, but you have to take the quote bbcode out, as that may have been possible in the past, but is no longer allowed.

[Blaine]

Originally Posted by NightWish

The [QUOTE] bb code is not permitted in signatures. However, that has nothing to do with images. For images you need to use either this bb code:

[IMG]...Image URL goes here...[/IMG]

Or, for images uploaded to the forum as a Signature Picture, this one:

[SIGPIC][/SIGPIC]

I am using the [img] link [/img] code and i still get that error.

[Skyfall]

Originally Posted by Blaine

I am using the [img] link [/img] code and i still get that error.

To me it looks like you have nothing entered in your signature field at all though

[Pellissier]

Yeah his sign field is empty. It might depend on the error though, some screencaps would help.
I pmed him (2 minutes after his above post) to send me the image / url, in order to make some tests on my own profile if needed be, but looks like he vanished already ^^

[NightWish]

Originally Posted by Skyfall

To me it looks like you have nothing entered in your signature field at all though

If the forum is blocking a bb code in the new signature, it will not update the signature and thus the signature remains blank. We need to know exactly what is being entered in the signature edit field to resolve the problem sensible. If all else fails this can be a screen shot as Pellissier suggests.

[felix]

Originally Posted by Blaine

I am using the [img] link [/img] code and i still get that error.

Copy the following and hit the preview button:

[img]http://forums.animesuki.com/images/as.global/smilies/smile.gif[/img]

Do you still get the error? (take a screenshot¹ if you do)

__________________
¹ press PrtScrn key (top right of keyboard) go to paint and open a new document and hit Ctrl+V to paste.

[Blaine]

Ok it seems to be working now, strange that it deleted my existing sig since my last visit to the forums.

[Kitsune]

Maybe breaking forum rules?

[Pellissier]

Originally Posted by Kitsune

Maybe breaking forum rules?

Uhm.. no. As far as I know, there is not an automatic sign deletion process for signatures breaking the rules. It's manual (and comes along with a notification too).
In the above case, most likely there was something wrong with the link and how it was written or tagged, we'll never know for sure anyway.