EnSimpleStaging 1.0 (Sep 05, 2006)

Removed the Public/Private Node's. Now content can be staged directly from inside a Staging Area. CompositePack works out of the box. Provides a 'offline' queue for long duration staging(s).

For additional information about this project, please visit the overview page .

Available downloads

EnSimpleStaging gzip archive

For all platforms (151kB)

Release Notes

Tested with Plone 2.5, Plone 2.1.3, Plone 2.1.2, Plone 2.1.1, Plone 2.1
State Final release
License LGPL
Release Manager Enfold Systems
With the release of EnSimpleStaging 1.0 we have learned from two (2) years of experience on how to make a useful staging system for the Plone CMS.  The staging software requires ZopeVersionControl, CMFStaging and a few other components that have been in use for several years.  We have bundled all required components into the 1.0 archive.

EnSimpleStaging simply provides users a mechanism to edit content while the public is shown the previously 'deployed' version of the stage's content.  This has been used successfully on Oxfam America and is the technology which is used in Enfold System's remote deployment mechanism, Entransit.  It has been compared to technology found in top-tier CMS vendors such as Vignette and mid-tier vendors such as Percussion.

There has been a thorough explanation of how to use EnSimpleStaging in Martin Aspell's tutorial,

Creating public websites with staging and custom skins which describes a methodology/process that Enfold Systems has used successfully to create high-traffic and flexible web content management systems with a seperate retail view.  The next step is to release the remote deployment technology, Entransit.

FUTURE: EnSimpleStaging will move away from the 'Staging Area' content type and move to an 'adapter' so that any container can become a staging area.  Removing the dependency on ZVC would also be ideal.  The book-keeping code for Add's, Update's, and Removal's of content in a stage is the most valuable part of the EnSimpleStaging system.  It should be factored out into a separate package in future versions.

Change log

Changes since 0.9.5

  • Add nonversionables to CompositePack
  • Create a 'Folder' via WEBDAV MKCOL
  • docstring for StagingArea.doInPlace()
  • And since MenuGenerator based sitemap was the last thing using relative_url, we can rip it out and stop fiddling with the catalog indexes and metadata
  • really remove MenuGenerator dependency
  • get rid of stagingarea_view.pt and it's MenuGenerator dependency
  • made 'stagePath' disappear when doing in-place staging.
    Also added a description for queueJobsByDefault field widget
  • enable queueing of deployment from the UI
  • Hide fields on the view pane
  • new icon for stages
  • Make label optional
  • Add in JS message on deploy
  • remove workspace specific folder view (revert to regular folder view)
    slight changes to the deployment view (hide 'label' entry in the form, rename 'label' column to 'ID')
  • stop requiring pluggablediscussion
  • - Move in-place thingie to a marker interface
    - Death to Interface, long live zope.interface
  • use InAndOutWidget for the content whitelist
  • stop registering the interstage reference with AT so it doesn't show up on the 'Add' menu in Plone anymore
  • many other changes ...