Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 2136:ee3cf6a44f29
queries on a per-user basis, and public queries [SF#891798] :)
EditAction was confused about who "self" was
Edit collision detection was broken for index-page edits
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Fri, 26 Mar 2004 04:50:51 +0000 |
| parents | fd5459469069 |
| children | f76d1642014a |
comparison
equal
deleted
inserted
replaced
| 2135:89f42bddeaee | 2136:ee3cf6a44f29 |
|---|---|
| 7 `administration guide`_. | 7 `administration guide`_. |
| 8 | 8 |
| 9 .. contents:: | 9 .. contents:: |
| 10 | 10 |
| 11 | 11 |
| 12 | |
| 13 Migrating from 0.7 to 0.8 | |
| 14 ========================= | |
| 15 | |
| 16 0.8.0 Added Dispatcher role | |
| 17 --------------------------- | |
| 18 | |
| 19 A new config option has been added. There is a 'role' that can be filled, | |
| 20 that of the 'dispatcher'. This person acts as a central sentinel for issues | |
| 21 coming into the system. You can configure it so that all e-mail error messages | |
| 22 get bounced to them, them and the user in question, or just the user (default). | |
| 23 | |
| 24 To toggle these switches, look at the new classic and minimal config.py's, | |
| 25 specifically: | |
| 26 | |
| 27 | |
| 28 # The 'dispatcher' is a role that can get notified of new items to the database. | |
| 29 DISPATCHER_EMAIL = ADMIN_EMAIL | |
| 30 | |
| 31 ... | |
| 32 | |
| 33 | |
| 34 # Send error messages to the dispatcher, user, or both? | |
| 35 # If 'dispatcher', error message notifications will only be sent to the dispatcher. | |
| 36 # If 'user', error message notifications will only be sent to the user. | |
| 37 # If 'both', error message notifications will be sent to both individuals. | |
| 38 ERROR_MESSAGES_TO = 'user' | |
| 39 | |
| 40 Migrating from 0.6 to 0.7 | 12 Migrating from 0.6 to 0.7 |
| 41 ========================= | 13 ========================= |
| 14 | |
| 15 0.7.0 Saving and sharing of user queries | |
| 16 ---------------------------------------- | |
| 17 | |
| 18 Due to popular demand, the user query saving mechanisms have been | |
| 19 overhauled. This means that queries remember the user that created them | |
| 20 and they may be marked as being private for a particular user. | |
| 21 | |
| 22 You *are not required* to make these changes. You only need to make them | |
| 23 if you wish to use the new query editing features. It's highly | |
| 24 recommended, as the effort is minimal. | |
| 25 | |
| 26 1. You will need to edit your tracker's ``dbinit.py`` to change the way | |
| 27 queries are stored. Change the lines:: | |
| 28 | |
| 29 query = Class(db, "query", | |
| 30 klass=String(), name=String(), | |
| 31 url=String()) | |
| 32 query.setkey("name") | |
| 33 | |
| 34 to:: | |
| 35 | |
| 36 query = Class(db, "query", | |
| 37 klass=String(), name=String(), | |
| 38 url=String(), private_for=Link('user')) | |
| 39 | |
| 40 That is, add the "private_for" property, and remove the line that says | |
| 41 ``query.setkey("name")``. The latter is the most important edit here. | |
| 42 | |
| 43 2. You will also need to copy the ``query.edit.html`` template page from the | |
| 44 ``templates/classic/html/`` directory of the source to your tracker's | |
| 45 ``html`` directory. | |
| 46 | |
| 47 3. Once you've done that, edit the tracker's ``page.html`` template to | |
| 48 change:: | |
| 49 | |
| 50 <td rowspan="2" valign="top" class="sidebar"> | |
| 51 <p class="classblock" tal:condition="request/user/queries"> | |
| 52 <b>Your Queries</b><br> | |
| 53 <tal:block tal:repeat="qs request/user/queries"> | |
| 54 | |
| 55 to:: | |
| 56 | |
| 57 <td rowspan="2" valign="top" class="sidebar"> | |
| 58 <p class="classblock"> | |
| 59 <b>Your Queries</b> (<a href="query?@template=edit">edit</a>)<br> | |
| 60 <tal:block tal:repeat="qs request/user/queries"> | |
| 61 | |
| 62 That is, you're removing the ``tal:condition`` and adding a link to the | |
| 63 new edit page. | |
| 64 | |
| 65 4. You might also wish to remove the redundant query editing section from the | |
| 66 ``user.item.html`` page. | |
| 67 | |
| 68 | |
| 69 0.7.0 Added Dispatcher role | |
| 70 --------------------------- | |
| 71 | |
| 72 A new config option has been added that specifies the email address of | |
| 73 a "dispatcher" role. This email address acts as a central sentinel for | |
| 74 issues coming into the system. You can configure it so that all e-mail | |
| 75 error messages get bounced to them, them and the user in question, or | |
| 76 just the user (default). | |
| 77 | |
| 78 To toggle these switches, add the "DISPATCHER_EMAIL" and | |
| 79 "ERROR_MESSAGES_TO" configuration values to your tracker's ``config.py``. | |
| 80 See the `customisation documentation`_ for how to use them. | |
| 81 | |
| 42 | 82 |
| 43 0.7.0 Added CSV export action | 83 0.7.0 Added CSV export action |
| 44 ----------------------------- | 84 ----------------------------- |
| 45 | 85 |
| 46 A new action has been added which exports the current index page or search | 86 A new action has been added which exports the current index page or search |