Opened 17 years ago
Closed 16 years ago
#5620 closed (duplicate)
XMLField not working
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Forms | Version: | |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
As described in
http://www.djangoproject.com/documentation/model-api/#xmlfield it
should validate its content with a RelaxNG schema, but it is simply
not working (is this newforms-admin specific?) Its dependency on JING
should also be documented in the model-api document. BTW: why not use
lxml? (http://codespeak.net/lxml/)
Attachments (3)
Change History (8)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
lxml instead of Jing would be nice since Jing seems to be dead and isn't very effective IMHO.
follow-up: 4 comment:3 by , 17 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #3094.
comment:4 by , 16 years ago
Component: | Admin interface → django.newforms |
---|---|
Resolution: | duplicate |
Status: | closed → reopened |
#3094 is about adding other validation methods besides Jing, starting with lxml. This ticket addresses the problem that the Jing-based validation we already have is oldforms-only. XMLField will need to override formfield(), providing a custom newforms.fields.Field subclass that uses core.validators.RelaxNGCompact.
by , 16 years ago
Attachment: | newforms_xmlfield.diff added |
---|
recycles the oldforms XMLField validation for newforms
by , 16 years ago
Attachment: | newforms_xmlfield2.diff added |
---|
by , 16 years ago
Attachment: | newforms_xmlfield.diff3 added |
---|
comment:5 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
Nah, the newforms-admin solution will be to implement #3094; this is still a dup.
Replying to anonymous:
Tried to get that into django, too:
http://code.djangoproject.com/ticket/3094#comment:4