github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 19:47:47 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Theme change is not saved #1849

New Issue
Closed
opened 2026-03-22 13:41:25 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-03-22 13:41:25 -05:00
Owner
Copy Link

Originally created by @JBMEIZO on GitHub (Feb 16, 2023).

Description

As soon as I change the color scheme from light to dark under the settings for my user, the color scheme changes as desired and the entire frontend is displayed dark.
After I logout and reload the page in my browser the color scheme adjustment is back to the old state. The settings in the profile regarding the color scheme are not saved.

Vikunja Frontend Version

0.20.3

Vikunja API Version

0.20.2

Browser and version

Brave: Version 1.48.164 Chromium: 110.0.5481.100

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @JBMEIZO on GitHub (Feb 16, 2023). ### Description As soon as I change the color scheme from light to dark under the settings for my user, the color scheme changes as desired and the entire frontend is displayed dark. After I logout and reload the page in my browser the color scheme adjustment is back to the old state. The settings in the profile regarding the color scheme are not saved. ### Vikunja Frontend Version 0.20.3 ### Vikunja API Version 0.20.2 ### Browser and version Brave: Version 1.48.164 Chromium: 110.0.5481.100 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:41:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 20, 2023):

The color scheme is not persisted on the server. That's a problem we want to solve with a general approach, not only for the color scheme.

See also https://kolaente.dev/vikunja/frontend/issues/2247

@kolaente commented on GitHub (Feb 20, 2023): The color scheme is not persisted on the server. That's a problem we want to solve with a general approach, not only for the color scheme. See also https://kolaente.dev/vikunja/frontend/issues/2247
GiteaMirror commented 2026-03-22 13:41:28 -05:00
Author
Owner
Copy Link

@vinaykapadia commented on GitHub (Apr 29, 2023):

At a minimum, just for now, is there a way to have the default be dark mode? Users can change it if they want, just like they can now. But all my users want dark any way.

@vinaykapadia commented on GitHub (Apr 29, 2023): At a minimum, just for now, is there a way to have the default be dark mode? Users can change it if they want, just like they can now. But all my users want dark any way.
GiteaMirror commented 2026-03-22 13:41:29 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 2, 2023):

Right now there's no way to make dark mode a default. The theme settings respects the system's preference for dark mode though, so if your users all want dark mode they should set it in their browser's settings accordingly.

@kolaente commented on GitHub (May 2, 2023): Right now there's no way to make dark mode a default. The theme settings respects the system's preference for dark mode though, so if your users all want dark mode they should set it in their browser's settings accordingly.
GiteaMirror commented 2026-03-22 13:41:30 -05:00
Author
Owner
Copy Link

@jamescochran commented on GitHub (Sep 21, 2023):

Sorry to beat a dead horse here but I was trying to figure this out and found this thread. My system (macOS 11) as well as browser (Firefox 117.0.1) are both set to dark mode yet Vikunja switches to light mode all the time. Should I bother making a new issue for that or just wait until Vikunja is updated to store this server side?

@jamescochran commented on GitHub (Sep 21, 2023): Sorry to beat a dead horse here but I was trying to figure this out and found this thread. My system (macOS 11) as well as browser (Firefox 117.0.1) are both set to dark mode yet Vikunja switches to light mode all the time. Should I bother making a new issue for that or just wait until Vikunja is updated to store this server side?
GiteaMirror commented 2026-03-22 13:41:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 25, 2023):

@jamescochran which version are you using? Can you reproduce this on try?

@kolaente commented on GitHub (Sep 25, 2023): @jamescochran which version are you using? Can you reproduce this on [try](https://try.vikunja.io)?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1849
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?