#1857 closed defect (fixed)
[patch] get_next_by_FIELD and get_previous_by_FIELD don't take params
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Core (Other) | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The docs for get_next/previous_by_FIELD state
Both methods accept optional keyword arguments, which should be in the format described in Field lookups above.
It's not clear what should will do, and anyway, they don't take keyword arguments. This patch makes the method do what I'd expect, which is to return the next/previous page that matches the passed filter params.
Attachments (1)
Change History (2)
by , 18 years ago
Attachment: | get_next_previous.diff added |
---|
comment:1 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [3157]) Fixed #1857 -- Fixed get_previous_by_FIELD and get_next_by_FIELD to work
properly with keyword arguments. Patch from tom@….