When the urlify util is used, ensure that we pass in the allow unicode value correctly in the SlugController.
Note: This was passed in for slugify but the usage of slugify, not urlify.
Fixes #11828
- Use a maximum of 3 workers
- Use the new generate_rendition_instance() method
- Define and execute future threads in a way that allows exceptions to be surfaced (avoid map)
Ensure that the non-prefixed settings for customised password required templates can be name-spaced like all other current settings.
Add backwards compatible deprecation support and warnings for the current names.
Fixes #11368
PASSWORD_REQUIRED_TEMPLATE -> WAGTAIL_PASSWORD_REQUIRED_TEMPLATE
DOCUMENT_PASSWORD_REQUIRED_TEMPLATE -> WAGTAILDOCS_PASSWORD_REQUIRED_TEMPLATE
* Accept alias for WAGTAILIMAGES_RENDITION_STORAGE
* Update wagtail.images.models.get_rendition_storage to handle the case when the WAGTAILIMAGES_RENDITION_STORAGE setting is given a storage alias (defined in the STORAGES setting). Preserve old behavior when a dotted module path or a Storage instance are given.
* Refactor and improve all tests related to the WAGTAILIMAGE_RENDITION_STORAGE setting.
* Update related documentation.
Whilst ideally we wouldn't use the secret key, it's the best way to ensure the value doesn't expose the wagtail version, whilst still being deployment-specific.
The new settings introduced in #11582 / #11536 only considered one use case of disabling the shared password option. However, we may want to allow for more complex configuration in the future in this area.
Ensure we can support potential future requirements such as #11640 with a more flexible structure for private pages & collections.
The following settings have been changed from boolean to dictionary values.
WAGTAIL_ALLOW_SHARED_PASSWORD_PAGE -> WAGTAIL_PRIVATE_PAGE_OPTIONS
WAGTAIL_ALLOW_SHARED_PASSWORD_COLLECTION -> WAGTAILDOCS_PRIVATE_COLLECTION_OPTIONS
