Package: collective - PloneStaging
a test of SfIndex product
Sourceforge Info
| Project Name: | collective |
| Package Name: | PloneStaging |
| Files Page: | |
| Browse CVS: | http://cvs.sourceforge.net/viewcvs.py/collective/PloneStaging/ |
Package README (CVS ver. 1.1)
Creator: sidnei and x3ng.br
Instigator: runyaga
Purpose: Expose ZopeVersionControl and CMFStaging into Plone interface
i.e. get proper versioning
Requires: Zope 2.6.1 or above
CMF1.3 or above
Plone 1.0 or above
cvs.zope.org/Products/ZopeVersionControl
cvs.zope.org/CMF/CMFStaging
In the root of your Zope you do not have a object with the id, plone
Documentation:
http://dev.zope.org/CVS/ZopeCVSFAQ
http://plone.org/development/current/projects/PloneStaging
Install:
In the ROOT of your ZODB (within the ZMI, not inside existing Plone site!),
add an external method with the following configuration values:
o id: install_staging
o title (optional): Install PloneStaging
o module name: PloneStaging.Install
o function name: create3SiteStage
NOTE THE FUNCTION NAME ABOVE. It's different from the regular "install"
Go to the management screen for the newly added external method and
click the 'Test' tab.
A folder called 'staging' will be created, and inside that another folder
called 'Stages' where the different Plone sites can be found.
* need to make it so /stages/Review and /stages/Production are not
traversable/modifiable by non-Managers. The only way objects get to
be in those areas is via CMFStaging tool/slot and Workflow.
* if you change the ID of a object after its been staged.. confusion ensues
Q: How do you version many objects? by doing a folder and all objects "below"?
I think we can use the plone infrastructure as management.
Q: What happens if you retract something and its the only version in the
repository
for the public website?