ListView pagination error does not expose specific InvalidPage exception message in 404.
|Reported by:||seawolf||Owned by:||seawolf|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When viewing a generic list page with pagenate_by set, several exceptions can be thrown that inherit from InvalidPage in the case of a 404 error. However, the 404 page simply states "Invalid page (1).", which does not give the developer anything useful to help with figuring out what the source of the problem is.
Should this actually return a 500 error?
Change History (5)
comment:1 Changed 4 years ago by seawolf
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
Changed 4 years ago by seawolf
comment:3 Changed 4 years ago by seawolf
- Component changed from HTTP handling to Generic views
- UI/UX unset
- Version changed from 1.5-alpha-1 to master