25da9fb81e
Fix empty admin search on Elasticsearch (backport to 5.2)
...
Backport of #11626 to 5.2; fixes #11600
2024-02-18 14:22:44 +10:00
5ad59c1a1a
Fix crash when accessing workflow reports with a deleted snippet
...
This can happen if the model does not define GenericRelations correctly
2024-02-06 12:53:18 +00:00
1e47194d74
Reduce queries in workflow reports
2024-02-06 12:50:13 +00:00
3187374df1
Fix pagination links on history and usage views ( #11579 )
...
Fixes #11569
Override `get_index_url` to point to the listing's own URL, so that BaseListingView uses this to generate pagination links.
2024-02-05 14:16:54 +00:00
da31733b93
Resolve error when specifying 'slug' as a read-only field ( #11447 )
2024-02-01 16:28:03 +00:00
222cf7de72
Fill in release date for 5.2.3
2024-01-23 15:17:24 +00:00
aa731d6a7c
Add 5.2.3 to releases index
2024-01-05 08:16:26 +00:00
4374ab4e3e
Version bump to 5.2.3
2024-01-05 08:16:01 +00:00
e9dbe412c6
Add release notes for #11406
2024-01-05 08:07:23 +00:00
24ad8d40dd
Fix FormSubmissionsPanel on Django 5.0 when creating a new form page
...
Fixes #11405
Django 5.0 rejects `FormSubmission.objects.filter(page=page)` when `page` is an unsaved in-memory instance. Since these can clearly not have any submissions, return an empty queryset in this case.
Also add end-to-end tests for the create and edit views with FormSubmissionsPanel in place.
2024-01-05 08:06:27 +00:00
d7c1345fa1
Bump telepath to 0.3.1
...
This ensures that people upgrading to Django 5.0 will have a compatible version. Now that Python <3.8 and Django <3.2 are EOL, there's no reason for anyone to be running an older version.
# Conflicts:
# setup.py
2023-12-13 06:41:25 +10:00
5dd4315caa
Fix incorrect heading for Django 5.0 support in release notes
2023-12-07 12:10:51 +00:00
018409b2bf
Add note about Django 5.0 support added in a patch release
2023-12-07 11:36:23 +00:00
a44e442656
Fill in release date for 5.2.2
2023-12-06 17:04:58 +00:00
ebb942fa0c
Version bump to 5.2.2
2023-12-06 17:01:47 +00:00
806590c237
Fetch new translations from Transifex
2023-12-06 16:27:15 +00:00
1fc14d12e1
End tag typo fix
...
Documentation typo. ¯\_(ツ)_/¯
2023-12-06 16:00:43 +00:00
0571c5e346
Fix issue aging pages report export if last_published_by is blank
...
Fixes #10821
2023-12-06 16:00:07 +00:00
caf68095b1
Add `display inline-block` to the Comment Control's wrapped ToolbarButton
2023-12-06 15:51:58 +00:00
514f24c51d
Formalise Django 5.0 support
2023-12-06 11:56:22 +00:00
f69f0b5e4a
Changelog for #11308 in 5.2.2
2023-12-06 08:09:12 +10:00
a3173408df
Make recommendations to add GenericRelation in snippets more explicit
2023-12-06 08:08:16 +10:00
be3bf4e4d2
Add more tests to ensure WorkflowState and Revision cascade on object delete
...
# Conflicts:
# wagtail/tests/test_revision_model.py
2023-12-06 08:08:14 +10:00
e89c1f5292
Reduce queries in WorkflowObjectsToModeratePanel by adding workflow_state to select_related
2023-12-06 08:07:52 +10:00
e964a2b0fc
Ensure workflow dashboard panels work when the page/snippet is missing
2023-12-06 08:07:52 +10:00
c26e0326a2
Fix alias() not compatible with specific()
...
Fixes #11285
# Conflicts:
# CHANGELOG.txt
# docs/releases/6.0.md
2023-12-06 08:07:50 +10:00
8e5ab4aeb4
linting fix
2023-11-27 11:53:45 +00:00
9efed6a8f2
Release note for #11262 in 5.2.2
2023-11-27 11:38:44 +00:00
a97403c465
Fix `get_valid_recipients` and `get_recipient_users` returning None
2023-11-27 11:37:16 +00:00
cae85c7dc5
Add failing tests (for missing user on Workflow actions)
2023-11-27 11:37:05 +00:00
bc4f04067a
Fix snippets index.html to use results_template_name for results #11231
...
Until now, if you've set an index_results_template_name or used the
namespaced template-lookup to override it, it was only used for the
ajax-results.
The include is now similar to wagtailadmin/generic/index.html.
# Conflicts:
# CHANGELOG.txt
# docs/releases/6.0.md
2023-11-27 11:26:21 +10:00
394c32c9a0
Fix issue with image focal point removal not working #11256
...
Ensure we define jcropapi, fixing javascript TypeError.
Fixes #11254
# Conflicts:
# CHANGELOG.txt
# docs/releases/6.0.md
2023-11-22 08:28:38 +10:00
45a89a9e34
Change light theme floating toolbar active color ( #11261 )
...
Co-authored-by: Cassidy <cassidy.pittman@torchbox.com>
2023-11-20 12:54:06 +00:00
3acf68524f
Add release notes for v5.2.2
2023-11-20 12:53:21 +00:00
f5242bd015
Version bump to 5.2.1
2023-11-16 14:42:42 +00:00
3868a358b7
Fill in release date for 5.2.1
2023-11-16 14:30:49 +00:00
b22ad48816
Fetch new translations from Transifex
2023-11-16 14:29:35 +00:00
c001335e71
Prevent error on locked pages report when a user has locked multiple pages ( #11245 )
...
Fixes #10960 . Thanks to @richie-blake and @rohitsrma for reporting / investigation.
2023-11-16 14:18:04 +00:00
e8ff6a2fa3
Restore the ability to have content type facets when searching pages with an empty query ( #11243 )
2023-11-16 13:24:03 +00:00
36f1c05a59
Check for ContentType and Permission models before migration ( #11184 )
...
This prevents `create_extra_permissions` from querying or creating
ContentType or Permission objects if the models cannot be found.
When using multiple databases which do not have the auth_permission
table `create_extra_permissions` will cause migrate to fail.
This is similar to https://code.djangoproject.com/ticket/24075 .
Thanks to @crccheck for additional bug reporting.
2023-11-16 13:17:20 +00:00
9933bb61e9
Release note for #11216 / #11234 in 5.2.1
2023-11-15 13:17:07 +00:00
ccf4227af1
Don't add _all_text fields to remapped_fields if explicit fields are specified
...
Also fix previously-masked issues with _compile_fuzzy_query - pass field boost, and use field_name as key instead of the Field object
2023-11-15 13:13:59 +00:00
1e964c1a22
Initialise individual Fields with the correct boost values
2023-11-15 13:13:59 +00:00
947c1c3491
Move ES5->ES6 remapped_field tweaks out of __init__ and into _remap_fields
2023-11-15 13:13:59 +00:00
8e65ff5b0a
Split out a _remap_fields method
2023-11-15 13:13:59 +00:00
a1bde7ef6c
Use a 'boost' field in match query clauses instead of "foo^2" notation
...
The latter notation is only valid within multi_match clauses: compare https://www.elastic.co/guide/en/elasticsearch/reference/8.11/query-dsl-multi-match-query.html#field-boost versus https://www.elastic.co/guide/en/elasticsearch/reference/8.11/query-dsl-match-query.html#match-field-params
2023-11-15 13:13:59 +00:00
f917c0dc53
Make field_name_with_boost a property of the Field object rather than having a get_boosted_fields helper function
2023-11-15 13:13:59 +00:00
4e6575e4c4
Only consider subclasses of the currently-queried model when compiling unique_boosts
...
At indexing time, any SearchFields with a boost value assigned are copied to an index field named "_all_text_boost_{value}". Then, when querying, we compile a list of all such index fields and query on those fields, with the relevant boost applied to each one.
Previously, "all such index fields" was obtained by looking at distinct boost values across all indexed models. However, we only really need to consider models that can actually appear in the results - i.e. are subclasses of self.queryset.model. If a boost value does not appear among this set of models, then these models will never contribute anything to that "_all_text_boost_{value}" index field, and so it's pointless to query it.
2023-11-15 13:13:59 +00:00
4c057f0069
Use doseq=True when re-encoding query params in set_query_params
...
Otherwise, the list of values will be stringified and then URL encoded, resulting in something like locale=%5B%27en%27%5D
From parse_qs docs: Use the urllib.parse.urlencode() function (with the doseq parameter set to True) to convert such dictionaries into query strings.
2023-11-14 15:41:47 +00:00
7194b6c837
Release note for #11223 in 5.2.1
2023-11-14 12:09:56 +00:00
Matt Westcott