--On 15. Juni 2008 13:25:51 +0200 Andreas Jung <[EMAIL PROTECTED]> wrote:
--On 15. Juni 2008 06:16:52 -0500 Jens Vagelpohl <[EMAIL PROTECTED]> wrote:On Jun 15, 2008, at 06:09 , Andreas Jung wrote:--On 15. Juni 2008 06:04:37 -0500 Jens Vagelpohl <[EMAIL PROTECTED]> wrote:IMHO seeing some caching-related issues in exchange for enjoying a redundantly configured caching tier is a good tradeoff for the current site.The current caching makes it impossible to edit anything on zope.org in a reasonable way.I have always been able to work with it using force-reload where necessary, using Camino or Firefox. I know some other browsers like Safari don't seem to be able to send a real force-reload, so I gave up on those for zope.org editing work. I have to admit I have not done any editing work after this move, but I have been able to log in and get to folder content views etc with all logged-in options intact and visible. If you are using a suitable browser that can issue "real" forced reloads and you still see a problem let us know, David (or some other ZC SA) will have to look into it then.I am always using suitable tools :-) Using Firefox here. I am logged in as ajung. <http://zope.org/Products/Zope/2.11.0> shows up with all Plohn edit options. <http://zope.org/Products/Zope/2.10.6/> does not. Even worser: wget "http://zope.org/Products/Zope/2.11.0/folder_contents"; returns the page from the cache rendered within _my_ user context. That's totally broken :-)
What is the current status of this issue? It can not be that personalized content (of authenticated users) is being cached and delivered to the outside world. I still can not do anything on zope.org :->
Andreas
pgphenAMkisHS.pgp
Description: PGP signature
_______________________________________________ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
