#7682: edit_inline issues error(s) incorrectly when going from revision 7710 to
TRUNK
--------------------------------------+-------------------------------------
Reporter: jleingang | Owner: mtredinnick
Status: new | Milestone:
Component: Admin interface | Version: SVN
Resolution: | Keywords: edit_inline validation
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by Karen Tracey <[EMAIL PROTECTED]>):
* has_patch: 0 => 1
Comment:
So I probably overstated how soon nfa needs to land to make this
worthwhile fixing, but I'm impatient for that merge to happen and a bit at
a loss to know how to help it along. FWIW the oneliner change (which I've
attached as a patch) posted by puyb fixes the case I tracked down and
allows me to freely switch my own app (which uses inlines and non-default-
named ID fields, which caused a different error when the validator was
attached to the hidden fields) between nfa and trunk admin as I've been
doing for testing purposes for the last several months. It seems harmless
but I'll admit it's in code that I've assiduously avoided learning
anything about since it's supposed to be going away real soon now.
--
Ticket URL: <http://code.djangoproject.com/ticket/7682#comment:7>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
