Matt Westcott

Thanks for the report @tbrlpld! I don't recall noticing this before, but a quick check shows that it's been like this since at least 2.11. This style is being defined...

A reduced test case that doesn't depend on anything Wagtail-specific: ``` from bakerydemo.base.models import People from django.contrib.postgres.search import SearchQuery, SearchRank, SearchVector vector = SearchVector("first_name") queryset = People.objects.annotate(vec=vector).order_by(SearchRank(vector, "ava")) print(queryset.query) list(queryset)...

Got it! A test case only using basic SQL functions... ``` from django.db.models.functions import Length, Lower from bakerydemo.base.models import People queryset = People.objects.annotate(lfn=Lower("first_name")).order_by(Length(Lower("first_name"))) print(queryset.query) list(queryset) ```

Bug opened on Django: https://code.djangoproject.com/ticket/34105

Fixed in Django.

Initially I wasn't keen on having a `{% dialog %}` stub embedded into every single instance of a chooser widget - which could add up to a lot of extra...

Hi @dholliday3 - thanks for the report. Have added an ID to the warning in #8780 - will leave the other issue (i.e. whether m2m relations should be considered valid...

@javoweb No, LTS releases will generally only receive updates for stability and security fixes, and this is really too minor for that.

@lb- No, I don't think so. #4122 is about StreamField not handling custom validation errors that are triggered outside of StreamField's own mechanism; this one is about the interaction between...

It should be possible to set this up on any (or all) of your page models by defining a suitable `get_sitemap_urls` method, for example: ``` class MyPage(Page): include_in_sitemap = models.BooleanField()...