#009435: Viewcache not working correctly for different CacheDir values

Description:

Assume view caching is on. The expected behavior would be that a cached node which is changed in the admin interface is removed from the cache and regenerated on first access.

However, if I use different settings for CacheDir ([FileSettings]) for the site access "example" and "example_admin", then publishing a new version of a document (using example_admin) will not remove the cached node version of "example" (since the cache directories for both site accesses are different) -- so view caching does not work as expected.

Although the documentation mentions "Note: Don't change the default setting "cache" unless you know what you are doing.", it would be helpful to explicitly mention this problem in the documentation. Or resolve it by changing the code.


Environment:

Operating System: Linux Ubuntu 6.10
PHP Version: (please be specific, like '4.4.3' or '5.1.5'): 4.4.2-1.1 Ubuntu
Database and version: Mysql 5.0.24a-9


- Attachments

No attachments for this issue.


- Comments

I agree that we probably should mention this in the documentation.

#257081 by Kristof Coomans on June 15th, 2008 [Permanent Link]

The suggested text is put in as a warning in the documentation under FileSetting in site.ini

#267142 by Geir Arne Waaler on August 26th, 2010 [Permanent Link]

- History
Properties
Type Bug
Priority Medium
Components Documentation
Misc
Affects 3.8.6
Fix Version -
Reporter Volker Mueller
Responsible Geir Arne Waaler
Status 0 Closed
Resolution Fixed
Created November 16th, 2006
Updated August 26th, 2010
Resolved August 26th, 2010
 
Navigation [Permanent Link]
Previous Issue
Back to Issues List
Next Issue: #019127
  DB Deadlocks on ezcontentobject_tree when updating subnode