mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-07-24 18:38:42 +00:00
61091e0027
When a user has a theme in the DB that is not among the themes in the configuration, the following happens to this user's UI: Image: https://codeberg.org/attachments/bf8d4ff1-8216-4df5-ab90-8dc7e03784d9 The workaround is to manually go to Appearance settings and update the theme. This can happen if the theme was removed from the server config. For example, admins don't want to have it anymore. Maybe it even was the default theme, which is being saved in the DB during sign up. It will be useful for Forgejo if we, for example, want to separate colorblind them variants from the actual themes, or if we ever want to remove the Gitea themes. Rel: https://codeberg.org/forgejo/forgejo/pulls/13054. And instance admins will also find it useful to not have to manually update the DB in case they want to get rid of some custom theme. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13110 Reviewed-by: Robert Wolff <mahlzahn@posteo.de> |
||
|---|---|---|
| .. | ||
| setting | ||
| avatar.go | ||
| code.go | ||
| home.go | ||
| home_test.go | ||
| main_test.go | ||
| notification.go | ||
| package.go | ||
| profile.go | ||
| search.go | ||
| stop_watch.go | ||
| task.go | ||