Personal tools
You are here: Home Documentation Manuals Plone 3.0 User Manual Managing Content Working Copy
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

3.9. Working Copy

Up one level
Working Copy lets you have two versions of your content in parallel.


When a Plone site is first created, there a number of additional features that can be enabled, including "Working Copy". If the Plone site you are using doesn't show the "Check out" option under the Actions menu, you will need to contact your site manager and request that "Working Copy Support (Iterate)" be installed.

Overview

You might have been in a situation like this before: you have published a document, and you need to update it extensively, but you want the old version to exist on the web site until you have published the new one. You also want the new document to replace the current one, but you'd like to keep the history of the old one, just in case. Working copy makes all this possible.

Essentially, you "check out" a version of the currently published document, which creates a "working copy" of the document. You then edit the working copy (for as long as you like) and when you're ready for the new version to go live, you "check in" your working copy, and it's live. Behind the scenes, Plone will replace the original document with the new one in the exact same location and web address — and archive the old version as part of the document's version history.

 

Using "Check out"

First, navigate to the page you want check out. Then from the "Actions" drop-down menu, select "Check out":

Next you will be prompted to select the folder in which the "working copy" should be placed -- this will be the version you edit. In this example, we'll choose the Home folder which is the user's own personal folder:

Then click on "Check out". Your current location is automatically updated to the working copy:



Now you're free to edit your own local copy of a published document. During this time,  the original document is "locked" -- that is, no one else can edit that published version while you have a working copy checked out. This will prevent other changes from being made to (and subsequently lost from) the published version while you edit your copy.

Using "Check in"

When you are ready to have your edited copy replace the published one, simply choose "Check-in" from the "Actions" drop-down menu:

You will then be prompted to enter a Check-in message. Fill it out and click on "Check in":

Your updated document will now replace the published copy and become the new published copy. You will also notice that your location has been updated to the location of the original document

You will also notice that there is no longer a copy of the document in the user's personal folder.

Note that it is not necessary (and in fact, it is not recommended) to use the "State" drop-down menu on a working copy. If you inadvertently do so, however, don't panic. Just go back to your working copy and use "Check in" from the "Actions" menu.

Canceling a "Check out"

If for any reason it becomes necessary to cancel a check out and you don't want to save any of your changes, simply navigate to the working copy and select "Cancel check-out":

You will prompted to confirm the "Cancel checkout" or to "Keep checkout":

Note that if the user who has checked out a working copy is not available to check in or cancel a check out, users with the Manager role may navigate to the working copy and perform either the check in or cancel check out actions.

 

by Darci Hanning last modified September 25, 2007 - 23:56
Contributors: JoAnna Springsteen, Martin Aspeli, Jon Baldivieso, Andrew Burkhalter, Sam Knox, Jon Stahl, Jeff Pittman, Esther Schindler, Rob Stevenson, Darci Hanning
All content is copyright Plone Foundation and the individual contributors.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by