What setting is needed for the Drupal caching mode? + CSS issue [#940334]

This is either a bug report a support request:

Question: what setting is needed for the Drupal caching mode (disabled, normal, agressive, external)? BTW, external is only for Pressflow.

The reason I ask is: if I set it to "normal" with Memcached enabled in settings.php, then very frequently my pages lose their CSS markup. The reference to the optimized CSS file points to a non-existing file. This means the memcache pagecache was not updated when the CSS file changed. When I flush the Drupal cache, or flush the memcache server manually, my page comes back to life.

The above does NOT happen when I set the caching mode to "disabled" - CSS is fine, but does Memcache still cache then?

I couldn't find an answer in the documentation.

Comments

Comment #1

Anonymous (not verified) commented 13 October 2010 at 11:48

Title:

Drupal caching mode & optimized CSS

» What setting is needed for the Drupal caching mode? + CSS issue

Comment #2

jeremy commented 14 October 2010 at 13:07

Status:

Active

» Postponed (maintainer needs more info)

It should work in any mode. Perhaps this is fallout from when the wildcard logic was broken for a time. Download the latest memcache.inc file from CVS and try again, does this fix your problem?

Comment #3

catch

he/him

English

commented 4 February 2011 at 08:50

Status:

Postponed (maintainer needs more info)

» Closed (works as designed)

Pretty sure this is an issue with page caching and CSS aggregates - where aggregates get deleted that are still in the page cache, this can't be fixed in memcache.inc

Comment #4

Slovak commented 1 March 2011 at 21:52

I'm experiencing the same issue... subscribing

Comment #5

mdorrell commented 21 March 2011 at 16:41

subscribing

Comment #6

js commented 22 March 2011 at 05:02

I am confused what setting "caching mode" when using memcache and pressflow.

Mine seems to be "forced" to "disabled" as it won't accept a alternative setting and I can't seem to find a reference to where that is happening.

cache_views show "set" directives, but false hits and they never seem to get "set" a second time.

Memcache appears to give me about 20% hits initially and then drops to single digits. I have tried many things, and hunted for a current recipe, but I obviously don't know what I am doing.

Any pointers would be appreciated.

Comment #7

agileware commented 23 May 2011 at 04:18

Status:

Closed (works as designed)

» Active

@catch in #3:

Can you elaborate on that comment. It isn't really descriptive enough to fully understand what the casue of the issue is.
If it can't be fixed in memcache then where?
And then is there an issue something else for the problem you have mentioned?
Or when using memcache do we just have to disable css optimization?