- as of 3.0 - report filters would overflow the viewport in Wagtail
- fix layout issue with form submission lists introduced with filtering changes
- remove invalid css grid-column-start (unused)
- adopt theme variables for all main spacing instead of hard-coded em/rem/px values
- fixes #8929
* Modified route decorator so it adds new route to view depending on pattern type; default to path
* Made a separate decorator
* Renamed route to path and updated RoutablePage models
* Added a check to warn user when using regex with path decorator
* Made @route alias of @re_path, added tests for @re_path
* resolves #7031
In Django 4.0, a search match expression would produce this SQL WHERE
clause:
WHERE ... MATCH (`title`, `body`) AGAINST (query IN BOOLEAN MODE)
In Django 4.1, this behavior was changed:
https://code.djangoproject.com/ticket/32691407fe95cb1
so that instead this SQL WHERE clause is generated, explicitly
filtering against "= True":
WHERE ... MATCH (`title`, `body`) AGAINST (query IN BOOLEAN MODE) = True
This no longer works properly because MATCH returns a floating point
score as a measurement of the match quality, not a boolean value:
https://dev.mysql.com/doc/refman/8.0/en/fulltext-boolean.html
In order for filtering on "= True" to work, this commit changes the
match expression SQL to be:
WHERE ... CASE WHEN MATCH (`title`, `body`) AGAINST (query IN BOOLEAN MODE) THEN True ELSE False END = True
- add id=main to all login flow form templates for non-JS skip link usage
- remove inline script to focus on username field in login form
- adopt a consistent DOM layout for all log in & password reset flow forms
- ensure h1 is at the top of the DOM in all forms
- add wagtail logo to sign in form and document the ability to override it
- fixes #2309
This allows the linked instance to be something that doesn't expose a `.pk` property, like a dict from a DRF response, while keeping the `get_link_url` mechanism
* added a forced-color media query to allow distinct visibiity of disabled buttons
* Also set disabled button border color to GrayText in forced-colors mode
The `button` element was not correctly picking up the same border color as the text, for some reason. This commit fixes that.
