I get this error in the Firefox addon Firebug.

Also, The messages aren't showing up in Internet explorer 6. I tried a few other themes with the same result.

Server is Linux with PHP5.2 running Drupal 5-dev

Comments

dwees’s picture

Thanks for the error warning. I will try and sort out this issue by tomorrow. I'd really like to get this module producing a lot less errors. :)

Dave

dwees’s picture

Assigned: Unassigned » dwees

Here's where I think this error is coming from. I include the jQuery.js file inside my Iframe content so that it has access to the $.Ajax call. Drupal also includes the jQuery.js file as part of its page. Some browsers can handle the duplicate function naming because they actually attach the functions to window or frame, rather than to the page, whereas I am pretty sure IE is not that clever.

So it looks like the solution is to use an external library and ask people to download it and place it in the right folder and use it for the Iframe Ajax instead. I have found a reasonably simple library to use, and will go about making the changes tonight.

If someone reads this and can shed some more light on this problem, that would be great.

Dave

mlncn’s picture

No light, just a report that it doesn't refresh in Firefox 2.0 for Mac either... and that other than that the module works perfectly for our needs, a site with a fairly focused community.

elizabeth.wood11’s picture

I don't get an error message, or at least not one that I've found. But I do find that using Firefox 2.0.0.4 I only see my own messages or others' messages if I manually refresh the browser window. They don't refresh on their own. In Safari2.0.4 the block title shows up but its window does not, and no messages appear even if I manually refresh the browser.

I'm looking for a simple chat module to run on Drupal 5.1 that will allow members of my site (http://sexinthepublicsquare.org) to coordinate with each other while online at the same time.

Thanks for any help you can offer!
Elizabeth

mgifford’s picture

Ok, I'm getting this error now "$ is not defined", but I didn't earlier in the week. I had verified that this was working nicely in both firefox & mostly well in safari, but now I just get this error in firebug and no fadein/fadeout functionality when you click on the demo:
http://openconcept.ca/blog/mgifford/jquery_load_XML_AJAX_fadeIn_fadeOut

The error I get is:
[Break on this error]
$(document).ready(function(){$('#itemsControl').change(showItemInfo);});

But that's pretty standard from what I know of AJAX.

Any ideas what I'm missing? I was pretty sure I didn't need drupal_add_js(), but who knows with caching, maybe there was still a value left in there.

Mike

rschaa’s picture

Title: $ is not defined Line 96 » timestamp is allways 0

Hi,

in the sql-table the timestamp allways 0,

you use microtime() and will store this in an integer, but microtime() returns two strings!

when you use time() then you can this store in integer :)

hope i help you, a little bit

dwees’s picture

Hi there,

I have this fixed in the current version, but have not sent it to CVS yet due to errors. Please be patient.

Dave

BDaggerhart’s picture

Is there any way to subscribe to this so we'll know when you update it? The auto-refresh is all I'm waiting for to put the chatblock on my site.

dwees’s picture

I think only the owner of a bug can subscribe to the bug?

I'm not sure sorry, just check back here.

BDaggerhart’s picture

Any new information on this? Just doing my three-weekly checkup :)

dwees’s picture

Status: Active » Fixed
plim’s picture

Hi dwees,
Is this issue is fixed ? I downloaded the lastest release of this module. The refresh is not working, here is the information available with firebug. for all messageid in the DB, the timestamp is always to 2147483647

information for the UPDATE :
POST http://www.club-info-montrabe.net/?q=chatblock/update (1516ms)

Response Headers
Date Mon, 12 Nov 2007 20:38:11 GMT
Server Apache
X-Powered-By PHP/4.4.4
Expires Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control store, no-cache, must-revalidate, post-check=0, pre-check=0
Last-Modified Mon, 12 Nov 2007 20:38:11 GMT
Vary Accept-Encoding
Content-Encoding gzip
Content-Length 20
Connection close
Content-Type text/html; charset=utf-8

Request Headers
Host www.club-info-montrabe.net
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection close
Content-Type application/x-www-form-urlencoded
X-Requested-With XMLHttpRequest
Referer http://www.club-info-montrabe.net/?q=node/9
Content-Length 70
Cookie SESS97628db4b9f0ee49715bf53fbc9ed24e=bef14625bbcb7f762adfa880fbb5031d; SESSe0099c37a34bdb736745a9a2d06d506b=4d3697a3120cca1de100773d5b24faa0
Pragma no-cache
Cache-Control no-cache

POST : chatboxtoken 0.11935712019614764
message qsqsq
timestamp 119489708993

RESPONSE:
Loading...

POST http://www.club-info-montrabe.net/?q=chatblock/view (2078ms)

Response Headers
Date Mon, 12 Nov 2007 20:38:14 GMT
Server Apache
X-Powered-By PHP/4.4.4
Expires Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control store, no-cache, must-revalidate, post-check=0, pre-check=0
Last-Modified Mon, 12 Nov 2007 20:38:14 GMT
Vary Accept-Encoding
Content-Encoding gzip
Content-Length 20
Connection close
Content-Type text/html; charset=utf-8

Request Headers
Host www.club-info-montrabe.net
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection close
Content-Type application/x-www-form-urlencoded
X-Requested-With XMLHttpRequest
Referer http://www.club-info-montrabe.net/?q=node/9
Content-Length 56
Cookie SESS97628db4b9f0ee49715bf53fbc9ed24e=bef14625bbcb7f762adfa880fbb5031d; SESSe0099c37a34bdb736745a9a2d06d506b=4d3697a3120cca1de100773d5b24faa0
Pragma no-cache
Cache-Control no-cache

POST
chatboxtoken 0.03663093752603841
timestamp 119489708993

response:
Loading...

dwees’s picture

Status: Fixed » Postponed (maintainer needs more info)

It looks like the database update query didn't work. Did you run the upgrade script when you enabled the module again, or is this the first time you are using the module?

In any case, go into the database and change the timestamp column to be 'bigint' and a length of '14'.

Dave

plim’s picture

It was the first time.
I changed the timestamp column type as you suggered. It works fine now.

Thank you.
philippe

dwees’s picture

Status: Postponed (maintainer needs more info) » Fixed

My bad, I forgot to update the chatblock.install file to reflect my changes, hopefully this will be fixed in the fix I just committed.

Dave

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

thesoorae’s picture

Title: timestamp is allways 0 » still won't reload(timestamp okay)

hi. i looked through all the threads involving the refresh issue and i still can't seem to locate what is preventing my chatblock from automatically reloading without refreshing the browser. the database (under chatblock) is set to bigint(14), so unless i'm neglecting to do something that can't be it do you know what's going on? sorry if this is still a duplicate.

dwees’s picture

Status: Closed (fixed) » Postponed (maintainer needs more info)

Need more information, specifically:

Browser and version:

Exact Drupal version:

Clean-urls enabled:

Server set-up:

dwees’s picture

Status: Postponed (maintainer needs more info) » Fixed

This turned out to be a 'problem' with the person's theme. They were using a theme which used a different base JavaScript file other than jQuery, and my module requires jQuery and Drupal.js to be part of your theme. I'll have to include this information in the next README.txt update.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.