Opened 4 years ago
Last modified 4 years ago
#33233 closed New feature
Handle 404 Not Found Error when invalid page num comes is given to ListView — at Initial Version
| Reported by: | DongGeon Lee | Owned by: | nobody |
|---|---|---|---|
| Component: | Generic views | Version: | 4.0 |
| Severity: | Normal | Keywords: | ListView, Paginator, Pagination |
| Cc: | DongGeon Lee | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There is pagination in ListView and it show 404 error when page number is out of page range.
It is reasonable but I think the options to control 404 exception always should be there.
In current Implementation, if users want to handle 404 exception(Http404), they have to override whole get_queryset() in django.view.generic.list.py or validate_number() in django.core.paginator.py.
So I suggest the flag allow_out_of_range: bool in MultipleObjectMixin class to on/off 404 exception.
(I already have a pull request ready to go.)
Note:
See TracTickets
for help on using tickets.