@eviltrout Repro steps: Let’s create a user field and it has id 1. Run the second line of the below code twice. Case 1 up = UserUpdater.new(Discourse.system_user, User.find(1)) up.update({:custom_fields=>{:user_field_1=>"abc"}}) You’ll see abc twice when you go to /my/preferences/profile Surp…

This does seem like a valid bug and should be fixed, thanks for reporting it!

My analysis comes down to this. # case 1 u1 = User.find(1) u1.custom_fields[:user_field_1] = "abc" u1.save # case 2 u1.custom_fields["user_field_1"] = "abc" u1.save In case 1, A new UserCustomField is created per call to u1.save [Screenshot 2020-08-20 at 11.52.09 AM] In case 2, All UserCustomF…

Ok, I went for it. Here’s the PR which fixes the issue https://github.com/discourse/discourse/pull/10486

Inkonsistentes Verhalten in der UserUpdater-Klasse

Entwickler

fzngagan (Faizaan Gagan) 25. August 2020 um 15:28 7

Okay, dieser ist also zusammengeführt.

Custom_fields updated simultaneous cause value to turn into array

Thema		Antworten	Aufrufe
[API] data loss caused by changed behaviour of custom user_field update Bug	2	811	20. Dezember 2017
Custom fields concurrency issue Development	0	67	6. Mai 2025
Custom_fields updated simultaneous cause value to turn into array Development rest-api	7	855	25. August 2020
Manipulating custom user fields from the Rails console Development rails-console , user-custom-fields	7	1638	5. August 2022
Custom User fields not saving Bug	18	2302	5. Oktober 2017

Inkonsistentes Verhalten in der UserUpdater-Klasse

Verwandte Themen