when I refreshed my page, all the messages disappear.
I will wish that all the messages not disappear.
It 's possible

Comments

dwees’s picture

When you check your settings, how many messages have you set to display? It sounds like it is somehow 0.

Dave

dwees’s picture

Assigned: Unassigned » dwees
Status: Active » Postponed (maintainer needs more info)
sbart76’s picture

I have similar issue here. It was working fine until I tried to add Aggregator block and start cron jobs. I am not sure which one of those operations was the cause, but now the chatblock doesn't display previous messages if the page gets refreshed. My setting show that it should display 100 messages (default value), I tried to change this for something else - but it didn't help at all.

sbart76’s picture

Version: 5.x-1.0.x-dev » 6.x-1.x-dev

I have similar issue here. It was working fine until I tried to add Aggregator block and start cron jobs. I am not sure which one of those operations was the cause, but now the chatblock doesn't display previous messages if the page gets refreshed. My setting show that it should display 100 messages (default value), I tried to change this for something else - but it didn't help at all.

sbart76’s picture

StatusFileSize
new1.11 KB

ok, looks like it's solved. The problem in my case was trivial - as soon as I turned on cron jobs, chatblock removed old archived messages, which in turn caused the mysql query (the LIMIT part to be precise) to fail... Anyway, here's the patch.

sbart76’s picture

Status: Postponed (maintainer needs more info) » Needs review
superdiva’s picture

Where does this patch script go in the chat block module?

superdiva’s picture

I applied your patch using the GnuWin32 program and it fixed the problem!!

For any beginner drupal users with little coding experience who don't know how to apply a patch, use this link for the module you're patching ======>

http://indiawebsearch.com/content/how-to-apply-a-patch-to-a-drupal-modul...

frank pfabigan’s picture

thanks a lot! that patch fixes the problem ;-)

scrimmage’s picture

yep. that's got it. thanks.

doitDave’s picture

Assigned: dwees » doitDave
Status: Needs review » Fixed

The issue has been solved by basic changes in the code architecture as with the latest dev. Nevertheless thanks for your input and the patch :)

Status: Fixed » Closed (fixed)

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