| Age | Commit message (Collapse) | Author |
|
This is a security fix. Disclosure following shortly.
Thanks Keryn Knight for the report and initial patch.
|
|
Backport of 0dea81cd6d34b3e41cc4bbec99b5fdf06142b09e from master
|
|
Backport of a7c3d0f288a66d327e71476e9a9bfcc791602b8c from master
|
|
Custom form fields having a `queryset` attribute but no
`limit_choices_to` could no longer be used in ModelForms.
Refs #2445.
Thanks to artscoop for the report.
Backport of bfb11b95626f39e2f5e18d97d7761c6f93dcc1a9 from master.
Conflicts:
django/forms/fields.py
|
|
Thanks Troy Grosfield for the report and Tim Graham for the tests.
Backport of ec2fd02bb3 from master
|
|
Backport of f7eee04ebe from master
|
|
Thanks sebastien at clarisys.fr for the report and gautier
for the patch.
Backport of 5e2c4a4bd1 from master
|
|
Backport of 67f9f385aa from master
|
|
Refs #22950.
Backport of 920904921 from master.
|
|
As far as possible, message evaluation should not happen in field
__init__ (often run at import time).
Backport of cecbb71312a from master.
|
|
Backport of 1dcc603eff from master
|
|
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
|
|
FormSet.min_num and FormSet.extra.
|
|
the admin.
Thanks Stephen Burrows for work on the patch as well.
|
|
Made explicit lack of microsecond handling by built-in datetime form
fields. Used that explicitness to appropriately nix microsecond
values in bound fields. Thanks Claude Paroz for the review.
Backport of a5de0df58 from master.
|
|
Backport of df60db0e78 from master
|
|
Backport of 2bcb8bfc8d from master
|
|
flake8 catches
Backport of 778ce245dd466bce1b19f89e52cf9ed8f1b46513 from master
|
|
Backport of b077ba7ac1 from master
|
|
Thanks Jeroen Pulles for the report and Simon Charette for the review.
|
|
Thanks Anssi Kääriäinen for the idea and Simon Charette for the
review.
|
|
serialization/deserialization step.
Thanks @apollo13 for the suggestion. Refs #17413.
|
|
|
|
Thanks Piotr Kasprzyk for help with the patch.
|
|
Thanks django at patjack.co.uk for the report and the review.
|
|
|
|
Thanks Aymeric Augustin for the suggestion.
|
|
Thanks Igor Mitrenko for the report.
|
|
ForeignKey or ManyToManyField attribute ``limit_choices_to`` can now
be a callable that returns either a ``Q`` object or a dict.
Thanks michael at actrix.gen.nz for the original suggestion.
|
|
Overriding the error messages now works for both unique fields, unique_together
and unique_for_date.
This patch changed the overriding logic to allow customizing NON_FIELD_ERRORS
since previously only fields' errors were customizable.
Refs #20199.
Thanks leahculver for the suggestion.
|
|
This is the result of Christopher Medrela's 2013 Summer of Code project.
Thanks also to Preston Holmes, Tim Graham, Anssi Kääriäinen, Florian
Apolloner, and Alex Gaynor for review notes along the way.
Also: Fixes #8579, fixes #3055, fixes #19844.
|
|
Thanks Tim Graham for the review.
|
|
Thanks orcein at gmail.com for the report.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks dibrovsd at gmail.com for the report and Simon Charette
for the review.
|
|
Refs #20199 #16986.
Thanks @akaariai, @bmispelon, @mjtamlyn, @timgraham for the reviews.
|
|
|
|
|
|
Thanks agale031176@gmail.com for the report.
|
|
Thanks Elec for the report and Simon Charette for the review.
|
|
On Python 3 sorting Fields mixed with GenericForeignKeys doesn't work
as GenericForeignKey isn't a subclass of django.db.models.fields.Field.
Refs #21428.
|
|
The GenericRelation refactoring removed GenericRelations from
model._meta.many_to_many. This had the side effect of disallowing
editable GenericRelations in ModelForms. Editable GenericRelations
aren't officially supported, but if we don't fix this we don't offer any
upgrade path for those who used the ability to set editable=True
in GenericRelation subclass.
Thanks to Trac alias joshcartme for the report and stephencmd and Loic
for working on this issue.
|
|
|
|
attribute
Thanks mitar for the report and Tim Graham for the review.
|
|
|