Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "Version History" pane for plugins is broken #17754

Closed
peteeckel opened this issue Oct 14, 2024 · 0 comments · Fixed by #17766
Closed

The "Version History" pane for plugins is broken #17754

peteeckel opened this issue Oct 14, 2024 · 0 comments · Fixed by #17766
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@peteeckel
Copy link
Contributor

peteeckel commented Oct 14, 2024

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.3

Python Version

3.12

Steps to Reproduce

  1. Open the "Admin/System/Plugins" page via the navigation menu
  2. Click on any plugin (e.g. NetBox BGP)
  3. In the "Version History" pane, select the "Per Page" dropdown and klick on "25" (any other value is OK, too)

Expected Behavior

Actually I would expect the paginator not to be there at all, as there are only the five most recent versions in the API so there won't be a longer list of versions anyway.

But since a paginator is shown, I would expect the last 25, 50, 100 ... most recent versions to appear in the "Version History" table.

Observed Behavior

A narrow version of the plugin's info page appears in the pane.

Screenshot 2024-10-14 at 19 11 07
@peteeckel peteeckel added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Oct 14, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Oct 15, 2024
@arthanson arthanson self-assigned this Oct 15, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants