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

Fix Longitude Field Validation Issue #11863

New Issue
Closed
opened 2025-12-29 21:50:55 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:50:55 +01:00
Owner
Copy Link

Originally created by @mr1716 on GitHub (Nov 22, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox Edition

NetBox Community

NetBox Version

v4.4.6

Python Version

3.10

Steps to Reproduce

  1. Create a new Device (either through the + on the navigation menu or from the devices page)
  2. Fill out the required fields for a new device
  3. Add in a value of 99.99 for latitude and 888.00 for longitude
  4. create the device

Expected Behavior

The request should fail as it should limit the longitude value to the proper values.

Observed Behavior

It creates the device with the longitude of 888.00000 and doesn’t validate that the data may be inaccurate

Originally created by @mr1716 on GitHub (Nov 22, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox Edition NetBox Community ### NetBox Version v4.4.6 ### Python Version 3.10 ### Steps to Reproduce 1. Create a new Device (either through the + on the navigation menu or from the devices page) 2. Fill out the required fields for a new device 3. Add in a value of 99.99 for latitude and 888.00 for longitude 4. create the device ### Expected Behavior The request should fail as it should limit the longitude value to the proper values. ### Observed Behavior It creates the device with the longitude of 888.00000 and doesn’t validate that the data may be inaccurate
adam added the type: bugstatus: acceptednetboxseverity: low labels 2025-12-29 21:50:55 +01:00
adam closed this issue 2025-12-29 21:50:55 +01:00
adam commented 2025-12-29 21:50:56 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Nov 22, 2025):

This is also an issue when editing devices. Can put in a value if 999 for the longitude.

Found this when utilizing the Devices, but also applies to anywhere else this is used. Such as Sites.

@mr1716 commented on GitHub (Nov 22, 2025): This is also an issue when editing devices. Can put in a value if 999 for the longitude. Found this when utilizing the Devices, but also applies to anywhere else this is used. Such as Sites.
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 severity: low 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#11863
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?