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

Device type compontent creation forms do not render #5050

New Issue
Closed
opened 2025-12-29 19:23:33 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:23:33 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jul 7, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.8

Python version

3.7

Steps to Reproduce

  1. Create a device type
  2. Attempt to add any type of component (e.g. interface) to a device type

Expected Behavior

The complete component creation form should render.

Observed Behavior

The page renders, however the form is empty.

This is due to a bug in the template which attempts to iterate through form.custom_fields. For device type components, custom_fields is not set. (The exception being raised is apparently swallowed within the template rendering, so our tests never caught it.)

Originally created by @jeremystretch on GitHub (Jul 7, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.8 ### Python version 3.7 ### Steps to Reproduce 1. Create a device type 2. Attempt to add any type of component (e.g. interface) to a device type ### Expected Behavior The complete component creation form should render. ### Observed Behavior The page renders, however the form is empty. This is due to a bug in the template which attempts to iterate through `form.custom_fields`. For device type components, `custom_fields` is not set. (The exception being raised is apparently swallowed within the template rendering, so our tests never caught it.)
adam added the type: bugstatus: accepted labels 2025-12-29 19:23:33 +01:00
adam closed this issue 2025-12-29 19:23:33 +01:00
adam commented 2025-12-29 19:23:34 +01:00
Author
Owner
Copy Link

@mabroze commented on GitHub (Jul 8, 2021):

Confirmed fixed in 2.11.9. Thanks for the quick resolution and your commitment to NetBox in general @jeremystretch @candlerb. Hope I'll be able to contribute in a meaningful way myself in the future.

@mabroze commented on GitHub (Jul 8, 2021): Confirmed fixed in 2.11.9. Thanks for the quick resolution and your commitment to NetBox in general @jeremystretch @candlerb. Hope I'll be able to contribute in a meaningful way myself in the future.
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 status: accepted 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#5050
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?