Re: [Django] #35876: Non-ASCII fieldset names are not displayed in the admin

23 views
Skip to first unread message

Django

unread,
Oct 31, 2024, 1:37:55 AM10/31/24
to django-...@googlegroups.com
#35876: Non-ASCII fieldset names are not displayed in the admin
-------------------------------------+-------------------------------------
Reporter: Namhong Kim | Owner: Sarah
| Boyce
Type: Bug | Status: assigned
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

* stage: Accepted => Ready for checkin

--
Ticket URL: <https://code.djangoproject.com/ticket/35876#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Oct 31, 2024, 1:38:17 AM10/31/24
to django-...@googlegroups.com
#35876: Non-ASCII fieldset names are not displayed in the admin
-------------------------------------+-------------------------------------
Reporter: Namhong Kim | Owner: Sarah
| Boyce
Type: Bug | Status: closed
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

* resolution: => fixed
* status: assigned => closed

Comment:

In [changeset:"2c029c718f45341cdd43ee094c24488743c633e6" 2c029c71]:
{{{#!CommitTicketReference repository=""
revision="2c029c718f45341cdd43ee094c24488743c633e6"
Fixed #35876 -- Displayed non-ASCII fieldset names when rendering
ModelAdmin.fieldsets.

Thank you to Namhong Kim for the report, and to Mariusz Felisiak and
Marijke Luttekes for the review.

Regression in 01ed59f753139afb514170ee7f7384c155ecbc2d.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35876#comment:5>

Django

unread,
Oct 31, 2024, 1:42:21 AM10/31/24
to django-...@googlegroups.com
#35876: Non-ASCII fieldset names are not displayed in the admin
-------------------------------------+-------------------------------------
Reporter: Namhong Kim | Owner: Sarah
| Boyce
Type: Bug | Status: closed
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

In [changeset:"9fa2d235c9b3ca6b0cd56e06456bf73d02814a8f" 9fa2d23]:
{{{#!CommitTicketReference repository=""
revision="9fa2d235c9b3ca6b0cd56e06456bf73d02814a8f"
[5.1.x] Fixed #35876 -- Displayed non-ASCII fieldset names when rendering
ModelAdmin.fieldsets.

Thank you to Namhong Kim for the report, and to Mariusz Felisiak and
Marijke Luttekes for the review.

Regression in 01ed59f753139afb514170ee7f7384c155ecbc2d.

Backport of 2c029c718f45341cdd43ee094c24488743c633e6 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35876#comment:6>

Django

unread,
Oct 31, 2024, 4:52:46 AM10/31/24
to django-...@googlegroups.com
#35876: Non-ASCII fieldset names are not displayed in the admin
-------------------------------------+-------------------------------------
Reporter: Namhong Kim | Owner: Sarah
| Boyce
Type: Bug | Status: closed
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Namhong Kim):

Thank you, Sarah Boyce
--
Ticket URL: <https://code.djangoproject.com/ticket/35876#comment:7>
Reply all
Reply to author
Forward
0 new messages