Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5120:722394a48d7b
issue2550831: Make the classic template query.edit page work.
R David Murray had a number of fixes.
At least some of the fixes were already present in the devel and
responsive templates.
I touched up the html a bit and did what I hope aresome improvement
for performance by shoving criteria into the filter rather than
looping over all issues and filtering at the tal level.
Also used R David's method to add a restore feature and work around an
issue where a retired (deleted) query could still be in the active
list. But because it was retired there was no way to manipulate it.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 03 Jul 2016 12:23:36 -0400 |
| parents | cf112b90fa8d |
| children | 894aa07be6cb |
comparison
equal
deleted
inserted
replaced
| 5119:748ba87e1aca | 5120:722394a48d7b |
|---|---|
| 129 db.security.addPermissionToRole ('Anonymous', p) | 129 db.security.addPermissionToRole ('Anonymous', p) |
| 130 | 130 |
| 131 If you are running a tracker that **does not** allow read access for | 131 If you are running a tracker that **does not** allow read access for |
| 132 anonymous, you should remove this entry as it can be used to perform | 132 anonymous, you should remove this entry as it can be used to perform |
| 133 a username guessing attack against a roundup install. | 133 a username guessing attack against a roundup install. |
| 134 | |
| 135 Improvements in Classic Tracker query.edit.html template | |
| 136 -------------------------------------------------------- | |
| 137 | |
| 138 There is a new query editing template included in the distribution at: | |
| 139 share/roundup/templates/classic/html/query.edit.html | |
| 140 | |
| 141 This template fixes: | |
| 142 | |
| 143 * Once added, a public query could not be removed from "Your Queries". Trying to do so would cause a permissions error. | |
| 144 * The private yes/no dropdown always showed "yes" regardless of underlying state | |
| 145 * The query Delete button did not work. | |
| 146 * The same query being displayed multiple times | |
| 147 | |
| 148 It also adds: | |
| 149 * the table layout displays queries created by the user first, then available public queries. | |
| 150 * public query owners are shown | |
| 151 * better support for deleted queries. When a query is deleted, it is | |
| 152 still available for those who added it to their query list. If you | |
| 153 are the query owner, you can restore (undelete) the query. If you | |
| 154 are not the owner you can remove it from your query list. | |
| 155 (If a query is deleted and nobody had it in their query list, it | |
| 156 will not show up in the "Active retired queries" section. You will | |
| 157 have to use the class editor or roundup_admin command line to | |
| 158 restore it.) | |
| 159 * notifies the user that delete/restore requires javascript. It | |
| 160 always did, but that requirement wasn't displayed. | |
| 161 | |
| 162 If you have not modified the query.edit.html template in your tracker, you should be | |
| 163 able to copy the new version from the location above. Otherwise you will | |
| 164 have to merge the changes into your modified template. | |
| 134 | 165 |
| 135 Migrating from 1.5.0 to 1.5.1 | 166 Migrating from 1.5.0 to 1.5.1 |
| 136 ============================= | 167 ============================= |
| 137 | 168 |
| 138 User data visibility | 169 User data visibility |