Closed (duplicate)
Project:
Memcache API and Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Oct 2010 at 10:31 UTC
Updated:
26 Apr 2011 at 07:17 UTC
Hi @all,
I just read through a lot of bug reports dealing with old contents serverd by memcache. Unfortunately this issue still seems not to be fixed with the 6.x-1.7 version.
You may easily reproduce this behavior:
You will see that all CSS an JavaScript files cannot be loaded because the page served is an old cache entry using outdated paths.
I'd appreciate if this get fixed soon, as all multilingual sites need to disable the page cache to ensure working pages.
Let me know if you have any further questions.
Thanx in advance & best regards
hctom
Comments
Comment #1
hctom... and i forgot to mention: I also tried the latest memcache.inc file from CVS... but this one also did not solve the problem :(
Comment #2
cwdcwd commentedI'm having this same issue. Anyone have any ideas?
tks
-CWD
Comment #3
catchI'm not sure this is a bug.
1. Can you reproduce this without minimum cache lifetime?
2. Is the only symptom of this the css/js - if so, you need #721400: Order JS files according to weight, don't change filenames for aggregated JS/CSS which memcache can't do much about.
Comment #4
hctom@catch:
I can confirm, that this does not occure when minimum cache lifetime is set to "none". And it only affects the aggregated CSS/JS files. So I guess we'll have to live with it right now, because the Advanced CSS/JS Aggregation states some issues with jQuery Update and jQuery UI which are also used on the site.
Thanx a lot & cheers
hctom
Comment #5
catchMarking this as duplicate of #1134242: Review cache_lifetime behaviour., I think there is something we can do there.