Very helpful, I have a ZClass that inherits a ZClass, a decision I wish I could have taken back, but it works, a little screwy override behavior, but it works.

Sounds like, you don't use a classic dev-staging-production cycle... I've been spoiled by editing anything, anywhere, during my dev & beta cycles... as I move to production, I had thought I might move to a staging-production cycle... but you're making me think that Zope in production, is as different, as Zope every other way. Perhaps an incremental backup strategy could replace staging-production in my plan.

Just checking my options for production strategies, before roll-out....

Thanks for your advice,

-Jon Cyr
cyrj@cyr.info

Dieter Maurer wrote:

Jonathan Cyr wrote at 2004-8-2 15:20 -0400:

I'm planning to use the Distribute function of the ZClass to move them 
to my ZEO setup, eliiminating the possibility of editing them in production.


There is a known problem that you cannot import (and therefore distribute)
products with ZClasses that use other ZClasses defined in a
different product.

Are there any known problems with the Distribution mechanism...


I only played with the distribution mechanism -- never used
it in earnest -- because I do want to be able to edit
anything anywhere (where it is necessary -- especially in production).