Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#11888 closed (worksforme)

Unable to render file name with special chars (non-ascii)

Reported by: rjc Owned by: nobody
Component: contrib.admin Version: 1.1
Severity: Keywords: file unicode
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: yes Patch needs improvement: no
Easy pickings: no UI/UX: no


File field render in admin doesn't support non-ascii. It doesn't even render the anchor, given no error.

Attachments (1)

t11888_r11366.patch (766 bytes) - added by rjc 9 years ago.
patch against v1.1 (r11366)

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by rjc

Attachment: t11888_r11366.patch added

patch against v1.1 (r11366)

comment:1 Changed 9 years ago by Jacob

milestone: 1.2
Triage Stage: UnreviewedAccepted

comment:2 Changed 9 years ago by Karen Tracey

Needs tests: set

comment:3 Changed 9 years ago by Karen Tracey

Resolution: worksforme
Status: newclosed

I can't recreate a problem here. Using trunk r12678 I:

Created an object in admin. The object has a file field, and I specified a file named 'unicode汉汉.txt' for upload during creation.

Selected "Save and continue editing". Admin presented the edit page for the newly-created object. The file field widget then includes a link to the current file, which I can click and then be taken to a new page showing the file contents.

This happened to be on Apache/mod_wsgi. I need more details of the failing case to understand what the reported problem here might be.

comment:4 Changed 7 years ago by Jacob

milestone: 1.2

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top