pull/1457/head
Matt Westcott 2015-06-29 16:59:31 +01:00
rodzic 7d7eece0d1
commit f82f0ddab4
2 zmienionych plików z 5 dodań i 0 usunięć

Wyświetl plik

@ -4,6 +4,7 @@ Changelog
1.1 (xx.xx.xxxx) 1.1 (xx.xx.xxxx)
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
* Implemented the `specific()` method on PageQuerySet, to return pages as their most specific type
* The `{% image %}` tag now supports filters on the image variable, e.g. `{% image primary_img|default:secondary_img width-500 %}` * The `{% image %}` tag now supports filters on the image variable, e.g. `{% image primary_img|default:secondary_img width-500 %}`
* Moved the style guide menu item into the Settings sub-menu * Moved the style guide menu item into the Settings sub-menu
* Search backends can now be specified by module (e.g. `wagtail.wagtailsearch.backends.elasticsearch`), rather than a specific class (`wagtail.wagtailsearch.backends.elasticsearch.ElasticSearch`) * Search backends can now be specified by module (e.g. `wagtail.wagtailsearch.backends.elasticsearch`), rather than a specific class (`wagtail.wagtailsearch.backends.elasticsearch.ElasticSearch`)

Wyświetl plik

@ -10,6 +10,10 @@ Wagtail 1.1 release notes - IN DEVELOPMENT
What's new What's new
========== ==========
``specific()`` method on PageQuerySet
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Usually, an operation that retrieves a queryset of pages (such as ``homepage.get_children()``) will return them as basic Page instances, which only include the core page data such as title. The ``specific()`` method (e.g. ``homepage.get_children().specific()``) now allows them to be retrieved as their most specific type, using the minimum number of queries.
Minor features Minor features
~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~