@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

Inconsistent behaviour in UserUpdater class

Development

fzngagan (Faizaan Gagan) August 25, 2020, 3:28pm 7

Ok, so this one is merged.

Custom_fields updated simultaneous cause value to turn into array

Topic		Replies	Views
[API] data loss caused by changed behaviour of custom user_field update Bug	2	801	December 20, 2017
Custom fields concurrency issue Development	0	58	May 6, 2025
Custom_fields updated simultaneous cause value to turn into array Development rest-api	7	835	August 25, 2020
Manipulating custom user fields from the Rails console Development rails-console , user-custom-fields	7	1613	August 5, 2022
Custom User fields not saving Bug	18	2281	October 5, 2017

Inconsistent behaviour in UserUpdater class

Related topics