Hello,
WIth Zope2, when I need to create or read a file in the filesystem, I
usually go in /myzopeinstance/var directory
and to find it is pretty easy:
import os
os.environ['CLIENT_HOME']
But in Zope3, CLIENT_HOME or INSTANCE_HOME are no longer provided in
os.environ
I had a look to different
Hi,I recently moved my webapp from z3.3.1 tarball to all eggs. It's working
great except for my
securitypolicy, which seems to sort of half-work. For example, earlier an
authenticated member
could view http://myhost/mysite/@@footest.html with and without the @@ but
now it's only viewable
with
I don't think there is any way whatsoever in Zope 3. There is no
instance home to begin with, and the os.pardir hacks don't work
either because you can't really know where your package is installed.
Stefan
On 6. Nov 2007, at 11:02, Eric Bréhault wrote:
I had a look to different source
Hi,
I'm in the process of evolving a DB and have come across an issue where
the zope.app.broken classFactory isn't being used, hence broken objects
come back as Pc
PersistentBroken rather than zope.app.broken.Broken.
The installBroken handler takes care of the logistics in monkey patching
the