Changes between Version 12 and Version 13 of TicketAccessPlugin
- Timestamp:
- Dec 15, 2015, 2:48:21 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TicketAccessPlugin
v12 v13 23 23 == Source 24 24 25 You can browse TicketAccessPlugin from [svn://svn.code.sf.net/p/ticketaccess/code-0 here] 25 You can browse TicketAccessPlugin from [svn://svn.code.sf.net/p/ticketaccess/code-0 here]. 26 26 27 27 == Installation 28 28 29 29 After downloading and installing, you will need to enable it in the Trac admin page. 30 You will have to do an upgrade of your Trac database. 30 You will have to perform an upgrade of your Trac database: 31 {{{#!sh 32 trac-admin /instance_trac/ upgrade 33 }}} 31 34 32 Changes are also needed in the `trac.ini` file: 33 34 Under the `trac` subsection, please add the permission policy '''!TicketAccessPolicy''' to the beginning of the permission_policies item: 35 Changes are also needed in the `trac.ini` file. Under the `trac` subsection, please add the permission policy '''!TicketAccessPolicy''' to the beginning of the permission_policies item: 35 36 36 37 {{{#!ini … … 59 60 And then the ticket will be hidden from users in these 2 groups. 60 61 61 In our example, only users from grpB (user1 and user3) are allowed to see the ticket. However user1 has already been restricted due to him belonging to grpA, so in effect, only user3 has access to the ticket.62 In our example, only users from grpB (user1 and user3) are allowed to see the ticket. However, user1 has already been restricted due to him belonging to grpA, so in effect, only user3 has access to the ticket. 62 63 63 Note that if a user has `TRAC_ADMIN` permissions then he will be allowed full accessregardless of the restrictions imposed by the plugin.64 Note that if a user has `TRAC_ADMIN` permissions, then this user will be allowed full access, regardless of the restrictions imposed by the plugin. 64 65 65 66 == Author/Contributors