I will take a look into this later should be rather easy :)



About UTF8 Support i have replicated the problem and i will work on finding a fix.

I'm using Turkish.

As far as you've managed to replicate, I'm waiting the fix then :p

Found a fix :) because UTF-8 is not vBulletin's default charset the data is incorrectly displayed the fastest way to fix this is to open your admin panel select "Languages and Phrases" then Language Manager. Now hit edit settings on the language you are using and 7 options down you will see "HTML Character Set" change this to UTF-8 (default is ISO-8859-1).
https://vborg.vbsupport.ru/attachmen...6&d=1258403651

Added FAQ to first post. Some time tomorrow i will be uploading a fix to gcbos.js this simply reduces the amount of AJAX requests made to the server and should make this more suitable for larger boards. The difference is not visible but will reduce server load when it counts.

Default charset was ISO-8859-9 here. When I change it to UTF-8, yes as you've said it works but everything except the chat breaks down. You can see it in the attachment.

I shall have a look on my test board sorry for the inconvenience. How odd seems to work for me, do you know what the collation of your database is? As that's the only thing i can see it being.

https://vborg.vbsupport.ru/external/2009/11/10.png

Nema problema. I hope you can find another fix.

I've looked to my tables and they are utf8_general_ci.

seems to work for me using some turkish i found on the net (i have my sql server set to UTF-8 aswell as boards). Im currently out of ideas towards this i shall ask around a few people i know who might have an answer :)

Interesting it really looks fine from your images but not like here. There is nothing to do but waiting then.

I've found that using this chatbox inside a style breaks IE rendering on pages the chatbox is displayed on. Renders fine in Chrome & FireFox. What's the deal?

I cant test on IE as i have no windows machine 8-) and the general vBulletin style hardly work on IE atm. Last time my testers used it IE reported fine what exactly is the error. If youc an provide a screen shot that would help :)