| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
if obj it None, it's None, there's no need to check it
|
|
|
|
|
|
|
|
|
|
Thanks to Yhal Htet Aung for the translation work.
|
|
Thanks to Xwybylty Soslan for the translation work.
|
|
Polish, Telugu, Georgian, Azerbaijani, Norwegian Bokmål, Basque,
Dutch, Thai, Spanish (Argentina), Afrikaans.
|
|
|
|
BCryptSHA256PasswordHasher pre-hashes the users password using
SHA256 to prevent the 72 byte truncation inherient in the BCrypt
algorithm.
|
|
Updated LogEntry.get_admin_url to use 'reverse' instead
of a hard-coded path.
|
|
The function removeChildren is a general utility that other functions
might want to use.
Fixes #4120. Thanks arvin for the initial patch.
|
|
The cancelEventPropagation function is a general utility function that
can be reused by other widgets. Refs #4120.
|
|
The function quickElement in calendar.js is a duplicate of the
quickElement function in core.js. Refs #4120.
|
|
Fixed #20117 -- Added missing translation override to fix flatpages test.
|
|
The commit of 266de5f9ae9e9f2fbfaec3b7e4b5fb9941967801 included only
tests, this time also code changes included...
|
|
Thanks to the many contributors who updated and improved the patch over
the life of this ticket.
|
|
|
|
Fixed #18000 -- Moved the code to handle goto requests to an extra WizardView method.
|
|
without the need to add them in the as_view call.
|
|
|
|
User models.
Thanks to matiasb for the report of #20060 and the draft patch for #20048.
|
|
This improves rendering in some foreign languages.
|
|
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 to loic84 for the report and patch.
|
|
Thanks martinogden for the initial patch and d1ffuz0r for tests.
|
|
catalanojuan/fix-admin-log-dependency-on-user-id-field-20088
Fixed #20088 -- Changed get_admin_log not to depend on User id field
|
|
Thanks jrothenbuhler for draft patch, Konark Modi for updates.
|
|
Before this change, the get_admin_log method would expect User model's
FK to be named `id`. When changing that FK name, admin/index.html
rendering would fail.
This includes:
* Changed the use of id for the use of pk property.
* Added a regression test that fails without the patch.
This commit refs #20088.
|
|
Thanks to Krzysztof Jurewicz for initial patch and
adupin for tests.
|
|
Thanks Claude and Julien for the review.
|
|
Some alternative implementations don't have them.
Closes #19944.
|
|
|
|
|
|
Thanks slinkp for the report and the initial patch.
|
|
When the 'invalid' error message is set at field level, it masks
the error message raised by the validator, if any.
|
|
Thanks chikiro.spam at gmail.com for the report.
|
|
The sql/query.py add_q method did a lot of where/having tree hacking to
get complex queries to work correctly. The logic was refactored so that
it should be simpler to understand. The new logic should also produce
leaner WHERE conditions.
The changes cascade somewhat, as some other parts of Django (like
add_filter() and WhereNode) expect boolean trees in certain format or
they fail to work. So to fix the add_q() one must fix utils/tree.py,
some things in add_filter(), WhereNode and so on.
This commit also fixed add_filter to see negate clauses up the path.
A query like .exclude(Q(reversefk__in=a_list)) didn't work similarly to
.filter(~Q(reversefk__in=a_list)). The reason for this is that only
the immediate parent negate clauses were seen by add_filter, and thus a
tree like AND: (NOT AND: (AND: condition)) will not be handled
correctly, as there is one intermediary AND node in the tree. The
example tree is generated by .exclude(~Q(reversefk__in=a_list)).
Still, aggregation lost connectors in OR cases, and F() objects and
aggregates in same filter clause caused GROUP BY problems on some
databases.
Fixed #17600, fixed #13198, fixed #17025, fixed #17000, fixed #11293.
|
|
One of these functions didn't exist anymore.
|
|
|
|
Refs #9437.
|
|
|
|
|
|
Since "unless managed" now means "if database-level autocommit",
committing or rolling back doesn't have any effect.
Restored transactional integrity in a few places that relied on
automatically-started transactions with a transitory API.
|
|
Thanks reidpr at lanl.gov for the report.
|