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

[GH-ISSUE #76] User registration fails due to missing timezone #5938

New Issue
Closed
opened 2026-04-20 16:23:56 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-20 16:23:56 -05:00
Owner
Copy Link

Originally created by @nebulade on GitHub (Jul 7, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/76

Description

Fresh and vanilla instance fails to register new users from the register web view. The logs contain the following resuliting in 500 status code.

RegisterUser 261 unknown time zone <time zone set at service.timezone>

It does not seem to matter if service.timezone is set in the config.yml or not. Looking at the docs and code, even if unset it should fallback to GMT which it was doing fine in the previous version.

The user is actually created and the welcome mail is sent, however it subsequently fails during login since the response when querying the user profile after login contains literally timezone: "<time zone set at service.timezone>" (with the <>) in the settings object.

Vikunja Frontend Version

0.21.0

Vikunja API Version

0.21.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @nebulade on GitHub (Jul 7, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/76 ### Description Fresh and vanilla instance fails to register new users from the register web view. The logs contain the following resuliting in 500 status code. ``` RegisterUser 261 unknown time zone <time zone set at service.timezone> ``` It does not seem to matter if `service.timezone` is set in the config.yml or not. Looking at the docs and code, even if unset it should fallback to `GMT ` which it was doing fine in the previous version. The user is actually created and the welcome mail is sent, however it subsequently fails during login since the response when querying the user profile after login contains literally `timezone: "<time zone set at service.timezone>"` (with the `<>`) in the `settings` object. ### Vikunja Frontend Version 0.21.0 ### Vikunja API Version 0.21.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:23:57 -05:00
Author
Owner
Copy Link

@nebulade commented on GitHub (Jul 7, 2023):

This was resolved by realizing that the config.yml actually has those strings set at e5cd4897d6/config.yml.sample (L333)

Clearing those makes it fallback correctly to the service. properties. Maybe the sample file could have empty values and the current ones only as comments?

<!-- gh-comment-id:1625650932 --> @nebulade commented on GitHub (Jul 7, 2023): This was resolved by realizing that the config.yml actually has those strings set at https://github.com/go-vikunja/api/blob/e5cd4897d6be52c5bacb39a4ddae322921bfc0ee/config.yml.sample#L333 Clearing those makes it fallback correctly to the service. properties. Maybe the sample file could have empty values and the current ones only as comments?
GiteaMirror commented 2026-04-20 16:23:57 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 7, 2023):

Maybe the sample file could have empty values and the current ones only as comments?

Yeah that's one improvement we'd like to make. The current sample configuration is also used to generate the config docs and this was the easiest way to let it handle default values.

<!-- gh-comment-id:1625702001 --> @kolaente commented on GitHub (Jul 7, 2023): > Maybe the sample file could have empty values and the current ones only as comments? Yeah that's one improvement we'd like to make. The current sample configuration is also used to generate the [config docs](https://vikunja.io/docs/config-options/) and this was the easiest way to let it handle default values.
GiteaMirror commented 2026-04-20 16:23:58 -05:00
Author
Owner
Copy Link

@kolinblue commented on GitHub (Sep 13, 2024):

This error pops up regardless of what's set in the config.yml. It only started working once I manually set the env variables when I started it. (Non docker version)

<!-- gh-comment-id:2347969828 --> @kolinblue commented on GitHub (Sep 13, 2024): This error pops up regardless of what's set in the config.yml. It only started working once I manually set the env variables when I started it. (Non docker version)
GiteaMirror commented 2026-04-20 16:23:58 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 13, 2024):

The config value is only read during creation of the user. Once the user exists, the setting is persisted into the database.

<!-- gh-comment-id:2348326474 --> @kolaente commented on GitHub (Sep 13, 2024): The config value is only read during creation of the user. Once the user exists, the setting is persisted into the database.
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#5938
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?