Well as the title says, when you enable the drupal built-in performance cache (normal mode), the shoutbox gets a bit buggy. On auto-refresh, the shouts made after the cache is turned on, does not show up even though its still there at /shoutbox

Anyone else experiencing this?

Comments

xamount’s picture

xamount
Primary language English
commented
Title: auto-resfresh does not work when drupal's performance is enabled » auto-resfresh does not work when drupal's performance cache is enabled (normal mode)

oppss, missed out the word "cache" in title

disterics’s picture

disterics commented
Assigned: Unassigned » disterics
bessonette’s picture

bessonette commented

xamount,

I use the normal caching mode in Drupal and everything seems to work okay. However, I will say that, in my experience, the auto-refresh is extremely buggy if you are using block caching. If you disable that, you should be good to go.

xamount’s picture

xamount
Primary language English
commented

block cache was disabled actually. @jbessie, do you have a link you can share with us that has shoutbox enabled and drupal caching on as well?

robloach’s picture

robloach
he/him
commented

Maybe the module should update the block via a jQuery call so that it can work when block caching is enabled.

momper’s picture

momper commented

some progress on this?
if it is like this -> the module is not usable -> i cannot disable the caching for drupal in general, because of one module ...

mstef’s picture

mstef commented

Has anyone tested on the 2.x branch?

momper’s picture

momper commented

2.x branch

i can't see what is happening, but something is wrong with anonymous users ...

i tried "cache exclude" module, but seems to be not the right solution ...
with "blockcache alter" it's clear block cache is off

most of the time the user can't see his own posting in the list after submit ...
in rare moments it seems to work ...
the other problem is: he also doesn't see the change of the list after the refresh period ...

in firebug the console says: http://xxx.info/shoutbox/js/view?shouts=15 304 Not Modified 68ms

so the request is fired in the right way ... but nothing happens ...

mstef’s picture

mstef commented
Version: 6.x-1.0 » 6.x-2.x-dev

Yea I'm seeing this now too..

I'm guessing drupal is caching the Js callback..

Any suggestions?

torgospizza’s picture

torgospizza
he/him
Primary language English
Location Portland, OR
commented

I can confirm that with JS aggregation turned on (we're using Drupal Commons) the Shoutbox breaks. When I say "breaks" I mean I get a WSOD, with no markup at all - even with error reporting turned on. I'm still digging in to see what's happening.

mstef’s picture

mstef commented

@torgosPizza: That's a different issue all together though. You're talking about JS aggregation causing a WSOD. This issue is about the drupal cache causing auto-refresh to not return new shouts. What version are you using (shoutbox and commons)?

I'm using Commons 1.3-dev which includes Shoutbox 2.4 and JS aggregation causes no problems for me. Are you sure that turning JS aggregation off fixes the WSOD?

torgospizza’s picture

torgospizza
he/him
Primary language English
Location Portland, OR
commented

Ah, sorry. Didn't mean to derail the thread. Yes, JS aggregation being turned off fixes this issue, however on the "main" page of Commons, it works fine - when I go to a "Group" page, submitting the Shoutbox causes a WSOD. I haven't gotten to investigate further, but when I can I'll create a new Issue. My bad!

vitalblue’s picture

vitalblue commented
Issue summary: View changes
Status: Active » Closed (outdated)