[bug] Error when changing settings #1031

New issue

Closed

opened 2025-12-13 06:27:06 +00:00 by Hiker · 1 comment

Hiker commented

2025-12-13 06:27:06 +00:00

Your setup

OTP

Extra details

Ubuntu 24.04.3 LTS

Version

3.17.0-0-g06589d9--stable- frontend 0da97ce

PostgreSQL version

16.11

What were you trying to do?

When changing something on the settings page it seems that is isn't stored and on the top left is an error message "Error saving settings".

What did you expect to happen?

No response

What actually happened?

No response

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details Ubuntu 24.04.3 LTS ### Version 3.17.0-0-g06589d9--stable- frontend 0da97ce ### PostgreSQL version 16.11 ### What were you trying to do? When changing something on the settings page it seems that is isn't stored and on the top left is an error message "Error saving settings". ### What did you expect to happen? _No response_ ### What actually happened? _No response_ ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

errorsettings.jpg

5.4 KiB

Hiker added the

bug

label

2025-12-13 06:27:06 +00:00

Oneric commented

2025-12-19 19:20:18 +00:00

Owner

This is a pure frontend bug and the setting still both takes effect and is synchronised to the server regardless of the displayed error. Only the copy stored in local browser long-term storage wasn’t updated; probably was only affecting recurring page visitors without an account.

Fixed by: AkkomaGang/akkoma-fe#469

For future reference, please file frontend bugs here: https://akkoma.dev/AkkomaGang/akkoma-fe

This is a pure frontend bug and the setting still both takes effect _and_ is synchronised to the server regardless of the displayed error. Only the copy stored in local browser long-term storage wasn’t updated; probably was only affecting recurring page visitors without an account. Fixed by: https://akkoma.dev/AkkomaGang/akkoma-fe/pulls/469 For future reference, please file frontend bugs here: https://akkoma.dev/AkkomaGang/akkoma-fe