Modify ↓
#12647 closed defect (fixed)
Query page ignores max parameter when its parameter is only max parameter
| Reported by: | Jun Omae | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.17 |
| Component: | query system | Version: | 1.0.11 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: |
Fixed |
||
| API Changes: | |||
| Internal Changes: | |||
Description
This issue can be reproduced with query:?max=1. I think query page should respect max parameter.
Attachments (0)
Change History (3)
comment:1 by , 8 years ago
| Milestone: | next-stable-1.0.x → 1.0.16 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
comment:2 by , 8 years ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.



Related issue. If the
default_queryincludesdesc=1(status!=closed&owner=$USER&order=reporter&desc=1), the order would not be overridden by query:?desc=0.I don't understand this area in the code well enough to be certain, but here are some changes for review: log:rjollos.git:t12647. Tests are passing for me, but probably more coverage is needed.