Fixed #11157 -- Stopped removing stop words in admin's prepopulated_fields.

Co-Authored-By: Andy Chosak <andy@chosak.org>
This commit is contained in:
Scott Cranfill 2020-05-20 13:11:30 -04:00 committed by Mariusz Felisiak
parent 922ff51f5a
commit 62f1655a64
6 changed files with 44 additions and 50 deletions

View file

@ -1096,8 +1096,7 @@ subclass::
automatically generate the value for ``SlugField`` fields from one or more
other fields. The generated value is produced by concatenating the values
of the source fields, and then by transforming that result into a valid
slug (e.g. substituting dashes for spaces; lowercasing ASCII letters; and
removing various English stop words such as 'a', 'an', 'as', and similar).
slug (e.g. substituting dashes for spaces and lowercasing ASCII letters).
Prepopulated fields aren't modified by JavaScript after a value has been
saved. It's usually undesired that slugs change (which would cause an
@ -1106,6 +1105,11 @@ subclass::
``prepopulated_fields`` doesn't accept ``DateTimeField``, ``ForeignKey``,
``OneToOneField``, and ``ManyToManyField`` fields.
.. versionchanged:: 3.2
In older versions, various English stop words are removed from
generated values.
.. attribute:: ModelAdmin.preserve_filters
The admin now preserves filters on the list view after creating, editing