Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5179:e8b3d3a14563
- issue2550796: Calendar and Classhelp selection tools don't cause
onchange event to be triggered.
Using the helper popups for modifying lists of users, lists of
issues, dates etc.. now trigger the change event on the form's
field. This allows onchange javascript to trigger to highlight
changes, recalculate other form values etc. See ``upgrading.txt``
for details on applying these changes to your tracker.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 28 Jan 2017 20:58:19 -0500 |
| parents | 12190efa30d4 |
| children | 36630a062fb5 |
comparison
equal
deleted
inserted
replaced
| 5178:1800d19a55a0 | 5179:e8b3d3a14563 |
|---|---|
| 204 (issue, user, keyword ....). It controls the next page displayed after | 204 (issue, user, keyword ....). It controls the next page displayed after |
| 205 creating the item. If '__redirect_to' is not set, then you end up on | 205 creating the item. If '__redirect_to' is not set, then you end up on |
| 206 the page for the newly created item. The url value assigned to | 206 the page for the newly created item. The url value assigned to |
| 207 __redirect_to must be under the tracker's base url and must be properly | 207 __redirect_to must be under the tracker's base url and must be properly |
| 208 url encoded. | 208 url encoded. |
| 209 | |
| 210 Helper popups trigger change events on the original page | |
| 211 -------------------------------------------------------- | |
| 212 | |
| 213 The helper popups used to set dates (from a calendar), change lists of | |
| 214 users or lists of issues did not notify the browser that the fields | |
| 215 had been changed. This release adds code to trigger the change event. | |
| 216 | |
| 217 To add the change event to the calendar popup, you don't need to do | |
| 218 any changes to the tracker. It is all done in the roundup python code | |
| 219 in templating.py. | |
| 220 | |
| 221 To add the change event when updating users using the help-submit | |
| 222 template, copy | |
| 223 share/roundup/templates/devel/html/_generic.help-submit.html and | |
| 224 replace your tracker's html/_generic.help-submit.html. If you have | |
| 225 done local changes to this file, change your file to include the code | |
| 226 that defines the onclick event for the input field with | |
| 227 id="btn_apply". | |
| 228 | |
| 229 To add the change event when updating lists of issues copy | |
| 230 share/roundup/templates/devel/html/help_controls.js to your tracer's | |
| 231 html directory. If you have made local changes to the javascript file, | |
| 232 merge the two if/else blocks labeled:: | |
| 233 | |
| 234 /* trigger change event on the field we changed */ | |
| 235 | |
| 236 into your help_controls.js | |
| 209 | 237 |
| 210 html/_generic.404.html in trackers use page template | 238 html/_generic.404.html in trackers use page template |
| 211 ---------------------------------------------------- | 239 ---------------------------------------------------- |
| 212 | 240 |
| 213 The original generic 404 error pages for many trackers did not use the | 241 The original generic 404 error pages for many trackers did not use the |