[Zope-CMF] Howto use CMFStaging?

Tim Hoffman timhoffman@cams.wa.gov.au
16 Aug 2002 13:21:20 +0800


Hi Shane

OK, I am quite willing to give it a go.

My case I think is fairly general for publishing of content within CMF,
and I really need Versioning/Locking.

In the current cmf, I can 

1. create content
2. submit content for review
3. review content either approving, or rejecting it. 
(and obviously create other workflow variations)

and now I have published content. I have to then be able to 
allow a content author to edit the published document, b currently I
must force a retract, so that the publishing process is 
then revisited for every change (other wise someone could make
undesirable changes). But this then means the old (approved version) of
the document is no longer visible

What I want to achieve is to allow the content author to edit the
published document, but with some form of version control/locking
which means when the published document is edited, a new version is 
created which is automatically retracted, leaving the previous version 
still published and accessible.

Once the new unpublished version is approved, it becomes the new
published visible incarnation of the document.

I have no idea if CMFStaging could be used to implement such a process.

If you think this could be done, I am quite willing to build, and
document as a tutorial the required steps, code etc....

I may need some help though.

Is this requirement even feasible. I have to embark on such a solution
and if I can utilise CMFStaging all the better.

Regards

Tim Hoffman

On Fri, 2002-08-16 at 12:10, Shane Hathaway wrote:
> Tim Hoffman wrote:
> > Yep
> > 
> > Done that.
> > 
> > Apart from one email from Shane Hathaway which I have read, so I know 
> > why I want to look at CMFStaging specifically, all the other emails on
> > the topic are suitably vague.
> > 
> > Bottom line, there is very little written about CMFStaging, and the code
> > is sufficiently uncommented such that trying to work out what is going
> > on, and how things relate ain't easy.
> > 
> > Oh well, if I work out how to make it do something I shall post it here.
> 
> Sorry, CMFStaging and CMFWorkspaces work as they stand, but the process 
> of integrating them into a site is not fully determined.  Of the 
> customers that have used them so far, each has had very different 
> requirements, and the products were integrated in different ways.  So it 
> would be quite difficult to write documentation for the general case, 
> since we can't guess very well what the general case is yet.
> 
> Someone could write for a specific case, though.  I wish someone could 
> just visit F'burg to get trained on the two products, then write public 
> docs according to what they learned.  That would be grand!  Or maybe a 
> phone call would be sufficient.  Visiting would be more fun, though. :-)
> 
> Shane