[VBDev]

Originally Posted by Dr. Bantham

I just attempted an upgrade from 1.2 which seemed to go well, but messages are not appearing when I enter them in the main channel. Private messages and team messages appear to be working properly. When entered in the main channel, the input box goes blank (as it should), but the message never appears. No error messages appear, however. The /announcement command is also not taking. I believe I followed all upgrade instructions, including file upload, overwrite product and command uploading.

I had also been using the page variable with success to insert within other pages. However, with the upgrade these now display the interface box with a perpetual "Loading..." message.

I am using vBulletin 3.6.7, which worked well previously.

UPDATE
There is no General Channel listed in ACP-->MGC Chatbox Evo-->Manage Channels. Should there be? I see only the Team Channel and Private Channel.

I think it's the same problem as above, first message don't work.

No the general channel is by default in the chatbox and shall not appear there.

Originally Posted by lucky51

ban command still not working in new version

Hum I forgot to test it after you reported it How bad boy I am !

Originally Posted by Dr. Bantham

I don't know what I did wrong with the upgrade (if anything) or how I managed to get it working (repeated tries), but it appears to be working now. With the exception, however, of the Display on Defined Pages as a Variable. The pages I had working with the previous version using this option no longer display the box. Any ideas?

I haven't changed that, it shall still be working.

Originally Posted by Saint_ago

The first message you enter in the input box isn't showed when you press enter or click ok. It just clean the box. The second one and all after that works ok.

Tested in opera and ie7, same problem

EDIT: If the option "Show a small prompt message in the chatbox" is on, the problem happens (and the prompt message isn't showed at all). If the option is turned off, works fine...

I would have said the contrary. I encountered it on my side and it's was when prompt message option was disabled.