Multiple people on Slack support have asked "how do I fix this error" now, which suggests that the wording here needs improvement...
* change "is obsolete" to "is no longer required", to make it sound less "your code is broken" and more "here's an improvement you can make" (but also state that it'll be removed in a future release, to make it clear that you have to do it soomer or later)
* leave out the full module paths - they're probably coming across as internal tech gobbledegook rather than informative, and obscuring the word "Panel" which is the most important thing in the message
* link to the release note to clear up any remaining confusion
This prevents errors when comments.js is loaded but a view does not use
the commenting functionality, which caused issues for StructBlocks containing
FieldBlocks on non page-models. In future we should only load comments.js
where it is actually needed as well.
This exception has not existed since Willow 0.3. Type checking on the 'except' line only happens when an exception occurs, so most of the time this is harmless, but if an unrelated exception occurs here (such as that caused by a faulty filetype library: https://github.com/h2non/filetype.py/issues/130) the real exception gets masked by an AttributeError for the missing definition.
Fixes#8970. Python 3.7 incorrectly opens the stream for writing in text mode (be6dbfb43b), so work around this by writing the unicode string back rather than encoding back to bytes.
This will probably fail if we're on Windows AND Python 3.7 AND encounter non-ASCII characters (because in that case it'll be open for writing as Windows-1252 encoding), but it's probably the best we can do without abandoning the fileinput library entirely.
In this case, workflow notification emails can't include the full URL (because they're triggered from a signal, where we don't have access to a request object) but we don't want them to break outright.
fixes#8582
* Fix splitting block with highlighted text deleting text
* Fix issue with splitting blocks at start/end crashing editor
* Add unit tests for Draftail split behaviour
Fixes#8190
Django 4 changed the rendering of radio button / checkbox lists to nested divs rather than ul/li - see 5942ab5eb1. This change simply applies the existing li styles to second-level divs.
- using padding meant the icon would visually spin 'wobbly'
- button content is no longer centre aligned so button longrunning active state should not be either
- fixes#8615
- If no panels show (due to permissions) the tab was still showing
- instead it is expected that the tabs should not show at all if empty
- fixes#8593
# Conflicts:
# CHANGELOG.txt
# docs/releases/4.0.md
* Make 'upload one now' link on document chooser work after results refresh
Fixes#8528
Put the initTabs call inside ajaxifyLinks so that it's reapplied when the results container (including the 'no results message') is replaced.
* Make 'create one now' link on task chooser work after results refresh
Fixes#8500. As a consequence of the CSS changes in c6fdb6bbb3, scroll position is no longer reflected in the document element's scrollTop property, but on the `<main>` element instead. As a result, comment positions were not being adjusted for scroll position. To account for this (and any future CSS changes), we walk all ancestor elements to calculate the true scroll position.
Matt Westcott