The discussion revolves around Adding and editing user custom fields in Discourse. watchmanmonitor reported an issue with custom fields not being editable by admins when “Not editable after signup” is selected. They also requested that custom fields be shown on the user’s profile page and be editable by admins at all times.
@codinghorror and @eviltrout clarified that admins can edit custom fields by visiting the user’s preference page, but watchmanmonitor pointed out that this doesn’t work when “Not editable after signup” is selected.
@eviltrout later fixed this issue with a commit, allowing staff to edit user fields even if they are uneditable. riking noted that some custom fields added by plugins may have strict structures that prevent them from being exposed to moderators.
The main request from watchmanmonitor is to have all custom fields, including the user’s full name field, visible and editable on the admin’s view of each user.
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.
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.
