The code tags should be fixed now--in my translation from JavaScript to PHP I decided to invert one of the conditions, but in doing so I got it completely messed up...the logic now is if the first [ code ] comes after the first open curly brace, or if the last [ / code ] comes before the last close curly brace, you get a warning. Once the code tag checker makes it through some more normal usage, I can also look into exempting long-time posters from it in order to make it easier to post curly braces...
@hk_mp5kpdw That behavior sounds like it might be a vBulletin performance optimization (similar to what you sometimes see in Google results where it doesn't accurately display the total number of available pages for some searches--I assume to avoid returning large result sets)
@Shakti One of my goals is to avoid having to deal with custom images that will be overwritten when upgrading vBulletin. If I can find a way to improve the images while meeting that goal, and I find better images, I will consider it, but no promises yet.
@Yarin Thanks! This should now be fixed.
@CommonTater Thanks for pointing out a workaround!
@cpjust It looks a lot more like the forums used to look than it did right after upgrading...That said, I tend to agree that everything takes up too much vertical space, and that's something I will consider addressing once some of the other issues are addressed.
