Changes between Version 29 and Version 30 of PrivateWikiPlugin


Ignore:
Timestamp:
Mar 11, 2015, 2:17:39 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes, tagged with license

Legend:

Unmodified
Added
Removed
Modified
  • PrivateWikiPlugin

    v29 v30  
    11[[PageOutline(2-5,Contents,pullout)]]
    2 = Restrict Access to sections of the Wiki =
    32
    4 == Description ==
     3= Restrict Access to sections of the Wiki
     4
     5== Description
    56
    67Allows you to protect wiki pages against access.
    78
    8 == Bugs/Feature Requests ==
     9== Bugs/Feature Requests
    910
    1011Existing bugs and feature requests for PrivateWikiPlugin are
     
    1415[/newticket?component=PrivateWikiPlugin&owner=natewlew new ticket].
    1516
    16 == Download ==
     17[[TicketQuery(component=PrivateWikiPlugin&group=type,format=progress)]]
     18
     19== Download
    1720
    1821Download the [download:privatewikiplugin zipped source], check out [/svn/privatewikiplugin using Subversion], or [source:privatewikiplugin browse the source] with Trac.
    1922
    20 = Installation Help =
    21  1. Install the plugin (either for a single project, or globally). See the details on how to install a trac plugin at: [trac:TracPlugins]
     23== Installation
     24
     25 1. Install the plugin, either for a single project or globally. See the details on how to install a trac plugin at: [trac:TracPlugins]
    2226
    2327 ''Latest Development Branch:''
     
    2529easy_install https://trac-hacks.org/svn/privatewikiplugin/trunk/
    2630 }}}
    27  2. Be sure that the plugin is enabled. Add `privatewiki.api.privatewikisystem = enabled` to trac.ini (in the [components] subheading).
    28   * Alternatively, this can be enabled in the Web Admin section of the website as well
    29  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, particular care will need to be taken to ensure the correct order. If `AuthzPolicy` is used to implement TracFineGrainedPermissions, then the order should most likely be `AuthzPolicy, PrivateWikiSystem, DefaultPermissionPolicy, LegacyAttachmentPolicy`.
     31 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.
     32 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`.
    3033
    31   Before:
     34 Before:
    3235{{{
    3336#!ini
     
    3538permission_policies = DefaultPermissionPolicy, LegacyAttachmentPolicy
    3639}}}
    37   After:
     40 After:
    3841{{{
    3942#!ini
     
    4245}}}
    4346
    44 == Use ==
     47== Usage
    4548
    46 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 _.
     49In `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 _:
    4750
    4851{{{
     
    5255}}}
    5356
    54 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.
     57Once 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.
    5558
    56 == Recent Changes ==
     59== Recent Changes
    5760
    5861[[ChangeLog(privatewikiplugin, 3)]]
    5962
    60 == Author/Contributors ==
     63== Author/Contributors
    6164
    6265'''Author:''' [wiki:eric256] [[BR]]
    63 '''Maintainer:''' [wiki:natewlew] [[BR]]
     66'''Maintainer:''' [[Maintainer]] [[BR]]
    6467'''Contributors:'''