Changes between Version 30 and Version 31 of PrivateWikiPlugin

Timestamp:

Nov 6, 2015, 3:18:46 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

PrivateWikiPlugin

@@ -5 +5 @@
 == Description
 
-Allows you to protect wiki pages against access.
+This plugin allows you to protect wiki pages against access.
 
 == Bugs/Feature Requests
 
 Existing bugs and feature requests for PrivateWikiPlugin are 
-[query:?status=new&status=assigned&status=reopened&group=&component=PrivateWikiPlugin&order=priority here].
+[report:9?COMPONENT=PrivateWikiPlugin here].
 
 If you have any issues, create a 
-[/newticket?component=PrivateWikiPlugin&owner=natewlew new ticket].
+[/newticket?component=PrivateWikiPlugin new ticket].
 
 [[TicketQuery(component=PrivateWikiPlugin&group=type,format=progress)]]
@@ -19 +19 @@
 == Download
 
-Download the [download:privatewikiplugin zipped source], check out [/svn/privatewikiplugin using Subversion], or [source:privatewikiplugin browse the source] with Trac.
+Download the zipped source from [export:privatewikiplugin here].
+
+== Source
+
+Check out [/svn/privatewikiplugin using Subversion], or [source:privatewikiplugin browse the source] with Trac.
 
 == Installation
 
- 1. Install the plugin, either for a single project or globally. See the details on how to install a trac plugin at: [trac:TracPlugins]
-
- ''Latest Development Branch:''
+ 1. Install the plugin, either for a single project or globally. See the details on how to install a trac plugin at [trac:TracPlugins]. For the latest development branch:
  {{{#!sh
 easy_install https://trac-hacks.org/svn/privatewikiplugin/trunk/
- }}}
- 2. Be sure that the plugin is enabled: add `privatewiki.api.privatewikisystem = enabled` to `trac.ini` (in the `[components]` subheading). Alternatively, this can be enabled in the Web Admin section of your Trac installation.
- 3. In `trac.ini` modify the `permission_policies` to include `PrivateWikiSystem` before the default entries (order is important!). If permission policies from other plugins are used, care will need to be taken to ensure the correct order. If `AuthzPolicy` is used to implement TracFineGrainedPermissions, then the order is most likely `AuthzPolicy, PrivateWikiSystem, DefaultPermissionPolicy, LegacyAttachmentPolicy`.
+}}}
+ 1. Be sure that the plugin is enabled: add `privatewiki.api.privatewikisystem = enabled` to `trac.ini` in the `[components]` subheading. Alternatively, this can be enabled in the Web Admin section of your Trac installation.
+ 1. In `trac.ini` modify the `permission_policies` to include `PrivateWikiSystem` before the default entries (order is important!). If permission policies from other plugins are used, care will need to be taken to ensure the correct order. If `AuthzPolicy` is used to implement TracFineGrainedPermissions, then the order is most likely `AuthzPolicy, PrivateWikiSystem, DefaultPermissionPolicy, LegacyAttachmentPolicy`.
 
  Before:
-{{{
-#!ini
+{{{#!ini
 [trac]
 permission_policies = DefaultPermissionPolicy, LegacyAttachmentPolicy
 }}}
+
  After:
-{{{
-#!ini
+{{{#!ini
 [trac]
 permission_policies = PrivateWikiSystem, DefaultPermissionPolicy, LegacyAttachmentPolicy
@@ -49 +50 @@
 In `trac.ini` add a `privatewikis` section, under that add a private_wikis field and list the Pages that you want to protect. Enter the pages in all upper case and replace /'s with _:
 
-{{{
-#!ini
+{{{#!ini
 [privatewikis]
 private_wikis = IT,FOOBAR,FOOBAR_INFO
 }}}
 
-Once you've added this you will have some new permissions in the admin section.  For example you'll have PRIVATE_VIEW_FOO and PRIVATE_EDIT_FOO_BAR which will control which users can view or edit !FooBar and anything below it like !FooBar/Test. The downside is that this plugin sees !FooBar and Foobar as the same page so any restrictions on one will restrict the access of the other.
+Once you have added this you will have some new permissions in the admin section. For example you will have PRIVATE_VIEW_FOO and PRIVATE_EDIT_FOO_BAR which will control which users can view or edit !FooBar and anything below it like !FooBar/Test. The downside is that this plugin sees Foo'''B'''ar and Foo'''b'''ar as the same page, so any restrictions on one will restrict the access of the other.
 
 == Recent Changes