[Zope-CMF] Staging content

Mark Gibson mark@dimensional.com
Tue, 11 Feb 2003 10:06:57 -0700

Dieter Maurer wrote:

>   workflow states	outgoing transistions
>     new			publish, becomeRevision
>     published		revise
>     underRevision	cancelRevision
>     isRevision		cancelRevision, publish
>   transitions		destination state
>     publish		published
>     revise		underRevision
>     cancelRevision	published
>     becomeRevision	isRevision
> "revise", "cancelRevision" and "publish" have associated scripts
> which perform the create/remove/store the revision copy.
> The copy is stored in the "Revision" attribute of revised object.
> "becomeRevision" is an automatic transistion which fires when
> the object has a parent and it is the "Revision" attribute of the
> parent.

I can't follow your last sentence above.  When is "becomeRevision" fired,
and for which objects?   Does this have to do with folderish objects?

So, you store revisions of an object as a property of that object?  If 
you can make sense of my diagram:

   Object  Attributes:
        -> title
        -> body
        -> body_type

        -> Revision    Attributes:
                    -> title
                    -> body
                    -> body_type

What about Folderish Object?  Do you just clone the folder and it's 
contents, and make it the Revision attribute of the revised object?