|
ConcurrentEditing<< Page Keywords | Cookbook-V1 | My PmWiki >> Note: The recipes here are for PmWiki versions 0.6 and 1.0 only. For PmWiki 2.0 recipes, see Cookbook.
DescriptionThis module changes the way PmWiki handles concurrent or simultaneous editing of wiki pages. It checks whether a page has been changed by other authors while somebody was editing it and allows that user to accept or decline unexpected changes. InstallationSimply copy include_once('local/concur.php');
Note that this module replaces standard 'edit' action, what may lead to problems with other modules which do the same thing. It is recommended to add following lines into your skin .css-file: #concurrent { border: 1px dotted gray; margin-top: 5px; margin-bottom: 5px; }
#concurrent .concurtitle { background: #F0F0F0; display: block; font-size: x-small; }
UsageUnder normal editing, you won't notice any changes from the standard 'edit' action. Concurrent editing typically occurs very rarely, except in some Intranet applications. However, if someone else has made changes to the page since you began editing it, the edit process will be different. Firstly, after pressing the 'Save' button, you'll notice that you're still in the edit mode. A message will be presented to you indicated that page text has been changed. And the worst - your text will be all messed up :) But don't panic. The markup you see added to the page text is designed to prevent any damage to either version of the page. Both versions are merged into one and marked by visible separators. At this point you need to remember what you have done to the original text and what you have not. There are three types of markup. The first is for added text: -ce-a---------------------------------- added:
This text was written by you or existed originally.
-ce-f-----------------------------------------
That means that you submitted text that wasn't in the page version that another person had submitted. There are two possibilities:
After reviewing a fragment and probably deleting inner text, separators should be deleted also. They take the whole line, so the deletion procedure should not be too hard. If you leave separators in the final version (for example, when you click 'Save' button twice, ignoring the warning message), somebody else may finish fixing the page later. There are two other markups that the merge function produces. Let's review what can cause them: -ce-a-------------------------------- deleted:
%color=red%This text may have been written by someone else!
-ce-f-----------------------------------------
-ce-c--------------------------- changed from:
This text is not yet modified.
-ce-t------------------------------------- to:
This text has now been modified.
-ce-f-----------------------------------------
ConfigurationThere is not much to configure. Actually you can't change anything but i18n strings and two variables that don't really need tuning. Variables
InternationalizationSeveral strings in default values are made i18nable, and some of those strings interfer with the standard ones. I think this is not critical because the meaning is the same. The strings are:
HistoryOct 29, 2004
Comments & BugsIt'd be great to have variables for the markup that appears, so the rather cryptic tags (e.g. AuthorI'm Ilya Zverev, you can mail to
|