#25532: JSONField form field double encodes invalid values
-------------------------------------+-------------------------------------
     Reporter:  davidszotten         |                    Owner:  Claude
                                     |  Paroz <claude@…>
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.postgres     |                  Version:  1.9
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"3744fc1666c41aeb4ed44f31605bafdb413b42bc" 3744fc1]:
 {{{
 #!CommitTicketReference repository=""
 revision="3744fc1666c41aeb4ed44f31605bafdb413b42bc"
 [1.10.x] Fixed #26917 -- Fixed crash in disabled ModelChoiceFields.

 Partially reverted refs #25532 to fix a regression in Django 1.10.
 This reintroduces a crash for disabled forms.JSONField (refs #26949),
 however, that issue is also present on Django 1.9.

 Thanks Ryan Schave for the test.

 Backport of a5f85d891b51d7ceb4f9e422e3e4f5c741062288 from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.05ca12a82b7a69d14d8ef72e1a5d01bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to