Package: collective - ArchiveStorage
A storage for holding a old version of an specified fields of an object.
a test of SfIndex product
Sourceforge Info
| Project Name: | collective |
| Package Name: | ArchiveStorage |
| Files Page: | |
| Browse CVS: | http://cvs.sourceforge.net/viewcvs.py/collective/ArchiveStorage/ |
Package README (CVS ver. 1.1.1.1)
About ArchiveStorage is a storage for holding a old version of an specified fields of an object. Additionally it works as sort of review storage and stores an working copy for editing while the object can be published (using the published version). On new publication the working copy will be copies to the archive and into the public copy which will be used for displaying to anonymous users. It's implemented as Archetype storage layer which stores the working copy in some subobject and the archive as list of (old) working copies in an archive subobject. So actually it's field based and you can define per field whether it's versioned by ArchiveStorage or not. AArticle shows an example with an example skin which shows how to use the archive actually. There's also a portal policy included which registers with Plone. If you want to use ArchiveStorage based objects then go to portal_migration and select the setup tab to apply the ArchiveStorage policy. Make sure not to select this on portal creation as this will not work. First create your Plone Site and then apply it. It will add a new workflow "archive_plone_workflow" which is based on the default plone workflow but allows a publish transition also when being in the published state (as you have a working copy there's no need to retract the object first for editing). Moreover it adds a script which is called after the publish transition which does the actual publication of the object (copies the working copy to the archive and into the public copy). Issues does not work yet with TextFields (never used them yet..) as they're objects which makes problem at the moment (there's a deepcopy somewhere which does not work on acquisition objects and somehow also not without.. also there might be more issues with that) Dependencies Zope 2.x Archetypes 1.0 or later Plone 2.x or later Author Written by Christian Scholz (cs@comlounge.net) in 2003-2004. History created in second half of 2003 as client work. put into public cvs in Feb 2004.