Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 1820:9560e94beeea maint-0.6 0.6.2
pre-release machinations
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Mon, 29 Sep 2003 08:08:31 +0000 |
| parents | d97e8f4989b6 |
| children | f0bf3a9a8b0e |
comparison
equal
deleted
inserted
replaced
| 1814:ffba0a574b4e | 1820:9560e94beeea |
|---|---|
| 5 Please read each section carefully and edit your tracker home files | 5 Please read each section carefully and edit your tracker home files |
| 6 accordingly. | 6 accordingly. |
| 7 | 7 |
| 8 .. contents:: | 8 .. contents:: |
| 9 | 9 |
| 10 | |
| 10 Migrating from 0.5 to 0.6 | 11 Migrating from 0.5 to 0.6 |
| 11 ========================= | 12 ========================= |
| 13 | |
| 12 | 14 |
| 13 0.6.0 Configuration | 15 0.6.0 Configuration |
| 14 ------------------- | 16 ------------------- |
| 15 | 17 |
| 16 Introduced EMAIL_FROM_TAG config variable. This value is inserted into | 18 Introduced EMAIL_FROM_TAG config variable. This value is inserted into |
| 27 doesn't cross-import detectors from other trackers (if you run more than one | 29 doesn't cross-import detectors from other trackers (if you run more than one |
| 28 in a single roundup-server). This change means that you'll need to copy the | 30 in a single roundup-server). This change means that you'll need to copy the |
| 29 __init__.py from roundup/templates/classic/detectors/__init__.py to your | 31 __init__.py from roundup/templates/classic/detectors/__init__.py to your |
| 30 <tracker home>/detectors/__init__.py. Don't worry, the "classic" __init__ is a | 32 <tracker home>/detectors/__init__.py. Don't worry, the "classic" __init__ is a |
| 31 one-size-fits-all, so it'll work even if you've added/removed detectors. | 33 one-size-fits-all, so it'll work even if you've added/removed detectors. |
| 34 | |
| 35 0.6.0 Templating changes | |
| 36 ------------------------ | |
| 37 | |
| 38 The ``user.item`` template (in the tracker home "templates" directory) | |
| 39 needs to have the following hidden variable added to its form (between the | |
| 40 ``<form...>`` and ``</form>`` tags:: | |
| 41 | |
| 42 <input type="hidden" name=":template" value="item"> | |
| 32 | 43 |
| 33 | 44 |
| 34 0.6.0 Form handling changes | 45 0.6.0 Form handling changes |
| 35 --------------------------- | 46 --------------------------- |
| 36 | 47 |
| 67 they will not be visible in new unicode environment. Some of such data (e.g. | 78 they will not be visible in new unicode environment. Some of such data (e.g. |
| 68 user names, keywords, etc) can be edited by administrator, the others | 79 user names, keywords, etc) can be edited by administrator, the others |
| 69 (e.g. messages' contents) is not editable via web interface. Currently there | 80 (e.g. messages' contents) is not editable via web interface. Currently there |
| 70 is no tool for converting such data, the only solution is to close | 81 is no tool for converting such data, the only solution is to close |
| 71 appropriate old issues and create new ones with the same content. | 82 appropriate old issues and create new ones with the same content. |
| 83 | |
| 72 | 84 |
| 73 0.6.0 User timezone support | 85 0.6.0 User timezone support |
| 74 --------------------------- | 86 --------------------------- |
| 75 | 87 |
| 76 From version 0.6.0 roundup supports displaying of Date data in user' local | 88 From version 0.6.0 roundup supports displaying of Date data in user' local |
| 100 | 112 |
| 101 After providing timezone, roundup will show all dates values, found in web | 113 After providing timezone, roundup will show all dates values, found in web |
| 102 and mail interfaces in local time. It will also accept any Date info in | 114 and mail interfaces in local time. It will also accept any Date info in |
| 103 local time, convert and store it in GMT. | 115 local time, convert and store it in GMT. |
| 104 | 116 |
| 117 | |
| 105 0.6.0 Search page structure | 118 0.6.0 Search page structure |
| 106 --------------------------- | 119 --------------------------- |
| 107 | 120 |
| 108 In order to accomodate query editing the search page has been restructured. If | 121 In order to accomodate query editing the search page has been restructured. If |
| 109 you want to provide your users with query editing, you should update your | 122 you want to provide your users with query editing, you should update your |