Mercurial > p > roundup > code
diff doc/customizing.txt @ 3744:c07ae92cebbc
doc fix
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 09 Nov 2006 03:19:23 +0000 |
| parents | 0d561b24ceff |
| children | c3bba2c81a6f |
line wrap: on
line diff
--- a/doc/customizing.txt Thu Nov 09 03:08:22 2006 +0000 +++ b/doc/customizing.txt Thu Nov 09 03:19:23 2006 +0000 @@ -2,7 +2,7 @@ Customising Roundup =================== -:Version: $Revision: 1.209 $ +:Version: $Revision: 1.210 $ .. This document borrows from the ZopeBook section on ZPT. The original is at: http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx @@ -1040,13 +1040,14 @@ - they're *anonymous*. **automatic registration of users in the e-mail gateway** - By giving the "anonymous" user the ("Create", "user" Permission, any + By giving the "anonymous" user the ("Create", "user") Permission, any unidentified user will automatically be registered with the tracker (with no password, so they won't be able to log in through - the web until an admin sets their password). This is the default - behaviour in the tracker templates that ship with Roundup. The new user - is given the Roles list defined in the "new_email_user_roles" config - variable. + the web until an admin sets their password). By default new Roundup + trackers don't allow this as it opens them up to spam. It may be enabled + by uncommenting the appropriate addPermissionToRole in your tracker's + ``schema.py`` file. The new user is given the Roles list defined in the +"new_email_user_roles" config variable. **only developers may be assigned issues** Create a new Permission called "Fixer" for the "issue" class. Create a
