Change comment:
Document converted from syntax xwiki/1.0 to syntax xwiki/2.0
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.S ergiu1 +XWiki.SilviaRusu - Syntax
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki 1.01 +XWiki 2.0 - Content
-
... ... @@ -1,22 +1,24 @@ 1 - 1Version Control1 += Version Control = 2 2 3 3 Any change made to a document is saved under Version Control. You can see the version of a document by looking at the bottom of the document. For example, on the following document the version is 5.4 and has last been modified by "Sergiu": 4 4 5 - {image:versioncontrol1.png}5 +image:versioncontrol1.png 6 6 7 -As the image shows, the document version consists of two numbers, separated by a dot: <tt><Major>.<Minor></tt>. The XWiki versioning system allows the distinction between major and minor edits. When [editing a page>Features.PageEditing], the user has the option to decide whether his edit brings major or minor changes to the document. Saving a major version will increase the first component and reset the second to "1", while a minor version will just increase the second component. 7 +As the image shows, the document version consists of two numbers, separated by a dot: {{html clean="false" wiki="true"}}<tt><Major>.<Minor></tt>{{/html}}. The XWiki versioning system allows the distinction between major and minor edits. When [[editing a page>>Features.PageEditing]], the user has the option to decide whether his edit brings major or minor changes to the document. Saving a major version will increase the first component and reset the second to "1", while a minor version will just increase the second component. 8 8 9 9 Clicking on the "History" button when viewing a page displays all the versions that were previously saved: 10 10 11 - {image:versioncontrol2.png}11 +image:versioncontrol2.png 12 12 13 13 Besides listing the document versions, the history page can be used to perform other actions as well: 14 -- compare any two versions 15 -- set an older version as the current version (restore); available only if the user has edit rights on the document 16 -- delete a version completely from the history (useful for removing spam, for example); available only if the user has administration rights 17 17 15 +(% style="list-style-type: square" %) 16 +* compare any two versions 17 +* set an older version as the current version (restore); available only if the user has edit rights on the document 18 +* delete a version completely from the history (useful for removing spam, for example); available only if the user has administration rights 19 + 18 18 By default, minor edits do not appear in the document history. The option "Show minor edits" will list all the versions, including minor ones. 19 19 20 20 Comparing 2 versions highlights the differences between them, grouped by what part of the document they affect: the content, metadata, attachments, comments, objects, class definition: 21 21 22 - {image:versioncontrol3.png}24 +image:versioncontrol3.png
- XWiki.XWikiComments[2]
-
- Date
-
... ... @@ -1,1 +1,1 @@ 1 -2009-07-18 15:05:53. 9981 +2009-07-18 15:05:53.0
- XWiki.XWikiComments[3]
-
- Comment
-
... ... @@ -1,5 +1,5 @@ 1 -The right place to ask questions is the [mailing list>dev:Community.MailingLists], that's why comments are rarely answered. 1 +The right place to ask questions is the [[mailing list>>dev:Community.MailingLists]], that's why comments are rarely answered. 2 2 3 -Yes, it is possible to plug in another versioning storage, but you need to implement it, since right now only the default one is provided. You would need to implement the com.xpn.xwiki.store.XWikiVersioningStoreInterface interface, and configure your implementation in WEB-INF/xwiki.cfg. If you don't need to actually replace the version storage, but just to push changes to a VCS, you can instead use the [notification mechanism>DevGuide.Notifications] to catch all document save actions and push the new version to the VCS. 3 +Yes, it is possible to plug in another versioning storage, but you need to implement it, since right now only the default one is provided. You would need to implement the com.xpn.xwiki.store.XWikiVersioningStoreInterface interface, and configure your implementation in WEB-INF/xwiki.cfg. If you don't need to actually replace the version storage, but just to push changes to a VCS, you can instead use the [[notification mechanism>>DevGuide.Notifications]] to catch all document save actions and push the new version to the VCS. 4 4 5 5 Please use the mailing list for further questions. - Date
-
... ... @@ -1,1 +1,1 @@ 1 -2009-07-18 15:21:48. 4861 +2009-07-18 15:21:48.0