#27183: JSONField improperly escaped in admin interface during normal usage
-------------------------------+--------------------------------------
Reporter: sjuxax | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by sjuxax):
It should be noted that I am also using Mezzanine and seeing this issue
through Mezzanine's admin interface, though I haven't found this issue to
exist in Mezzanine's code -- as I said, the fix that's working for me is
in contrib/postgres/forms/jsonb.py. I haven't tested non-Mezzanine. I'm
using PgSQL 9.5.4, Django 1.10.1, Mezzanine git head (06b3df5380a5a),
Python 3.5.2.
Steps to reproduce: create a django.contrib.postgres.fields.JSONField in a
model. Migrate. Make sure the model is registered for admin. Load up the
admin. Input valid JSON into the JSONField and save. Open the newly-added
record in the admin. Observe that the JSONField is improperly escaped.
--
Ticket URL: <https://code.djangoproject.com/ticket/27183#comment:3>
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/064.2174e8038f5309a017e32c9e26c92824%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
