Package: plone.app.stagingbehavior
IntroductionTheIStagingSupportbehavior is used for enabling the plone.app.iterate
functionality for Dexterity content. It allows you to perform the checkout
and checkin operations to work on a copy of your original content.UsageJust use the behaviorplone.app.stagingbehavior.interfaces.IStagingSupportin your Dexterity content-type.In yourprofiles/default/types/YOURTYPE.xmladd the behavior:<?xml version="1.0"?>
<object name="example.conference.presenter" meta_type="Dexterity FTI"
   i18n:domain="example.conference" xmlns:i18n="http://xml.zope.org/namespaces/i18n">

 <!-- enabled behaviors -->
 <property name="behaviors">
     <element value="plone.app.stagingbehavior.interfaces.IStagingSupport" />
 </property>

</object>The IStagingSupport behavior just adds the referred staging support to your
content-type, but it does not enable it.You have to set the “versioning” option in the Plone types control panel
(/@@types-controlpanel) to either “Manual” or “Automatic” for activating
versioning.More InformationFor more information about how the staging works see the documentation of
plone.app.iterate and Products.CMFEdtitions:http://pypi.python.org/pypi/plone.app.iteratehttp://pypi.python.org/pypi/Products.CMFEditionsChangelog0.1 (2014-10-20)useindexinstead oftemplatefor info viewlet to allow overriding the
template with zcml registrations (sync approach with that used in
p.a.iterate)
[cewing]Fix a problem with the implementation of dexterity support at plone.app.linkintegrity,
when this behavior is used with plone.app.referenceablebehavior the delete_confirmation form
was failing because the object than is being deleted doesn’t have an intid.
With this patch the get_relations method simply returns an empty list in this case.
[jpgimenez]0.1b4 (2012-08-20)Do not display locked message to anonymous users
[mattvoss]Copy annotations from working copy to baseline checkin.
[frapell, jone]Fix KeyError when accessing previously checked in content through Acquisition
wrapperhttp://code.google.com/p/dexterity/issues/detail?id=270[anthonygerrard]Hide the ‘locked’ status message if user is anonymous
[mattvoss]0.1b3 (2011-09-24)Make sure that changes to the subjects field are carried over when the
working copy is checked in.
[swampmonkey]Fix broken dependency declaration.
[danjacka, jonstahl]0.1b2 (2011-06-16)Declare plone.app.versioningbehavior and plone.app.referenceablebehavior
as test dependencies.
[danjacka, davisagli]Declare the implicit dependency on plone.app.relationfield.
[davisagli]0.1b1 (2011-05-20)Add functional tests.
[anthonygerrard, davisagli]0.1a2 (2011-01-25)Fixed to avoid try setting values on read-only fields.
[deo]Improved documentation and usage information.
[deo]0.1a1 (2011-01-24)Renamed package to plone.app.stagingbehavior.
[deo]Made sure to fire an IAfterCheckinEvent so that the iterate
locking handler (handleCheckin) removes the lock from the
baseline object.
[deo]Added a workaround to allow the checkin operation to succeed.
Sent message to the mailing list to discuss the issue.
[deo]Fixed to only use the plone.app.stagingbehavior policy for Dexterity
content, avoiding any interference with Archetypes content.
[deo]Removed dependency to plone.relations, made some cleanups.
[jbaumann]Added creator attribute to the StagingRelationValue.
[jbaumann]Fixed AttributeError processForm in checkin.
[jbaumann]Implemented simple checkin process, which just copies all field values.
[jbaumann]Cleaned up the code a little bit.
[jbaumann]First implementation.
[jbaumann]