Well, you mentioned that it is that way by default. I pointed you back to vb.com thinking this was a bug and it just needs to be fixed. Have you entered it into the bug tracker? Were you told it is acting as designed? It just seems it would be better to have vbulletin fix it rather than have you go changed thing.
However, you wrote:
Quote:
I checked some other vbulletin 4 installs and this is the same so it is not just my board.
|
I just checked my test site and I don't see any of this behavior. I'm not sure if that is because it's fixed in 4.0.1, or what, but you may just want to wait and upgrade to 4.0.1 and see if that fixes the issue.