Adding and editing user custom fields


(Allen - Watchman Monitoring) #1

Here’s my experience with a custom field, as added via the Admin-> customize feature.

  1. Admin interface -> Add a custom field
  2. Mark it: Not editable after signup, required at signup, show on public profile (see below)
  3. have a new user register - All works as expected
  4. [Grumble that Full Name is still optional]
  5. View the new user in Admin area
  • user field is visible, but not editable
  1. View the user’s preferences page, Custom Field isn’t shown
  • Field is not visible to the user when logged in as him/her
  1. As the admin, looking at my acount in admin, I can’t edit the field

As I see it, 5 and 6 are not working as expected.

I’d like to see the custom field on the user’s profile page, and I’d like the Admin to be able to edit the field from the UI at all times.

Thanks!


(Sam Saffron) #2

OK, this boils down to

  1. User fields that are not “Editable after signup?” are not editable by admins
  2. If “show on public profile?” is unchecked, the user with the custom field can not see the field on profile page, nor can admins.

(Allen - Watchman Monitoring) #3

1 - Is that intentional? how are they supposed to be corrected if there’s a mistake?

2 - In my example, show on profile was selected. Will edit to add a picture.


(Allen - Watchman Monitoring) #4

I just saw these two admin options

staff user custom fields
and
public user custom fields

perhaps I’m missing a step as it relates to those… where can I see more information about the expected workflow?


(Jeff Atwood) #5

I agree that admins should always be able to edit these custom user fields on the user page, is that not the case @eviltrout ?


(Robin Ward) #6

I just checked, as an admin you can edit the fields by visiting the user’s preference page (as well as their other fields).


(Allen - Watchman Monitoring) #7

Unless they are not “editable later”.

Our need is for admins to do all their work on one page, the Admin view of the user, and always be able to edit the fields.

Without that, I’m jumping through hoops making them visible/not-visible, editable/not-editable, and on the admin page/user pref page. All of it taking extra time, but not providing any real controls because it’s all editable at some point.

the tl;dr summary:

Please put the User’s full name field, and all custom fields on the admin’s view of each user, all in an editable state.

Thank you


(Kane York) #8

Note that there can be other custom fields added by plugins, and they might have a strict structure, which I think is why this hasn’t been done. For the “private notes on a user” plugin, it wouldn’t exactly do to expose your ‘private’ notes to the moderators when they went to a user’s page.


Custom fields added by plugins - when would they be visible?
(Robin Ward) #9

Aha, that is indeed a problem. I’ve fixed it in this commit:

https://github.com/discourse/discourse/commit/6d38005a2294a23e1754573f2ce3089fb9f12077

Staff can now edit user fields even if the fields are uneditable.


(Jeff Atwood) #10