Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 1813:6c2cff78d6a0
added note about hidden :template var in user.item ([SF#799842])
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Wed, 17 Sep 2003 22:30:30 +0000 |
| parents | a3b1b1dcf639 |
| children | 461d8aa81376 |
comparison
equal
deleted
inserted
replaced
| 1812:6f3b92a817aa | 1813:6c2cff78d6a0 |
|---|---|
| 15 | 15 |
| 16 Removed Database.curuserid attribute. Any code referencing this attribute should | 16 Removed Database.curuserid attribute. Any code referencing this attribute should |
| 17 be replaced with a call to Database.getuid(). | 17 be replaced with a call to Database.getuid(). |
| 18 | 18 |
| 19 | 19 |
| 20 | |
| 20 Migrating from 0.5 to 0.6 | 21 Migrating from 0.5 to 0.6 |
| 21 ========================= | 22 ========================= |
| 23 | |
| 22 | 24 |
| 23 0.6.0 Configuration | 25 0.6.0 Configuration |
| 24 ------------------- | 26 ------------------- |
| 25 | 27 |
| 26 Introduced EMAIL_FROM_TAG config variable. This value is inserted into | 28 Introduced EMAIL_FROM_TAG config variable. This value is inserted into |
| 37 doesn't cross-import detectors from other trackers (if you run more than one | 39 doesn't cross-import detectors from other trackers (if you run more than one |
| 38 in a single roundup-server). This change means that you'll need to copy the | 40 in a single roundup-server). This change means that you'll need to copy the |
| 39 __init__.py from roundup/templates/classic/detectors/__init__.py to your | 41 __init__.py from roundup/templates/classic/detectors/__init__.py to your |
| 40 <tracker home>/detectors/__init__.py. Don't worry, the "classic" __init__ is a | 42 <tracker home>/detectors/__init__.py. Don't worry, the "classic" __init__ is a |
| 41 one-size-fits-all, so it'll work even if you've added/removed detectors. | 43 one-size-fits-all, so it'll work even if you've added/removed detectors. |
| 44 | |
| 45 0.6.0 Templating changes | |
| 46 ------------------------ | |
| 47 | |
| 48 The ``user.item`` template (in the tracker home "templates" directory) | |
| 49 needs to have the following hidden variable added to its form (between the | |
| 50 ``<form...>`` and ``</form>`` tags:: | |
| 51 | |
| 52 <input type="hidden" name=":template" value="item"> | |
| 42 | 53 |
| 43 | 54 |
| 44 0.6.0 Form handling changes | 55 0.6.0 Form handling changes |
| 45 --------------------------- | 56 --------------------------- |
| 46 | 57 |
| 77 they will not be visible in new unicode environment. Some of such data (e.g. | 88 they will not be visible in new unicode environment. Some of such data (e.g. |
| 78 user names, keywords, etc) can be edited by administrator, the others | 89 user names, keywords, etc) can be edited by administrator, the others |
| 79 (e.g. messages' contents) is not editable via web interface. Currently there | 90 (e.g. messages' contents) is not editable via web interface. Currently there |
| 80 is no tool for converting such data, the only solution is to close | 91 is no tool for converting such data, the only solution is to close |
| 81 appropriate old issues and create new ones with the same content. | 92 appropriate old issues and create new ones with the same content. |
| 93 | |
| 82 | 94 |
| 83 0.6.0 User timezone support | 95 0.6.0 User timezone support |
| 84 --------------------------- | 96 --------------------------- |
| 85 | 97 |
| 86 From version 0.6.0 roundup supports displaying of Date data in user' local | 98 From version 0.6.0 roundup supports displaying of Date data in user' local |
| 110 | 122 |
| 111 After providing timezone, roundup will show all dates values, found in web | 123 After providing timezone, roundup will show all dates values, found in web |
| 112 and mail interfaces in local time. It will also accept any Date info in | 124 and mail interfaces in local time. It will also accept any Date info in |
| 113 local time, convert and store it in GMT. | 125 local time, convert and store it in GMT. |
| 114 | 126 |
| 127 | |
| 115 0.6.0 Search page structure | 128 0.6.0 Search page structure |
| 116 --------------------------- | 129 --------------------------- |
| 117 | 130 |
| 118 In order to accomodate query editing the search page has been restructured. If | 131 In order to accomodate query editing the search page has been restructured. If |
| 119 you want to provide your users with query editing, you should update your | 132 you want to provide your users with query editing, you should update your |