Mercurial > p > roundup > code
diff doc/customizing.txt @ 3121:bdd31aaf556e
tweak
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Fri, 28 Jan 2005 04:30:17 +0000 |
| parents | 460eb0209a9e |
| children | 6e8eb05435cf |
line wrap: on
line diff
--- a/doc/customizing.txt Fri Jan 28 04:07:58 2005 +0000 +++ b/doc/customizing.txt Fri Jan 28 04:30:17 2005 +0000 @@ -2,7 +2,7 @@ Customising Roundup =================== -:Version: $Revision: 1.166 $ +:Version: $Revision: 1.167 $ .. This document borrows from the ZopeBook section on ZPT. The original is at: http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx @@ -3943,6 +3943,7 @@ So now, if an edit action attempts to set "assignedto" to a user that doesn't have the "Fixer" Permission, the error will be raised. + Users may only edit their issues ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -3950,13 +3951,14 @@ have access to edit the issues they submit, but not others. We create a new Role called "Provisional User" which is granted to newly-registered users, and has limited access. One of the Permissions they have is the new "Edit -Own" on issues (regular users have "Edit".) We back up the permissions with -an auditor. +Own" on issues (regular users have "Edit".) First up, we create the new Role and Permission structure in ``schema.py``:: + # # New users not approved by the admin + # db.security.addRole(name='Provisional User', description='New user registered via web or email') @@ -3975,11 +3977,11 @@ # Assign the Permissions for issue-related classes for cl in 'file', 'msg', 'query', 'keyword': - db.security.addPermissionToRole('User', 'View', cl) - db.security.addPermissionToRole('User', 'Edit', cl) - db.security.addPermissionToRole('User', 'Create', cl) + db.security.addPermissionToRole('Provisional User', 'View', cl) + db.security.addPermissionToRole('Provisional User', 'Edit', cl) + db.security.addPermissionToRole('Provisional User', 'Create', cl) for cl in 'priority', 'status': - db.security.addPermissionToRole('User', 'View', cl) + db.security.addPermissionToRole('Provisional User', 'View', cl) # and give the new users access to the web and email interface db.security.addPermissionToRole('Provisional User', 'Web Access') @@ -3994,19 +3996,6 @@ new_web_user_roles = 'Provisional User' new_email_user_roles = 'Provisional User' -Note that some older trackers might also want to change the ``page.html`` -template as follows:: - - <p class="classblock" - - tal:condition="python:request.user.username != 'anonymous'"> - + tal:condition="python:request.user.hasPermission('View', 'user')"> - <b>Administration</b><br> - <tal:block tal:condition="python:request.user.hasPermission('Edit', None)"> - <a href="home?:template=classlist">Class List</a><br> - -(note that the "-" indicates a removed line, and the "+" indicates an added -line). - Changes to the Web User Interface --------------------------------- @@ -4167,6 +4156,7 @@ </tal:block> </table> + Setting up a "wizard" (or "druid") for controlled adding of issues ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
