mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-07-15 19:24:45 +03:00
Remove the custom Element Web welcome page
Element Web redesigned its welcome page into a built-in component (element-hq/element-web#33211, first released in spring 2026) and no longer falls back to loading welcome.html. The custom page the playbook installed had therefore silently stopped having any effect, and it was a fork of an upstream file that upstream has deleted (its button icon assets are already missing from current Element Web builds). Remove the welcome.html shipping and the variables that only applied to it (matrix_client_element_welcome_headline, _welcome_text, _welcome_logo_link, _page_template_welcome_path), rejecting them in validate_config.yml with pointers to the alternatives. Logo and background customization keep working through Element Web's branding options, which the new welcome page still honors. A fully custom page can be self-hosted and wired via embedded_pages.welcome_url. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,27 @@
|
||||
# 2026-07-14
|
||||
|
||||
## The playbook no longer ships a custom welcome page for Element Web
|
||||
|
||||
Element Web [redesigned its welcome page](https://github.com/element-hq/element-web/pull/33211) (the screen shown at `/#/welcome` before logging in) into a built-in component and no longer loads a custom `welcome.html` file by default. Since the playbook upgraded to an Element Web version containing that change (spring 2026), the custom welcome page the playbook installed (and the variables customizing it) had silently stopped having any effect.
|
||||
|
||||
The playbook now embraces the new upstream behavior and no longer ships its own `welcome.html`. The following variables have been removed and the playbook will let you know if you're still using them: `matrix_client_element_welcome_headline`, `matrix_client_element_welcome_text`, `matrix_client_element_welcome_logo_link` and `matrix_client_element_page_template_welcome_path`.
|
||||
|
||||
Most welcome page customizations keep working, because they go through Element Web's branding configuration, which the new welcome page still honors:
|
||||
|
||||
- a custom logo, via `matrix_client_element_welcome_logo` (or `matrix_client_element_branding_auth_header_logo_url`)
|
||||
- a custom background, via `matrix_client_element_branding_welcome_background_url`
|
||||
|
||||
If you need a fully custom welcome page, you can self-host an HTML page and point Element Web at it, like this:
|
||||
|
||||
```yaml
|
||||
matrix_client_element_configuration_extension_json: |
|
||||
{
|
||||
"embedded_pages": {
|
||||
"welcome_url": "https://example.com/my-welcome.html"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## BorgBackup now includes Synapse's local thumbnails
|
||||
|
||||
For Synapse servers, the built-in [BorgBackup](./docs/configuring-playbook-backup-borg.md) integration no longer excludes the media store's `local_thumbnails` directory from backups.
|
||||
|
||||
Reference in New Issue
Block a user