[VBDev]

Originally Posted by Playa82

oh, ok. but i got 0.4.0 installed. and i fixed it with the files 2 posts above ;-)

Those fixes should not be needed when using the 0.4.0 with the last vbulletin versions.

Originally Posted by johnban

No, I check and I have put

Minimum number of posts to use the chatbox --> 1
Minimum number of posts during the last 24H to use the chatbox --> 0

The count is not based on a number of posts since install, that's strange.

Can you make a screenshot of all usergroup permissions please.

Originally Posted by Tom S

I am also having troubles with the channels showing text instead of the .gif for team and pm. I noticed for the General channel that the image called for in the coding is not the same as the image name. I am having troubles getting the Gen channel to show anything. Could this be one of the issues or has it always been this way?

In the coding it calls for <img id="mgc_cb_evo_channel_$channel[chanid]_on"

But in my channel image directory, it is called mgc_cb_gen_channel_sel.gif.

Is the evo and gen confusing the program?

I may be way off base, learning the coding stuff.

Another thing that I have noticed is that images folder for vB has the small i, and with the folder in the download package has the large I (Images).

Tom S.

You need 3 images for a channel, they have the same name except the end :

• _sel
• _nosel
• _new

followed by the extension.

Originally Posted by XiZa

I've noticed that you are sending the entire contents of the chat table with each ajax request. I think it would be better if you only sent some sort of javascript array (json) with the new entries, and an empty response if no new messages were sent.

It will save on javascript processing (possibly javascript memory leakage as well) and on bandwidth considering this auto refreshes every x seconds.

Yes that's right I am sending the whole content.

It would indeed be perhaps better to send with the new entries.

However, imagine if a user remove a shout or ignore someone, then the need of a full reload is logical.

I have perhaps not had a good idea to code it like that but considering what I just said I don't see how I could do it in another way but perhaps you have another good suggestion ?