DescriptionCommit b8cfd0f implemented Javascript based filtering and navigation on issue listing pages.
In order to do so, the issue listing table needed to be given an ID, and the output of mt_rand was used to ensure the ID was unique if the table was ever called multiple times in one page.
The downside of this, is that where the output of JILS is being used in an incremental backup, the pages change every time they're requested, regardless of whether there's been any activity on the project.
Need to change to use a consistent ID.
Activity
2015-09-18 16:15:59
so moving to a static ID as a short-term fix should be a suitable method of stopping the issue with backups.
Needs addressing properly longer term though.
2015-09-18 16:16:03
2015-09-18 16:17:56
2015-09-18 16:18:15
2015-09-18 16:18:56
Webhook User-Agent
View Commit
2015-09-23 14:27:03
I think the best way forward is to have a 'default', but to allow the calling page to override it, so the first table might get ID 1 and then any page introducing a second table can set it to ID 2 (or 'foo' or 'biscuits' or whatever, so long as it's different).
2015-09-23 14:30:02
2015-09-23 14:30:16
2015-09-23 14:30:56
Webhook User-Agent
View Commit
2015-09-23 14:44:32
2015-09-23 14:44:40
2015-09-23 14:44:40
2015-09-23 14:44:43
2016-04-29 14:54:01
2016-04-29 14:54:01
2016-04-29 14:54:01
2016-04-29 14:55:11
2016-04-29 14:55:11
2016-04-29 14:55:11
2016-04-29 14:58:52
2016-04-29 14:58:52
2016-04-29 14:58:52
2016-04-29 14:58:56