On Tue, 8 May 2001, Jeff wrote:
> I have created a product with a zclass that contains a zclass; classA contains
>classB.
[...]
> Now for the part I don't understand.
> I have a page where I would like dynamically display a classB object. I used the
>following:
>
>
>
> Where 'index_objec
I'm trying to upload a .zexp to a product release ("Add Product Release")
and it's not working. The export is only 57k, but all I get is zope.org not
responding...
Any hints? Should I upload something other than a zexp?
Richard
--
Richard Jones
[EMAIL PROTECTED]
Senior Software Developer,
Hi ya'll,
I have created a product with a zclass that
contains a zclass; classA contains classB.
Both use 'Folder' as bases class.
I want the classB objects to have a 'default
rendering' capability so I added a DTML Method named index_html to classB with
the following code:
Where 'tem
Just a quick thought - It'd be useful to be able to see what is on
your 'clipboard' when you're copyandpasting. Would it be a Bad Thing
to factor out the first bit of OFS.CopySupport.manage_pasteObjects into a
separate function, which is callable TTW? You could then iterate over
the objects on t
> "AB" == Anthony Baxter <[EMAIL PROTECTED]> writes:
AB> Any known gotchas with running ZEO server and ZEO client on
AB> boxes of different endianness? e.g. the server running on sun
AB> solaris/sparc, while the clients are on x86 linux boxes.
AB> I'd expect it to be fine, but am fee
Any known gotchas with running ZEO server and ZEO client on boxes of
different endianness? e.g. the server running on sun solaris/sparc,
while the clients are on x86 linux boxes.
I'd expect it to be fine, but am feeling paranoid...
ta,
Anthony.
___
Z
Here Chris, I'll try to solve your pain (untested):
from AccessControl import ModuleSecurityInfo
ModuleSecurityInfo('Products').declarePublic('Catalog')
ModuleSecurityInfo('Products.Catalog').declarePublic('CatalogError')
It's not so bad.
- C
- Original Message -
From: "Chris Withers"
Evan Simpson wrote:
>
> Use the same security process as providing access to anything Zope doesn't
> already expose.
Wgh! :~(
> We should expose exceptions like this by default, but we
> haven't yet. Sorry.
No worries, where should I be looking to implement this? Woudl a patch eb likely
