A typical table view - based on the flag module - with one column containing the Javascript toggle to flag/unflag a node, and the other being the node title.

This works just fine when in the http://dev.sitename.com version of the site, but the Flag columns end up completely blank when dev is removed from the FQDN and the site accessed via http://sitename.com - thus turning the automagic caching layer on.

Couldn't find anything on how caching might affect flag module in the issue queues, and the way the automatic caching is coming in to play here is certainly escaping me, as are what the options might be to work around the caching.

http://dev.sitename.com/flagged - flag column populated and flags can be toggled just fine
http://sitename.com/flagged - flag column has a header, but is otherwise empty

Occurs when using the Normal link Views link type instead of the JavaScript toggle link type as well.

Is there a subset of the caching that could be turned off, or another way to turn off caching for a site (or uri) apart from having dev in the domain name?

Hmm, just noticed that the javascript flag toggles are missing on regular nodes as well, unless dev is in the FQDN, so flag module doesn't seem too happy overall without dev.

Thanks ever,

mysty

--
# cat /var/aegir/config/includes/barracuda_log.txt
Mon Apr 11 13:23:31 BST 2011 / Debian.lenny i686 / Aegir 1.0-boa-T-5 / Barracuda 1.0-boa-T-5 / Nginx 0.9.5 / PHP 5.2.17

.. yes, I know this needs updating.

Comments

omega8cc’s picture

omega8cc commented

This can be also related to the cache (redis+memcached) and not speed booster cache, so you may want to debug this by disabling the cache integration for this site, like in this example: http://drupalcode.org/project/barracuda.git/blob/HEAD:/aegir/conf/overri...

If this doesn't work, you can put in the /data/conf/override.global.inc file something like:

// disable Speed Booster for listed domains
if (isset($_SERVER['HTTP_HOST']) && preg_match("/(?:domain\.com|another-domain\.com)/", $_SERVER['HTTP_HOST'])) {
  header('X-Accel-Expires: 0'); // do not cache it on the Nginx level
}

However this will work only with recent stable, so you should upgrade first.

It will work like it works on the "dev" subdomain, yet, the issue is still interesting, anyway.

omega8cc’s picture

omega8cc commented
Status: Active » Closed (cannot reproduce)

Closed because of lack of feedback.

Please re-open if there will be more info available.