Hello,
Design question, is it considered bad practice to include a meta.zcml
from a configure.zcml file ?
e.g Package A depends on package B
My package A requires some meta defined in package B before loading
configure of package B so I do in configure.zcml of package A:
http://namespace
I am building a platform where I want to initialize the ZODB (that will
be running under Zope) with three folders with sitemanagers.
If I use Folders like this:
if 'AR' not in root['Application']:
root['Application']['AR']=folder.Folder()
sm = LocalSiteManager(root['Application']['AR'])
BTreeContainer doesn't support site managers.
Folder is a subclass of SiteManagerContainer which is a subclass of
BTreeContainer.
You can happily use Folder here.
With regards,
- Shailesh
On 7/8/08, Tim Cook <[EMAIL PROTECTED]> wrote:
>
> I am building a platform where I want to initialize th
On Tue, 2008-07-08 at 09:31 -0700, Shailesh Kumar wrote:
> BTreeContainer doesn't support site managers.
>
> Folder is a subclass of SiteManagerContainer which is a subclass of
> BTreeContainer.
>
> You can happily use Folder here.
>
Thanks. I hadn't noticed that. In the earlier days of Z
I have a project that is based on zopeproject.
There are several people working on translations on this domain via
Launchpad translation services.
The project is in a directory called oship. I have initially put the
translations in a directory:
oship/src/oship/locales
But I was wondering if
Hi All,
I've got a web application that uses pluggable authentication, but I
don't want the overhead of authentication for public resources like CSS,
javascript, images, etc. Is it possible to just disable authentication
for a given resource ? I tried just setting the permission to zope.View,
but
Did you try the resourceDirecotry ZCML directive?
that way they don't need the authentication overhead.
On 7/8/08, andrew <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> I've got a web application that uses pluggable authentication, but I
> don't want the overhead of authentication for public resou
