| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
functions/classes.
Since refs #21489, FormSet classes and factories are exposed on the
django.forms package.
|
| |
|
|
|
|
|
|
|
|
| |
By specifying form_kwargs when instantiating the formset, or overriding
the `get_form_kwargs` method on a formset class, you can pass extra
keyword arguments to the underlying `Form` instances.
Includes tests and documentation update.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
output of formsets.
Thanks velle for the report.
|
| |
|
|
|
|
| |
Thanks bmispelon, kezabelle, jorgecarleitao, and timgraham for reviews.
|
|
|
|
|
|
| |
behavior of formset.save(commit=False).
Thanks django at patjack.co.uk.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is consistent with Python's official documentation
and it's a sphinx recommendation too[1].
[1] http://sphinx-doc.org/markup/desc.html#dir-method
Refs #21855.
|
|
|
|
| |
Thanks gsf for the suggestion.
|
|
|
|
|
| |
Thanks PaulM for the suggestion and Luke Granger-Brown and
Wiktor Kołodziej for the initial patch.
|
|
|
|
|
|
| |
longer deletes objects
Thanks laureline.guerin@ and Wedg.
|
|
|
|
| |
Thanks gregcorey@ for the suggestion.
|
|
|
|
|
|
| |
formsets.
Thanks to frog32 for the report and to Tim Graham for the review.
|
| |
|
| |
|
| |
|
|
|
|
| |
validating max_num.
|
| |
|
|
|
|
| |
Refs #20104.
|
|
|
|
|
|
| |
documentation.
Thanks to feraudyh at yahoo.com for the report.
|
|
|
|
| |
adjusting formsets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
max_num on server.
This is provided as a new "validate_max" formset_factory option defaulting to
False, since the non-validating behavior of max_num is longstanding, and there
is certainly code relying on it. (In fact, even the Django admin relies on it
for the case where there are more existing inlines than the given max_num). It
may be that at some point we want to deprecate validate_max=False and
eventually remove the option, but this commit takes no steps in that direction.
This also fixes the DoS-prevention absolute_max enforcement so that it causes a
form validation error rather than an IndexError, and ensures that absolute_max
is always 1000 more than max_num, to prevent surprising changes in behavior
with max_num close to absolute_max.
Lastly, this commit fixes the previous inconsistency between a regular formset
and a model formset in the precedence of max_num and initial data. Previously
in a regular formset, if the provided initial data was longer than max_num, it
was truncated; in a model formset, all initial forms would be displayed
regardless of max_num. Now regular formsets are the same as model formsets; all
initial forms are displayed, even if more than max_num. (But if validate_max is
True, submitting these forms will result in a "too many forms" validation
error!) This combination of behaviors was chosen to keep the max_num validation
simple and consistent, and avoid silent data loss due to truncation of initial
data.
Thanks to Preston for discussion of the design choices.
|
|
|
|
| |
Thanks Simon Charette for his help on the patch. Refs #16630.
|
|
|
|
|
|
| |
a formset.
This is a security fix. Disclosure and advisory coming shortly.
|
| |
|
|
|
|
| |
Added -n to sphinx builds to catch issues going forward.
|
| |
|
| |
|
|
|
|
| |
for Django 1.3
|
|
|
|
| |
Thanks Florian Apolloner for the patch.
|
|
|
|
| |
1.4 addition.
|
|
|
|
| |
compatibility syntax).
|
|
|
|
|
|
|
|
|
|
|
|
| |
formsets and inline formsets.
This make them consistent with the similar capability of regular
formsets. Thanks to simon29 form the report and to Claude Paroz for the
patch.
Fixes #14574.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17373 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
| |
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16925 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
consistancy with ``Form.has_changed``. Thanks to michelts for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16773 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
you override ``__iter__`` you now need to also override ``__getitem__`` for consistant behavior. Thanks to Carl and Russ for the review.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16770 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
which was broken in [16564]. Thanks to dmclain for pointing out that the original example was correct.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16623 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
teraom.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16564 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
magopian.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16433 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
ORDER fields in formsets. Many thanks to Aleksandra Sendecka.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16430 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
documentation. Thanks DaNmarner. Refs #15635.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15874 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
|
|
| |
Django 1.0 and 1.1
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15055 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
|
|
| |
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14988 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|