Personal tools
You are here: Home Lists ZPUG DC List Archives 2005 2005-04 the secrets of minimizing the ZODB aka flushing cache- how to let a subsidiary Plone admin handle this? / Christoph Berendes <berendes@netalyst.com>
Navigation
Log in


Forgot your password?
New user?
Mailing Lists
You can read our ZPUGDC mailing list archives online.
You can subscribe to our mailing list:
Book Review

The Definitive Guide to Plone

Reviewer: joel
 

the secrets of minimizing the ZODB aka flushing cache- how to let a subsidiary Plone admin handle this? / Christoph Berendes <berendes@netalyst.com>

the secrets of minimizing the ZODB aka flushing cache- how to let a subsidiary Plone admin handle this?
Christoph Berendes <berendes(at)netalyst.com>
2005-04-04 13:01:01 [ FULL ]
Two questions about caching css and logo changes in a plone site - while 
experimenting with new logos or css in a Plone site in a larger Zope 
instance:

1. In spite of what a lot of documentation says, in pointing me to  * 
RAM Cache Manager*, and * Accelerated HTTP Cache Manager,  *the*** *key 
seems to be to go to the root of the Zope instance, at 
/Control_Panel/Database/main/Flush Cache -> minimize. That always does 
the trick, while setting the "time to live' in the RAM Cache or the HTTP 
cache does not a thing.

Oddly, the Zope book and the Definitive Guide seem to be silent about this.

Is this documented in any official sources? I dug it up in support 
forums on Zettai, e.g. 
http://www.zettai.net/Forums/04/1086367653/talkback/1086367552

2. Is there a way to give the admin of a subsidiary Plone site the power 
to minimize the ZODB as above (or flush the database cache in some other 
way), without giving them admin access to the entire Zope instance?

Thanks.
Attachments: 
text.html text/html - 1433 Bytes

Powered by Plone, the Open Source Content Management System

This site conforms to the following standards: