#13524: Changes to (model) formsets' max_num sematics not listed in the 1.2 release notes ---------------------------+------------------------------------------------ Reporter: ramiro | Owner: nobody Status: new | Milestone: 1.2 Component: Documentation | Version: 1.1 Keywords: max_num | Stage: Unreviewed Has_patch: 1 | ---------------------------+------------------------------------------------ After a couple of threads in the [http://groups.google.com/group/django- es/browse_thread/thread/790b5887d77496ca/912a1bd79f7c292f django-es] and [http://groups.google.com/group/django- users/browse_thread/thread/e03e65afffd48826?hl=en# django-users] mailing lists (that also gave bith to #13521/r13234) it seemed clear we aren't documenting in the release notes the backward incompatible changes implemented in r12872 that affect usage of formsets, model formsets and admin inlines.
The patch attached tries to fix that. Any help reviewing the language used and fleshing it out with more content especially by people more familiar with the changes implemented in such commits will be greatly appreciated. The patch also: * Moves a note about the admin inlines JS-powered 'Add another' link from the formsets docs to the admin docs because that seem the place where it belongs. It doesn't even belog in the model formsets docs. * Add a few tests and fixes typos to the formsets and model formsets I created when trying to understand and confirm the new behavior. Setting milestone = 1.2. -- Ticket URL: <http://code.djangoproject.com/ticket/13524> Django <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.
