Posted by bjurk on August 30, 2008 at 2:50pm
| Project: | Chatblock |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | doitDave |
| Status: | closed (fixed) |
Issue Summary
when I refreshed my page, all the messages disappear.
I will wish that all the messages not disappear.
It 's possible
Comments
#1
When you check your settings, how many messages have you set to display? It sounds like it is somehow 0.
Dave
#2
#3
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.
#4
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.
#5
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.
#6
#7
Where does this patch script go in the chat block module?
#8
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...
#9
thanks a lot! that patch fixes the problem ;-)
#10
yep. that's got it. thanks.
#11
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 :)
#12
Automatically closed -- issue fixed for 2 weeks with no activity.