I'm not sure which is the culprit, but even after a user hits the X the block pops up over and over with this server config. Any idea which could be the problem? I'm looking at mem ATM but im not sure,

Comments

kevinquillen’s picture

kevinquillen commented

I've seen this before in D6. I think it was related to block cache being enabled... and possibly the JS response being cached.. or possibly a JS error where its not triggering the callback.

Are there any JS errors in Firebug?

Media Crumb’s picture

Media Crumb commented

No firebug issues with JS atm. Seems like its going to be fairly hard to pin this down with so much caching, but I was hoping maybe the dev would know.

kevinquillen’s picture

kevinquillen commented

Yeah, the most we have employed is memcache/nginx/boost and I have not seen much issue. I have not used Varnish before.

Do you see in the database when you click close on a message, does it create a new record recording the action?

Media Crumb’s picture

Media Crumb commented

I'm assuming this would be under user_alert?

I do see records in there. This leads me to believe that the cookie is not being set. Then again I know very little about programming.

Media Crumb’s picture

Media Crumb commented

Looks like it is in fact varnish. Now i just have to figure out why

kevinquillen’s picture

kevinquillen commented
Status: Active » Postponed (maintainer needs more info)

Keep me posted. I have never used Varnish, but I know it works with nginx.

kevinquillen’s picture

kevinquillen commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing due to lack of activity.