kopia lustrzana https://github.com/wagtail/wagtail
Release note for #1815
rodzic
928bc0d25f
commit
0bb4bac2bc
|
@ -7,6 +7,7 @@ Changelog
|
|||
* Core templatetags (pageurl, image, wagtailuserbar, etc) are now compatible with Jinja2
|
||||
* Image and document models now provide a `search` method on their QuerySets
|
||||
* Search methods now accept an `operator` argument to determine whether multiple terms are ORed or ANDed together
|
||||
* Search methods now accept an `order_by_relevance` argument, which can be set to False to preserve the original QuerySet ordering
|
||||
* InlinePanel now accepts `max_num` and `min_num` arguments to limit the number of inline items
|
||||
* 'Add' button on inline panels is disabled when `max_num` is reached (Salvador Faria)
|
||||
* WagtailRedirectMiddleware can now ignore the query string if there is no redirect that exactly matches it (Michael Cordover)
|
||||
|
|
|
@ -21,7 +21,10 @@ See: :doc:`/advanced_topics/jinja2`
|
|||
Search API improvements
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Wagtail's image and document models now provide a ``search`` method on their QuerySets, making it easy to perform searches on filtered data sets. In addition, search methods now accept an ``operator`` keyword argument, to determine whether multiple search terms will be treated as 'or' (any term may match) or 'and' (all terms must match).
|
||||
Wagtail's image and document models now provide a ``search`` method on their QuerySets, making it easy to perform searches on filtered data sets. In addition, search methods now accept two new keyword arguments:
|
||||
|
||||
* ``operator``, to determine whether multiple search terms will be treated as 'or' (any term may match) or 'and' (all terms must match);
|
||||
* ``order_by_relevance``, set to True (the default) to order by relevance or False to preserve the QuerySet's original ordering.
|
||||
|
||||
See: :ref:`wagtailsearch_searching`
|
||||
|
||||
|
|
Ładowanie…
Reference in New Issue