Opened 8 years ago

Closed 8 years ago

Last modified 5 years ago

#8151 closed (fixed)

UnicodeDecodeError from /django/contrib/admin/ in save_change

Reported by: kmtracey Owned by: nobody
Component: contrib.admin Version: master
Severity: Keywords:
Cc: eallik@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


As reported here:

The failing line of code in the dpaste traceback is:

File "/home/rime/www/tammeoue/packages/django/contrib/admin/" in save_change
  431.         msg = _('The %(name)s "%(obj)s" was changed successfully.') % {'name': force_unicode(opts.verbose_name), 'obj': new_object}

This is similar to #7992/#8016 -- some code that moved from django/contrib/admin/views/ in old admin to django/contrib/admin/ in newforms-admin was missed when the Unicode changes were merged from trunk to newforms-admin. The corresponding line of code in pre-NFA ( is:

            msg = _('The %(name)s "%(obj)s" was changed successfully.') % {'name': force_unicode(opts.verbose_name), 'obj': force_unicode(new_object)}

That is, there is a force_unicode around the new_object as well as opts.verbose_name. It's probably worth a closer look to see if any other places have been missed; I'll do this when I get a chance but don't wait on me to fix it if someone else gets to it first.

Change History (7)

comment:1 Changed 8 years ago by Karen Tracey <kmtracey@…>

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

#8153 reports the same problem and includes a patch that catches one more instance of missing force_unicode wrapper.

comment:2 Changed 8 years ago by RaceCondition

  • Cc eallik@… added

comment:3 Changed 8 years ago by mtredinnick

(In [8236]) Added a few force_unicode() calls around objects in the admin. Required for
Python 2.3 compatibility. Patch from nfg.

Refs #8151, #8153.

comment:4 Changed 8 years ago by jacob

  • Triage Stage changed from Unreviewed to Accepted

comment:5 Changed 8 years ago by julien

  • Resolution set to fixed
  • Status changed from new to closed

I'm not sure why this ticket was reopened. Probably a mistake. It seems that the reported issue has been fixed in [8236].

comment:6 Changed 8 years ago by julien

Correction: it was not reopened, but it hadn't been closed (as I guessed it should have been).

comment:7 Changed 5 years ago by jacob

  • milestone 1.0 deleted

Milestone 1.0 deleted

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