Hello, I installed your cute chat for community server 2.x. It is working fine. But I can't post message in the forum after log in or can't reply a message also. It throws an error that  Editor could not load Telligent.FreeTextbox Wrapper etc.   Can tou kindly help me?   Soumitra.

cutechat: Ariel   CopyTo may take a long time and the ASP.NET page will timeout.   Please try MoveTo , or set the Server.ScriptTimeout to a larger value.   Regards, Terry     Terry,   I tried using the MoveTo method and recieved the same error. Then I changed the Server.ScriptTimeout to a larger ...

Guys,   We decided to fix this bug before version 6.0 release.   Please download the latest build from:   http://cutesoft.net/downloads/default.aspx   Demo:   http://cutesoft.net/example/general.aspx    

Hi Robert,   #1 cause It can't be the incorrect path using the demo files, isn't it? I have the same problem with sites actually using version 5.0 when I'm updgrading to 5.1, but they work with version 5   #2 cause It could be this, in my server I have no installed MSXML2.DOMDocument.4.0 because we have been using ...

While uploading a large pdf file of 4.25MB I am getting an error that just says ''Error: 1''.  What is the cause of this?  I have increased my MaxDocumentSize to 10000.

I have the following error when i try to use Cute ChatHa ocurrido un error crítico.The located assembly's manifest definition with name 'CuteSoft.Chat' does not match the assembly reference.

Sandy,   I am getting the white box with black outline that you described as well.    But, how did you get your code to work?   When I try using a directory for GalleryClient that starts with ../ , it gives me an error that says ''Cannot use a leading .. to exit above the top directory''   Thanks! Jason

Hi Rascariz, Please send the test page url to Kenneth@CuteSoft.net, I will check it and get back to you as soon as possible. Regards, Ken

Any ideas? I can get it to work as long as I use the old ForumGroupView control, but then of course the chat rooms  don't show up.

Adam,   I may have missed something but there is no change in behavior based on the new DLL.  Also, it seems to be the same version as the one in the install.  Here is the trace information.  The test I did was to put the new DLL in the bin directory, kill the IIS process, go to my website, log in, and then click on the file ...