chat messages and popout is not working for sites accessed via different domains

same problem here

I have a similar problem that I posted here: #703098: Only Superuser can type a message

I hadn't tried the popout yet, I couldn't get it to type a message.

For the popout issue, I'm wondering if it has to do with URL generation.
I get: www.mysite.com/drupal/node/68?chatroom_popout=true

when for my setup I should get:
www.mysite.com/drupal/?q=node/68&chatroom_popout=true

Line 42 in chatroom.js is the culprit.

More generally though, the module doesn't currently work without Clean URLs enabled. When I switched to Clean URLs, everything worked fine.

Issue fixed, clean url was off, i configured httpd.conf with:

<Directory /var/www/example.com>
   RewriteEngine on
   RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</Directory>

... and problem fixed, now i have a new issue, mensages are not auto refreshing.

regards

Ideally, the module should detect whether or not clean url is being used, and if it isn't, throw out a different link instead. (I'd be happy to give a try at adding this, but as I'm a newbie to Drupal, I'm not sure what the proper protocol is (or whether it's already being dealt with).

FYI, i had the same problem and fixed the message issue by changing the following function::

Drupal.chatroom.postMessage = function(message) {
$.ajax({
type: 'POST',
url: Drupal.settings.basePath + '?q=' + Drupal.settings.chatroom.postMessagePath + '/' + Drupal.settings.chatroom.chatId + '/' + Drupal.settings.chatroom.latestMsgId,
dataType: 'json',
success: Drupal.chatroom.pollHandler,
data: { message: message }
})
}

( added the '?q=' + in the url field )

and fixed the pop out window by modifying the following :

Drupal.behaviors.chatroom = function(context) {
$("#chatroom-popout-link").click(function (e) {
e.preventDefault();
e.stopPropagation();
url: Drupal.settings.basePath + Drupal.settings.chatroom.banUserPath + '/' +
window.open(Drupal.settings.basePath + 'node/' + Drupal.settings.chatroom.chatId + '?chatroom_popout=true', '', Drupal.settings.chatroom.popoutParams);
});

( added the ? before chatroom_popout )

All of these seem to stem from needing clean URLS but if you don't have them then the simple change also seems to work.

Thanks, af199,

adding '?q=' solved main problem; chatting is now possible.

But there's still no popout possible. The '?' ( added the ? before chatroom_popout ) was already there.
Any ideas?
Thank you.
ts

Really great!:
I'm just new to Drupal and nevertheless was able to find a solution to the message issue and fix it in a minute. Congratulations for the help-cross-referencing (I started on Installation page of online module docs and was guided to this page by an user comment - it's just a so simple but efficient way) and thank you very much.
Sorry for spamming here - don't know where else to clap my hands.

I have also installed chat room module and I have the same problem.

1. I don't see the message in the output window.
2. The pop out window is not working properly.

Still a problem in 6.x-2.13. Had to use the snippet given by af199 to fix this issue!

Same issue.

Same problem here.

Nothing works without clean URL's, but the first part of AF199's suggestion from one year ago fixes the chat, but I can't fix the popout..

hey man !
where can i find these two function ! in which file ! please reply me

guys i fixed the problem of popout !
fixed
go to the file chatroom.js
and change this function

Drupal.behaviors.chatroom = function(context) {
$("#chatroom-popout-link").click(function (e) {
e.preventDefault();
e.stopPropagation();
url: Drupal.settings.basePath + Drupal.settings.chatroom.banUserPath + '/' +
window.open(Drupal.settings.basePath + '?q=node/' + Drupal.settings.chatroom.chatId + '&chatroom_popout=true', '', Drupal.settings.chatroom.popoutParams);
});

///changed the '?chatroom_popout=true' to '&chatroom_popout=true'

and alsoo added "?q=" before "ndoe"

it works :)

Looks like the issue is still present in the latest version.

Subscribing, any patch??

The popout works fine for me but I can't see any messages.

Hi, I´ve used the path suggested in #18 now when I write and click on chat, what I wrote is showed in the above window(where you have the convesation), however the problem is that the other people takes too long to receive the message.
I have edited the chat and in update frecuency I choosen 1, however it doesn´t work
What can I do?
thank you!

Just upgraded from 6.x-2.16 to 6.x-2.17 and don't get any messages appearing in the listing upon message submit. Quick look in MySQL chatroom_msg table shows that no messages are being submitted/recorded; have tried both keyboard Enter and clicking the 'Chat" button. Popout window pops out, but same problem is still there (ie, messages not appearing to be submitted). Copied the chatroomread.php function *just in case* it was updated too.

In meantime have reverted to 6.x-2.16 and all seems fine again.

So what's the problem? It doesn't seem to be specific to a single release: I get the same problem seen in this queue when upgrading, but not when reverting to an older [previously working] version. Are people encountering this issue when upgrading... or from initial install? Just a thought...

arrrgh, Did you try the solution posted in this comment?

@anand_s Tried the JS tweak for 'non-clean' URLs and it makes no difference. Non-clean URLs have been partially addressed in the latest release (6.x-2.17); I have rolled a patch against latest release based on #702210-7: chat messages and popout is not working for sites accessed via different domains. Also noted suggestion at #702210-18: chat messages and popout is not working for sites accessed via different domains

EDIT: Talking mince Disabling Javascript means that the message should still be submitted (although who'd want to use the chatroom without JS...), but it's just not happening in 6.x-2.17. Maybe it's a separate issue, as this is not necessarily JS-related. #orisitjustme? Chatroom doesn't appear to degrade without JS

Still having to run with 6.x-2.16 on Production

@arrrgh - My bad. I didn't see you were talking about 6.x-2.17. I am running 6.x-2.16 and I had to apply the above patch. I guess now I'll wait till 6.x-2.18 to upgrade.

Yes, The messages don't appear after it being submitted in 6.x-2.17. And the cpu is 100%.
I need help. Thank you!

I try the patch and it works.

It looks like that the CPU usage is OK.

Thank you!

I tested the Chat Room 6.x-2.18 in localhost and intranet again.
1. In localhost it's OK in IE8.
2. in intranet computer A, it's OK in IE8 too.
3. But in intranet computer B, the messages don't appear after it being submitted in ie8 and the database don't have the submitted message.
Sometimes in localhost, the messages don't appear after it being submitted in ie8 and the database don't have the submitted message.

I don't know what was going wrong, so I re-open this.

Updating title to reflect an important detail in the bug.

I'd guess that the Chat Room don't work in intranet with a different domain, because the messages don't appear after it being submitted (in IE8).
BTW: I enter the target computer's IP address.

my setup is the following(xampp for windows):
- Drupal 6.22
- Apache/2.2.11
- PHP 5.2.9
- Mysql 5.0.51a
-Chat Room 6.x-2.18

The CPU usage is 100% if someone enter to chat.
I don't know what was going wrong.

If I disable the clear url, my site will don't work, because many links in my site is based on clear url.

When chatting using the Chat Room 6.x-2.18 the CPU usage is 100% if someone enter to chat in IE.
if leave the chatting page the CPU usage is 11%(it is OK).
But FF is OK.

1. Open the IE and chat.
2. Click a link on the page and then click another link on the page.
3. You will find the IE is getting slow and you don't open any page when you click the link in the page. And you find that IE is loading for long time , and the CPU usage is 100%.

I guess that it caused by blocking issues.

Note: My site have IFrame framework.

retitle to different domains

Today, I test it again.
Everything is ok.
So I don't know what was going wrong yesterday.

All seems to work for me now. Thanks for your help.