starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 13:00:30 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Visual Bug in the permissions page #11948

New Issue
Open
opened 2025-12-29 21:51:48 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:51:48 +01:00
Owner
Copy Link

Originally created by @gebz-97 on GitHub (Dec 24, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.4.9

Python Version

3.10

Steps to Reproduce

  1. click on permissions
  2. go to the object selection
  3. scroll down

Expected Behavior

scroll normally

Observed Behavior

visual bug

Image
Originally created by @gebz-97 on GitHub (Dec 24, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.4.9 ### Python Version 3.10 ### Steps to Reproduce 1. click on permissions 2. go to the object selection 3. scroll down ### Expected Behavior scroll normally ### Observed Behavior visual bug <img width="1869" height="929" alt="Image" src="https://github.com/user-attachments/assets/ce7a52c5-ffde-4e2b-ba63-2863cbdee224" />
adam added the type: bugstatus: under reviewnetbox labels 2025-12-29 21:51:48 +01:00
adam commented 2025-12-29 21:51:49 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Dec 24, 2025):

Thanks for raising the issue.

Since this looks like a frontend/UI problem, could you share which browser (and version) you’re using, and whether you can reproduce it in a different browser (or in an incognito/private window)?

This kind of behavior is sometimes caused by stale cached assets after an upgrade. A couple of quick things to try/check:

  • Do a hard refresh / clear the browser cache
  • Test in a private window (to rule out cached assets/extensions)
  • If this appeared after an upgrade, confirm that python manage.py collectstatic was run (and the web service restarted) as part of the upgrade process

Let us know what you find.

@pheus commented on GitHub (Dec 24, 2025): Thanks for raising the issue. Since this looks like a frontend/UI problem, could you share which browser (and version) you’re using, and whether you can reproduce it in a different browser (or in an incognito/private window)? This kind of behavior is sometimes caused by stale cached assets after an upgrade. A couple of quick things to try/check: - Do a hard refresh / clear the browser cache - Test in a private window (to rule out cached assets/extensions) - If this appeared after an upgrade, confirm that `python manage.py collectstatic` was run (and the web service restarted) as part of the upgrade process Let us know what you find.
adam commented 2025-12-29 21:51:49 +01:00
Author
Owner
Copy Link

@gebz-97 commented on GitHub (Dec 24, 2025):

reproduced it on edge (I usually never use edge)
Image
Image

@gebz-97 commented on GitHub (Dec 24, 2025): reproduced it on edge (I usually never use edge) <img width="850" height="269" alt="Image" src="https://github.com/user-attachments/assets/fcd7a78b-d82e-46b5-a30c-11ae8a398493" /> <img width="448" height="169" alt="Image" src="https://github.com/user-attachments/assets/54762ea1-3a4a-48c2-8c9b-7e3bcd4d57db" />
adam commented 2025-12-29 21:51:49 +01:00
Author
Owner
Copy Link

@gebz-97 commented on GitHub (Dec 24, 2025):

Image
@gebz-97 commented on GitHub (Dec 24, 2025): <img width="663" height="224" alt="Image" src="https://github.com/user-attachments/assets/2b3bf714-cdb9-4af8-9164-f50ca6869c10" />
adam commented 2025-12-29 21:51:50 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Dec 29, 2025):

Thanks for the screenshots — that helps.

If you’re definitely running v4.4.9, then the collectstatic prompt showing a 4.4.8 path (/opt/netbox-4.4.8/...) is a strong hint that static files are being collected from (or served out of) the previous release directory.

A couple of things to double-check:

  • Confirm you’re running manage.py collectstatic from the active NetBox installation/virtualenv (the one used by your systemd service / container), not an older checkout.
  • Verify that your web server (or reverse proxy) is pointing /static/ at the same STATIC_ROOT directory you’re collecting into. If it’s still aliased to the 4.4.8 path, the UI can end up serving stale assets even though the app itself is 4.4.9.
  • After re-collecting static files to the correct location, do a hard refresh (or test in an incognito/private window) to rule out cached assets.
@pheus commented on GitHub (Dec 29, 2025): Thanks for the screenshots — that helps. If you’re definitely running **v4.4.9**, then the `collectstatic` prompt showing a **4.4.8** path (`/opt/netbox-4.4.8/...`) is a strong hint that static files are being collected from (or served out of) the *previous* release directory. A couple of things to double-check: - Confirm you’re running `manage.py collectstatic` from the **active** NetBox installation/virtualenv (the one used by your systemd service / container), not an older checkout. - Verify that your web server (or reverse proxy) is pointing `/static/` at the same `STATIC_ROOT` directory you’re collecting into. If it’s still aliased to the 4.4.8 path, the UI can end up serving stale assets even though the app itself is 4.4.9. - After re-collecting static files to the correct location, do a hard refresh (or test in an incognito/private window) to rule out cached assets.
adam commented 2025-12-29 21:51:50 +01:00
Author
Owner
Copy Link

@gebz-97 commented on GitHub (Dec 29, 2025):

4.4.9 in the issue was a typo, it is 4.4.8

@gebz-97 commented on GitHub (Dec 29, 2025): 4.4.9 in the issue was a typo, it is 4.4.8
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label netbox status: under review type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11948
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?