Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5122:1c90f15a177f
issue2550831: Make the classic template query.edit page work.
Forgot to update the classic schema.py with the Restore permissions
for the query class for the User role.
Also forgot to document same in upgrading.txt.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 03 Jul 2016 14:20:48 -0400 |
| parents | 894aa07be6cb |
| children | d16ba6e6624b |
comparison
equal
deleted
inserted
replaced
| 5121:894aa07be6cb | 5122:1c90f15a177f |
|---|---|
| 172 | 172 |
| 173 Improvements in Classic Tracker query.edit.html template | 173 Improvements in Classic Tracker query.edit.html template |
| 174 -------------------------------------------------------- | 174 -------------------------------------------------------- |
| 175 | 175 |
| 176 There is a new query editing template included in the distribution at: | 176 There is a new query editing template included in the distribution at: |
| 177 share/roundup/templates/classic/html/query.edit.html | 177 |
| 178 ``share/roundup/templates/classic/html/query.edit.html`` | |
| 178 | 179 |
| 179 This template fixes: | 180 This template fixes: |
| 180 | 181 |
| 181 * Once added, a public query could not be removed from "Your Queries". Trying to do so would cause a permissions error. | 182 * public query could not be removed from "Your Queries" once it was added. |
| 182 * The private yes/no dropdown always showed "yes" regardless of underlying state | 183 Trying to do so would cause a permissions error. |
| 183 * The query Delete button did not work. | 184 * private yes/no dropdown always showed "yes" regardless of |
| 184 * The same query being displayed multiple times | 185 underlying state |
| 186 * query Delete button did not work. | |
| 187 * same query being displayed multiple times | |
| 185 | 188 |
| 186 It also adds: | 189 It also adds: |
| 187 * the table layout displays queries created by the user first, then available public queries. | 190 * the table layout displays queries created by the user first, |
| 191 then available public queries. | |
| 188 * public query owners are shown | 192 * public query owners are shown |
| 189 * better support for deleted queries. When a query is deleted, it is | 193 * better support for deleted queries. When a query is deleted, it is |
| 190 still available for those who added it to their query list. If you | 194 still available for those who added it to their query list. If you |
| 191 are the query owner, you can restore (undelete) the query. If you | 195 are the query owner, you can restore (undelete) the query. If you |
| 192 are not the owner you can remove it from your query list. | 196 are not the owner you can remove it from your query list. |
| 195 have to use the class editor or roundup_admin command line to | 199 have to use the class editor or roundup_admin command line to |
| 196 restore it.) | 200 restore it.) |
| 197 * notifies the user that delete/restore requires javascript. It | 201 * notifies the user that delete/restore requires javascript. It |
| 198 always did, but that requirement wasn't displayed. | 202 always did, but that requirement wasn't displayed. |
| 199 | 203 |
| 200 If you have not modified the query.edit.html template in your tracker, you should be | 204 To use the new template, you must add Restore permission on queries to |
| 201 able to copy the new version from the location above. Otherwise you will | 205 allow the user to restore queries (see below). |
| 202 have to merge the changes into your modified template. | 206 |
| 207 If you have not modified the query.edit.html template in your tracker, | |
| 208 you should be able to copy the new version from the location above. | |
| 209 Otherwise you will have to merge the changes into your modified template. | |
| 210 | |
| 211 You will need to add the query Restore permission for the User role to | |
| 212 your tracker's schema.py file. Place it right after the query retire | |
| 213 permission for the user role. After the change it should look like:: | |
| 214 | |
| 215 p = db.security.addPermission(name='Retire', klass='query', check=edit_query, | |
| 216 description="User is allowed to retire their queries") | |
| 217 db.security.addPermissionToRole('User', p) | |
| 218 p = db.security.addPermission(name='Restore', klass='query', check=edit_query, | |
| 219 description="User is allowed to restore their queries") | |
| 220 db.security.addPermissionToRole('User', p) | |
| 221 | |
| 222 where the last three lines are the ones you need to add. | |
| 203 | 223 |
| 204 Migrating from 1.5.0 to 1.5.1 | 224 Migrating from 1.5.0 to 1.5.1 |
| 205 ============================= | 225 ============================= |
| 206 | 226 |
| 207 User data visibility | 227 User data visibility |