Stable/1.13.x #14
Open
Stable/1.13.x #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mbiguity Thanks to @rifuso for the suggestion!
…resql backend doesn't support it Fixes #3899 - thanks @sivictorallen for the report!
Also remove tr_TR translations, as they will mask the more-complete TR translation due to #3600.
Fixes #3967 If there was no site configured, the listing views in the API would break with an AttributeError. Now, the following happens if there is no site record: - In the Admin API, all pages are returned but links in the response do not include a domain name - In the Public API, no pages are returned
When all pages on a site is private, the last_mods set will be empty causing a crash when trying to get the max value from it. This fix adds a test that the set is truthy (not empty) before calling max.
It appears that the bug may have reappeared in 5.5 final. Fixes #3985
…list bug addressed by #3957
…n filtering by __in with a subquery This ensures that it will work equivalently for lists (as returned when connection.features.can_use_chunked_reads is False) as for iterators, and means we don't need to worry about missing results if we ever receive a chunked resultset.
…avis test matrix We now know that sqlite vs postgresql is a meaningfully different code path for our ES5 tests, so they warrant separate test runs more than py3.5 versus py3.6 does...
…boost values It's valid for the same field to exist as both a SearchField and FilterField, and in this case get_boost would randomly find the FilterField and try (and fail) to read its 'boost' attribute.
Documentation for elasticsearch client suggests to pass arguments into exists_alias as keyword arguments: http://elasticsearch-py.readthedocs.io/en/6.0.0/api.html#elasticsearch.client.IndicesClient.exists_alias They changed order of arguments at least once: * https://github.com/elastic/elasticsearch-py/blob/1.6.0/elasticsearch/client/indices.py#L378 * https://github.com/elastic/elasticsearch-py/blob/1.7.0/elasticsearch/client/indices.py#L385 This is also fixes support for `ATOMIC_REBUILD`.
…s in their representation Calling `repr()` on a model instance that has non-ASCII characters in its string representation returns a UTF8-encoded bytestring that includes that representation. This cannot be substituted into a `unicode` string, since Python will attempt and fail to decode it with the `ascii` codec.
…dation error Fixes #4548
It contains a critical bug that breaks Wagtail: https://bugs.launchpad.net/beautifulsoup/+bug/1784408
Conflicts: CHANGELOG.txt docs/releases/index.rst
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for contributing to Wagtail! 🎉
Before submitting, please review the contributor guidelines https://docs.wagtail.io/en/latest/contributing/index.html and check the following:
make lintfrom the Wagtail root)