MAX_PAGE_SIZE parameter is being ignored by the paginator #9204

Closed
opened 2025-12-29 20:46:55 +01:00 by adam · 4 comments
Owner

Originally created by @jurossi-cisco on GitHub (Feb 7, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.8

Steps to Reproduce

MAX_PAGE_SIZE parameter is being ignored.

It has a default of 1000 and in the demo site it can be seen that more than a 1000 records can be requested.
https://demo.netbox.dev/extras/changelog/?per_page=2000

Expected Behavior

MAX_PAGE_SIZE should take effect, and always limit the the objects per page, regardless of the per_page setting in the paginator.

Observed Behavior

You can get more than MAX_PER_PAGE objects rendered in the UI paginator

Originally created by @jurossi-cisco on GitHub (Feb 7, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.2 ### Python Version 3.8 ### Steps to Reproduce MAX_PAGE_SIZE parameter is being ignored. It has a default of 1000 and in the demo site it can be seen that more than a 1000 records can be requested. https://demo.netbox.dev/extras/changelog/?per_page=2000 ### Expected Behavior MAX_PAGE_SIZE should take effect, and always limit the the objects per page, regardless of the per_page setting in the paginator. ### Observed Behavior You can get more than MAX_PER_PAGE objects rendered in the UI paginator
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:46:55 +01:00
adam closed this issue 2025-12-29 20:46:55 +01:00
Author
Owner

@aryansanchiya commented on GitHub (Feb 7, 2024):

You can set "None" to per page, after this it will capped at 1000.
It should work.

@aryansanchiya commented on GitHub (Feb 7, 2024): You can set "None" to per page, after this it will capped at 1000. It should work.
Author
Owner

@jeffgdotorg commented on GitHub (Feb 7, 2024):

Thanks for your report. We need more information in the Steps to Reproduce section before we're able to attempt to reproduce the issue you're seeing. Please specify where and how you're setting MAX_PER_PAGE; I'm personally not aware of a NetBox configuration parameter by that name, and git grep isn't turning up anything either.

Additionally, please bear in mind that the demo system is not a valid reference point for bug reports, as is called out in the issue report template.

@jeffgdotorg commented on GitHub (Feb 7, 2024): Thanks for your report. We need more information in the *Steps to Reproduce* section before we're able to attempt to reproduce the issue you're seeing. Please specify where and how you're setting `MAX_PER_PAGE`; I'm personally not aware of a NetBox configuration parameter by that name, and `git grep` isn't turning up anything either. Additionally, please bear in mind that the demo system is not a valid reference point for bug reports, as is called out in the issue report template.
Author
Owner

@jurossi-cisco commented on GitHub (Feb 8, 2024):

Sorry parameter is MAX_PAGE_SIZE. It has a default of 1000 per https://demo.netbox.dev/static/docs/configuration/dynamic-settings/.
I edited my report, apologies for the confusion

Called out that netbox demo as it has more than 1000 objects at the changelog, I would recommend setting https://demo.netbox.dev/ with more than 1000 objects to test the paginator

We are using netbox docker image, I will gather more information

@jurossi-cisco commented on GitHub (Feb 8, 2024): Sorry parameter is MAX_PAGE_SIZE. It has a default of 1000 per https://demo.netbox.dev/static/docs/configuration/dynamic-settings/. I edited my report, apologies for the confusion Called out that netbox demo as it has more than 1000 objects at the changelog, I would recommend setting https://demo.netbox.dev/ with more than 1000 objects to test the paginator We are using netbox docker image, I will gather more information
Author
Owner

@jeremystretch commented on GitHub (Feb 13, 2024):

Per the bug report template:

Additionally, do not rely on the demo instance for reproducing suspected bugs, as its data is prone to modification or deletion at any time.

We are not able to accept any bug report which references data or configuration on the demo server. I'm going to close this out as sufficient reproduction steps have not been provided. If you are able to reproduce a suspected bug entirely on your local instance, you are welcome to submit a new bug report including detailed steps that someone else can follow to reproduce the behavior.

@jeremystretch commented on GitHub (Feb 13, 2024): Per the bug report template: > Additionally, **do not rely on the demo instance** for reproducing suspected bugs, as its data is prone to modification or deletion at any time. We are not able to accept _any_ bug report which references data or configuration on the demo server. I'm going to close this out as sufficient reproduction steps have not been provided. If you are able to reproduce a suspected bug entirely on your local instance, you are welcome to submit a new bug report including detailed steps that someone else can follow to reproduce the behavior.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9204