[Bug]: `enforce_theme=default` Disables Browser-Based Dark/Light Mode Detection about server

[bromiesTM]

Exactly, that's why enforcing default should prevent the non-privileged user from switching themes manually while preserving the auto-adjusting functionality based on browser / OS settings.
At least that's what I expected.

[kesselb]

cc @susnux @skjnldsv

[skjnldsv]

Ah, we should just remove default from the example in config.sample.php.
Default is not a valid theme, enforcing it makes zero sense :)

[pandusen]

Ah, we should just remove default from the example in config.sample.php. Default is not a valid theme, enforcing it makes zero sense :) <

Currently it does make sense. It is the only way to force browser based choice of theme. for me, that makes sense, as I am using a custom theme, that is designed to work in dark and light mode.

If I force either dark or light, it will overwrite the theme completely.
If I dont set any value, the users will be able to change the theme.

[skjnldsv]

custom theme as within the themes directory of your Nextcloud root?

[pandusen]

custom theme as within the themes directory of your Nextcloud root?
<

Correct. It used to be that you could just write your theme name "my_theme" directly in "enforce_theme" to apply the theme, and disable user theming. But as always with nextcloud, admin control is slowly getting deprecated.. Now you can only use the build-in themes: dark, dark-highcontrast, default, light, light-highcontrast, opendyslexic. Where default is the current theme.

[skjnldsv]

@pandusen yeah, the custom theming feature you're using is slowly getting deprecated for a few years now.
I would no rely on it on the long run, sorry :)