1.1 --- a/README.txt Tue Nov 05 22:18:45 2013 +0100
1.2 +++ b/README.txt Tue Nov 05 22:56:25 2013 +0100
1.3 @@ -16,23 +16,6 @@
1.4 See pages/HelpOnApproveChanges for the documentation for this software and how
1.5 to use it.
1.6
1.7 -Pre-Installation Tasks
1.8 -----------------------
1.9 -
1.10 -Before installing the software, create a new user who will be responsible for
1.11 -queuing untrusted changes. This user will be used by the software internally,
1.12 -and it should never be necessary to log in manually as this user to perform
1.13 -tasks.
1.14 -
1.15 -Adding a new user can be done using the moin program as follows:
1.16 -
1.17 - moin --config-dir=path-to-wikiconfig account create \
1.18 - --name=ApprovalQueueUser --email=... --password=...
1.19 -
1.20 -The ... values should be substituted with acceptable values. Beware that
1.21 -MoinMoin insists on distinct e-mail addresses. Beware also that providing a
1.22 -password on the command line can be a risk on multi-user systems.
1.23 -
1.24 Installation
1.25 ------------
1.26
1.27 @@ -107,21 +90,8 @@
1.28
1.29 Once the event handler has been installed, all page saving operations will be
1.30 affected by its operation. With no further configuration, it is most likely
1.31 -that only superusers will be able to save changes to wiki pages, and even the
1.32 -queuing of changes will not function properly.
1.33 -
1.34 -Thus, it becomes necessary to change the wiki configuration to enable the
1.35 -successful queuing of changes by changing the acl_rights_before configuration
1.36 -setting, adding the following rule:
1.37 -
1.38 - ApprovalQueueUser:write,admin
1.39 -
1.40 -This will let the special internal wiki user responsible for queuing changes
1.41 -(see "Pre-Installation Tasks") save and define an ACL on a page saved by an
1.42 -untrusted user. See the following page for more information on access control
1.43 -lists (ACLs):
1.44 -
1.45 - http://moinmo.in/HelpOnAccessControlLists
1.46 +that only superusers will be able to save changes to wiki pages, and the edits
1.47 +of all other users will be queued.
1.48
1.49 The configuration settings used by ApproveChanges are as follows:
1.50
1.51 @@ -158,24 +128,6 @@
1.52 This gives the name of the group page holding the names of reviewers. By
1.53 default, it is set to PageReviewersGroup. See "Resource Pages" above.
1.54
1.55 - queued_changes_user
1.56 - -------------------
1.57 -
1.58 - This gives the name of the user who saves unapproved changes to approval
1.59 - queues. By default, it is set to ApprovalQueueUser.
1.60 -
1.61 -Troubleshooting
1.62 ----------------
1.63 -
1.64 -When a user tries to save a page, they get the following error (or
1.65 -equivalent):
1.66 -
1.67 - You can't change ACLs on this page since you have no admin rights on it!
1.68 -
1.69 -This is possibly caused by the absence of the ApprovalQueueUser (see
1.70 -"Pre-Installation Tasks" above) and/or the acl_rights_before rule for that
1.71 -user (see "Configuration" above).
1.72 -
1.73 Recommended Software
1.74 --------------------
1.75
1.76 @@ -204,6 +156,9 @@
1.77 --------------------------------------------------------------
1.78
1.79 * Added user-specific approval queues.
1.80 + * Removed the special ApprovalQueueUser. This user can be removed from
1.81 + existing installations since the software no longer needs it to perform
1.82 + the queuing of unapproved contributions.
1.83
1.84 New in ApproveChanges 0.1.1 (Changes since ApproveChanges 0.1)
1.85 --------------------------------------------------------------