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

Multiedit of custom JSON fields injects escaping #7639

New Issue
Closed
opened 2025-12-29 20:26:21 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:26:21 +01:00
Owner
Copy Link

Originally created by @paulexyz on GitHub (Feb 14, 2023).

NetBox version

v3.4.4
(newer versionsnot yet tested, but to my knowledge this is not yet fixed)

Python version

Docker image: netboxcommunity/netbox

Steps to Reproduce

  1. Create a custom field with the type json
  2. Select and edit more than one entity having that field
  3. populate the field with valid json

Expected Behavior

Json should be saved to each entities custom field

{
    "a": "foo",
    "b": "bar"
}

Observed Behavior

Json gets escaped and then saved to each enity

"{\n    \"a\": \"foo\",\n    \"b\": \"bar\"\n}"
Originally created by @paulexyz on GitHub (Feb 14, 2023). ### NetBox version v3.4.4 (newer versionsnot yet tested, but to my knowledge this is not yet fixed) ### Python version Docker image: netboxcommunity/netbox ### Steps to Reproduce 1. Create a custom field with the type json 2. Select and edit more than one entity having that field 3. populate the field with valid json ### Expected Behavior Json should be saved to each entities custom field ```json { "a": "foo", "b": "bar" } ``` ### Observed Behavior Json gets escaped and then saved to each enity ``` "{\n \"a\": \"foo\",\n \"b\": \"bar\"\n}" ```
adam closed this issue 2025-12-29 20:26:21 +01:00
adam commented 2025-12-29 20:26:21 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Feb 15, 2023):

I cannot replicate this. Please revise your steps to allow other people to replicate it.

@kkthxbye-code commented on GitHub (Feb 15, 2023): I cannot replicate this. Please revise your steps to allow other people to replicate it.
adam commented 2025-12-29 20:26:22 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Feb 20, 2023):

Closing this as there has been no response and I wasn't able to replicate it.

@kkthxbye-code commented on GitHub (Feb 20, 2023): Closing this as there has been no response and I wasn't able to replicate it.
adam commented 2025-12-29 20:26:22 +01:00
Author
Owner
Copy Link

@paulexyz commented on GitHub (Mar 17, 2023):

Sorry it was a bug which was fixed in v3.4.x, I must have tested it in the wrong development instance. Yes I can confirm the bug is not present anymore.

@paulexyz commented on GitHub (Mar 17, 2023): Sorry it was a bug which was fixed in v3.4.x, I must have tested it in the wrong development instance. Yes I can confirm the bug is not present anymore.
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
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#7639
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?