While a Version is active, a line beneath the current object identifier (the icon and path to the object presented in the workspace) will indicate that a Version is active and give the Zope path to the active Version. If there is no active Version, nothing is displayed. While a version is active, objects that are modified in the Version will be marked with a small red diamond following their title and id in a folders contents. A Folder containing items which have been changed in a Version is shown in Figure 45 .
![]() |
To ensure safety, when an object is modified in a Version it becomes "locked" outside of the version. Another user will not be able to modify that object until the changes in the Version have been committed. This helps to prevent conflicts when the between Versions.
Take the following scenario with a folder (Folder1), containing two DMTL Methods (Document1and Document2) with an active Version (Version1). If the user in Version1 deletes Document1 in Folder1, Folder1 and Document1 cannot be modified outside of the Version. That is, no additions or deletions of objects inside of Folder1 is allowed, and Document1's source cannot be changed from the state it was in at time of deletion. Document2, however, has been untouched inside of Version1 and is editable by users not in Version1.
It is important to remember that even though Document2 is editable outside of Version1, it cannot be deleted. Once Version1's changes are committed to the system, Folder1 is usable by others again. When working is Versions, it is a good idea to plan and organize ahead to make sure it does not conflict with other users of the system.
To ensure further safety, the Undo list in an active version only allows actions to be undone that were done inside the version. This prevents version users from accidentally undoing an action that would affect the outside site and possibly the changes occurring within the version.
Previous Chapter | Next Chapter | Up | Next Section | Contents