#22510: Form fields cannot have names that are present as attributes on the form
---------------------------------+--------------------------------------
     Reporter:  gc@…             |                    Owner:  nobody
         Type:  Bug              |                   Status:  closed
    Component:  Forms            |                  Version:  1.7-beta-2
     Severity:  Release blocker  |               Resolution:  fixed
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  1                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+--------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"be733bf672eebb7d03061a293a2b0b03c727ab44"]:
 {{{
 #!CommitTicketReference repository=""
 revision="be733bf672eebb7d03061a293a2b0b03c727ab44"
 [1.7.x] Fixed #22510 -- Harden field removal to only None.

 Refs #8620.

 If we allow any value to remove form fields then we get name clashes
 with method names, media classes etc. There was a backwards
 incompatibility introduced meaning ModelForm subclasses with declared
 fields called media or clean would lose those fields.

 Field removal is now only permitted by using the sentinel value None.
 The docs have been slightly reworded to refer to removal of fields
 rather than shadowing.

 Thanks to gcbirzan for the report and initial patch, and several of the
 core team for opinions.

 Backport of 9fb0f5dddc4cf7f2d294af1bcde2c359cffd90a5 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22510#comment:19>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.d424914811afe90e7f9a6e03affaf7fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to