Closed (fixed)
Project:
Chatblock
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
30 Aug 2008 at 14:50 UTC
Updated:
5 Dec 2011 at 02:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
dwees commentedWhen you check your settings, how many messages have you set to display? It sounds like it is somehow 0.
Dave
Comment #2
dwees commentedComment #3
sbart76 commentedI 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.
Comment #4
sbart76 commentedI 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.
Comment #5
sbart76 commentedok, 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.
Comment #6
sbart76 commentedComment #7
superdiva commentedWhere does this patch script go in the chat block module?
Comment #8
superdiva commentedI 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...
Comment #9
frank pfabiganthanks a lot! that patch fixes the problem ;-)
Comment #10
scrimmage commentedyep. that's got it. thanks.
Comment #11
doitDave commentedThe issue has been solved by basic changes in the code architecture as with the latest dev. Nevertheless thanks for your input and the patch :)