Mercurial > p > roundup > code
diff doc/upgrading.txt @ 2270:3cdefcb2b7d2 maint-0.7
have roundup server pass though the cause of a "403 Forbidden" response
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Sun, 09 May 2004 23:41:13 +0000 |
| parents | d22a40dd33af |
| children | c0e86056739f f72d2fb8ef78 |
line wrap: on
line diff
--- a/doc/upgrading.txt Fri May 07 00:48:08 2004 +0000 +++ b/doc/upgrading.txt Sun May 09 23:41:13 2004 +0000 @@ -6,8 +6,40 @@ accordingly. Note that there is information about upgrade procedures in the `administration guide`_. +If a specific version transition isn't mentioned here (eg. 0.6.7 to 0.6.8) +then you don't need to do anything. If you're upgrading from 0.5.6 to +0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3" +steps. + .. contents:: +Migrating from 0.7.0 to 0.7.1 +============================= + +0.7.1 Permission assignments +---------------------------- + +If you allow anonymous access to your tracker, you might need to assign +some additional View (or Edit if your tracker is that open) permissions +to the "anonymous" user. To do so, find the code in your ``dbinit.py`` that +says:: + + for cl in 'issue', 'file', 'msg', 'query', 'keyword': + p = db.security.getPermission('View', cl) + db.security.addPermissionToRole('User', p) + p = db.security.getPermission('Edit', cl) + db.security.addPermissionToRole('User', p) + for cl in 'priority', 'status': + p = db.security.getPermission('View', cl) + db.security.addPermissionToRole('User', p) + +Add add a line:: + + db.security.addPermissionToRole('Anonymous', p) + +next to the existing ``'User'`` lines for the Permissions you wish to +assign to the anonymous user. + Migrating from 0.6 to 0.7 =========================
