Web Staff Client: Pending Patrons limited to 100
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned | ||
3.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In 3.0.2 Web Client:
The Pending Patrons grid is cutting off after the first 100 pending patron applications. Attempting to page to the next 100 simply reloads the same entries. Downloading full CSV downloads the same first 100. (The xul client in this particular case shows that there are 105 pending patrons.) New pending patrons that are added appear in the xul client, but not in the web client.
Since the web client is also missing the Delete button in that interface (bug https:/
The xul client defaulted to a limit of 100 (which could then be changed in the interface and refreshed), so perhaps the retrieval script in the web client was built with that artificial limit of 100 as well?
Changed in evergreen: | |
assignee: | nobody → Jeff Godin (jgodin) |
Changed in evergreen: | |
milestone: | none → 3.3.1 |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.3.4 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
Changed in evergreen: | |
assignee: | Jeff Godin (jgodin) → Galen Charlton (gmc) |
status: | In Progress → Confirmed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
The table only displays 100, but it also ignores the row limits along with pagination. If you have 30 pending patrons and limit the rows to 10, it still displays 30 rows.