news_create permission is assigned to registered
users. However, they can only submit a news items, but not approve
it. Approval requires news_admin privilege or can be set to take
-place automatically by setting the parameter ApprovalPolicy
+place automatically by setting the parameter ApprovalPolicy
to 'open'. The news privileges can be changed in /permissions/ by
the administrator on the /news/admin/index page. The needs of an
individual site, e.g. sharing the news administration duties among
@@ -192,8 +192,8 @@
The publicly accessible pages are in the root directory of the
mounted instance. The administrative pages are in /news/admin/. No
privilege check is needed in the news/admin/ directory.
-The corresponding links for Administer and Create news -item only appear for parties which possess the appropriate +
The corresponding links for Administer and Create news
+item only appear for parties which possess the appropriate
privileges. Viewers not authorized to view the index page (i.e.
parties who were denied the news_read permission) are
shown the the site-wide 'not-authorized' template.
Note, that releasing/revoking can be done for an item individually as well, following the ID# link in the second column which leads to /admin/item. On that page, a new revision can be -added. There is no UI to edit a revision; A new revision +added. There is no UI to edit a revision; A new revision must be accompanied by a revision log string to describe the changes. The /admin/item administration page shows the audit history of an item in a similar format as that of the files shown @@ -235,7 +235,7 @@