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

Extend default MIME type for export templates to specify UTF-8 #7812

New Issue
Closed
opened 2025-12-29 20:28:31 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:28:31 +01:00
Owner
Copy Link

Originally created by @gdprdatasubect on GitHub (Mar 30, 2023).

Originally assigned to: @gdprdatasubect on GitHub.

NetBox version

v3.4.7

Python version

3.8

Steps to Reproduce

  1. Create an object where the name contains UTF8-Characters (E.g. a device containing é )
  2. Create a custom Export templates that accesses said object names (E.g.: {%for device in queryset%}{{device.name}}{%endfor%}
  3. Use the Export template on previously created objects

Expected Behavior

Same as with "Current View" and "All Data (CSV)", there it works just fine:
grafik

Observed Behavior

grafik
Characters get mangled up

Originally created by @gdprdatasubect on GitHub (Mar 30, 2023). Originally assigned to: @gdprdatasubect on GitHub. ### NetBox version v3.4.7 ### Python version 3.8 ### Steps to Reproduce 1. Create an object where the name contains UTF8-Characters (E.g. a device containing é ) 2. Create a custom Export templates that accesses said object names (E.g.: `{%for device in queryset%}{{device.name}}{%endfor%} ` 3. Use the Export template on previously created objects ### Expected Behavior Same as with "Current View" and "All Data (CSV)", there it works just fine: ![grafik](https://user-images.githubusercontent.com/101808236/228752851-a76b31c3-22af-43a4-ac75-f71f2c88101d.png) ### Observed Behavior ![grafik](https://user-images.githubusercontent.com/101808236/228752734-b7b39be5-054c-4542-9620-9e29ea0dd9bf.png) Characters get mangled up
adam added the status: acceptedtype: feature labels 2025-12-29 20:28:31 +01:00
adam closed this issue 2025-12-29 20:28:31 +01:00
adam commented 2025-12-29 20:28:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2023):

This doesn't happen for me; the content comes through as expected. However I suspect this is occurring because the default MIME type for an export template is text/plain. Try setting this to text/plain; charset=utf-8 in your export template.

@jeremystretch commented on GitHub (Mar 30, 2023): This doesn't happen for me; the content comes through as expected. However I suspect this is occurring because the default MIME type for an export template is `text/plain`. Try setting this to `text/plain; charset=utf-8` in your export template.
adam commented 2025-12-29 20:28:32 +01:00
Author
Owner
Copy Link

@gdprdatasubect commented on GitHub (Mar 30, 2023):

Yes, selecting the charset explicitly helped, thanks :)
Should this maybe set as default value?
I can also offer to clarify the documentation if you want…

@gdprdatasubect commented on GitHub (Mar 30, 2023): Yes, selecting the charset explicitly helped, thanks :) Should this maybe set as default value? I can also offer to clarify the documentation if you want…
adam commented 2025-12-29 20:28:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2023):

I can't think of a reason not to change the default MIME type to text/plain; charset=utf-8.

@jeremystretch commented on GitHub (Mar 30, 2023): I can't think of a reason _not_ to change the default MIME type to `text/plain; charset=utf-8`.
adam commented 2025-12-29 20:28:32 +01:00
Author
Owner
Copy Link

@gdprdatasubect commented on GitHub (Mar 30, 2023):

Can you assign me to this? Then i could add a pull request to change netbox/extras/models/models.py

@gdprdatasubect commented on GitHub (Mar 30, 2023): Can you assign me to this? Then i could add a pull request to change `netbox/extras/models/models.py`
adam commented 2025-12-29 20:28:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2023):

Thanks @gdprdatasubect! I've reclassified this as an enhancement just because I think it's slightly more accurate relative to existing behavior, though admittedly it's a gray area.

@jeremystretch commented on GitHub (Mar 30, 2023): Thanks @gdprdatasubect! I've reclassified this as an enhancement just because I think it's _slightly_ more accurate relative to existing behavior, though admittedly it's a gray area.
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: feature
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#7812
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?