🐛 Bug Report: "locale" behavior #207

Closed
opened 2025-10-07 00:05:56 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @ptath on GitHub.

Reproduction steps

When I create new user via API

{
  "disabled": true,
  "email": "test@test.rld",
  "firstName": "name",
  "isAdmin": false,
  "lastName": "lname",
  "locale": "ru-RU", // <- locale set
  "username": "testuser"
}

Expected behavior

User open email and login to web with defined locale already set

Actual Behavior

User open (not-translated) email and login to web with default locale (en-EN)

Version and Environment

v.0.53.0

Log Output

not applicable

Originally created by @ptath on GitHub. ### Reproduction steps When I create new user via API ``` { "disabled": true, "email": "test@test.rld", "firstName": "name", "isAdmin": false, "lastName": "lname", "locale": "ru-RU", // <- locale set "username": "testuser" } ``` ### Expected behavior User open email and login to web with defined locale already set ### Actual Behavior User open (not-translated) email and login to web with default locale (en-EN) ### Version and Environment v.0.53.0 ### Log Output not applicable
OVERLORD added the bug label 2025-10-07 00:05:56 +03:00
Author
Owner

@ptath commented on GitHub:

expect the Pocket ID to display in Russian when users click the link in the email. But after the user signs in the locale is correctly set to Russian, right?

Right, but the problem magically disappeared in 1.0.0 =) Closing, thanks.

P.S. System emails don't have the ability to translate

@ptath commented on GitHub: > expect the Pocket ID to display in Russian when users click the link in the email. But after the user signs in the locale is correctly set to Russian, right? Right, but the problem magically disappeared in 1.0.0 =) Closing, thanks. P.S. System emails don't have the ability to translate
Author
Owner

@kmendell commented on GitHub:

If you look in the database in the users table, do you see the locale being set for the user after that api call?

@kmendell commented on GitHub: If you look in the database in the users table, do you see the locale being set for the user after that api call?
Author
Owner

@stonith404 commented on GitHub:

@ptath Could you elaborate on the issue you're experiencing. From what I understand, you expect the Pocket ID to display in Russian when users click the link in the email. But after the user signs in the locale is correctly set to Russian, right?

@stonith404 commented on GitHub: @ptath Could you elaborate on the issue you're experiencing. From what I understand, you expect the Pocket ID to display in Russian when users click the link in the email. But after the user signs in the locale is correctly set to Russian, right?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#207