Fixes#9010. `wagtail.documents.widgets` is no longer reliably imported on startup now that the chooser widget is constructed within wagtail.documents.views.chooser instead, so the telepath adapter wasn't getting register. This meant that DocumentChooserBlocks in StreamField were using the base chooser implementation, which didn't include customisations such as populating the title field from the file upload field. Fix this by making ChooserViewSet responsible for registering the telepath adapter.
Fixes#8989. The previous fix#9004 failed for custom document models because ChooserViewset assigns an internal name for the ChooserBlock class based on the model name, and if this is anything other than Document it won't match the name DocumentChooserBlock that it's exposed under in wagtail.documents.blocks. Fix this by replacing the `block_class` property with a `get_block_class` method that lets us specify the class name. As a bonus, user code that defines chooser blocks no longer has to directly hack the `__module__` attribute.
- fix some broken refs that were lost in the migration to markdown files
- use lower_snake_case for all internal refs (most follow this convention)
- release process sub-section in docs should be named release schedule instead
- Use inline code for `Locale` and `TranslatableMixin` headers to be consistent with other classes in the page
- Move `locale` and `translation_key` of `TranslatableMixin` to its own "Database fields" section
- Add missing periods in Page.update_aliases parameter description
* 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
- Use a setting called WAGTAILADMIN_USER_PASSWORD_RESET_FORM to allow
users to specify a custom form for use in PasswordResetView
- Add an extra_fields property so that fields other than the
mandatory email field can be easily rendered in the template.
- Add extra blocks to the default template to allow users to
easily add their own stuff.
- Render extra fields in the template like we're doing in the
login template.
- apply general fixes to existing markdown documentation
- various cases of rst syntax still used
- update some links to be the new format
- clean up line breaks (prettier)
Matt Westcott