The last chat messages in the chat 'window'/area are getting reloaded in an infinite loop again and again and again, in some important browsers (at least faulty in Safari 4 and FF 3 - Opera 9 seems fine though, didn't test in IE).
In other words: If some chatter posts a chat message, she and all other participants are receiving the same message time and again, i.e. the same last message get's appended in the chat area infinite times.
Since this happens with both branches in in several browsers, and renders the module basically useless, i marked it critical.
Since we're in a *very* time-tight project, we'd need some hint here real soon!
If there's just a bug, we're happy to help fixing it!
Is there an older version which is not subject to this bug?
Thanks!!
Comments
Comment #1
Anonymous (not verified) commentedwill look into this. i'm picking up the module after quite a break, and it was very broken.
patches welcome.
Comment #2
Anonymous (not verified) commentedi can't reproduce this. can you give me some more information about exactly how you reproduced this?
i tested this on the latest DRUPAL-6--1 branch. please set back to active when you post some more information.
Comment #3
danielnolde commentedHey Justin,
just double checked on two different systen (local VMWare Ubuntu server, differently set up dedicated Dev Server Ubuntu) and three different browsers, the problem is definitely there as described and persists.
Exemplary system data:
Drupal: 6.14, Acquia Drupal
MySQL: 5.0.51a
PHP: 5.2.4-2ubuntu5.6
Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch
Chat Room: 6.x-1.0-beta - as well as 6.x-1.x-dev (2009-09-29)
we can try and help with the bugfix - but we need a hint in which code/function/client-server-side/file to start looking... any ideas?
cheers,
daniel
Comment #4
Anonymous (not verified) commentedplease test again with 6.x-1.0-beta9. can you describe this in more detail? perhaps set up an install somewhere i can open in a browser and see the problem? i still can't reproduce this issue.
as for hints, i still can't reproduce this issue. one possibility is that this code
isn't working as it should, and the last seen cmid is not being updated? can you start logging the POST'ed cmid value to a file and check that its ok?
there is an underlying issue with the initial 6.x port in that cmid is not validated on the client side at all, so requests can pass each other on the wire, and the same messages get written twice in a given client.
i've fixed that in the 6.x-2 branch, but you're issue sounds bigger than that.
Comment #5
Anonymous (not verified) commentedping? still seeing this? have you tried the 6.x-2 code?
going to close this without feedback shortly.
Comment #6
Anonymous (not verified) commented