Hi, I have just begun operating a small discourse for real life friends and I wanted to enforce a Real Name policy. I’ve required full name on sign up and an approval only policy, but after sign up users can edit their Full Name. I want to disable this so that an approved user’s full name is essentially locked after sign-up, but an admin can still edit the field. I was looking at where this check happens and it seems there’s no logic that will let me enforce this policy exactly: lib/guardian/user_guardian.rb e8c7c6fab is_me?(user) && (user.post_count == 0 || user.created_at > SiteSetting.username_change_period.days.ago) end def can_edit_email?(user) return false if (SiteSetting.sso_overrides_email? && SiteSetting.enable_sso?) return true if is_staff? return false unless SiteSetting.email_editable? can_edit?(user) end def can_edit_name?(user) return false if not(SiteSetting.enable_names?) return false if (SiteSetting.sso_overrides_name? && SiteSetting.enable_sso?) return true if is_staff? can_edit?(user) end def can_block_user?(user) user && is_staff? && not(user.staff?) end Username and e-mail have settings that relate to whether a user can self-edit them, but there are no such settings for full names. Is this true? Is there some work around? Thanks!

I have an instance where avatars are handled elsewhere and I changed the preferences template to hide the avatars change section. You can do the same.

I see. That seems like a clean solution. Was the separate avatar handling page a custom page you’ve added?

Yes, I changed the preferences template, so the little pencil from avatar on preferences page is a link that send people to the avatar change page in another system. Our avatars were handled outside Discourse and integrated with the setting default avatars.

Thanks I think that gives me an idea of how I might proceed.

Interesting. I have a similar requirement for a Membership site. In my case we will carry over Real Names from a separate site with registration using SSO. We will allow users to adopt usernames for taking part in the Discourse conversation, but we want them to always be linked to a Real Name on their profile, and so do not want them to be able to change it once it has been populated during registration. Is this possible?

thanks! I’m not yet using … but it is the plan I am putting together and so have not discovered that yet. Much obliged

[תמונה] Falco: I changed the preferences template to hide the avatars change section. You can do the same. I’ve been searching 20 minutes and can’t find the preferences template. I’ve found pieces of it but not the template. Can someone point me to it?

I think the template is referring to this part of the codebase This portion specifies the action that gets taken when someone clicks on the big pencil for editing the avatar. app/assets/javascripts/discourse/app/templates/preferences/account.hbs 42f6c9b6b {{/if}} {{#unless siteSettings.discourse_connect_overrides_avatar}} {{i18n "user.avatar.title"}} {{! we want the "huge" version even though we're downsizing it in CSS }} {{bound-avatar model "huge"}} {{d-button action=(route-action "showAvatarSelector") actionParam=model class="btn-default pad-left" icon="pencil-alt"}} {{/unless}} {{#if canCheckEmails}} {{i18n "user.email.title"}} {{#if model.email}} {{#if siteSettings.enable_secondary_emails}} & here is the action associated with the showAvatarSelector that could be replaced if you wanted to customize. Hope this helps!

Thanks, but I believe @Falco may have been referring to Admin > Customize > Text. For example I can find this piece: js.user.change_avatar.title and I expected there would also be a higher-level template that defines the entire user’s preference page and contains that piece. By removing the avatar section from that template, one could prevent users from changing their avatar. (Or their full name, which is what I want to do.) But I still can’t find the template that defines the users preference page.

Disabling full name changes

Product Support

fefrei (Felix Freiberger) 20 בדצמבר,‏ 2016,‏ 4:34pm 7

Since you’re using SSO, checking sso overrides name should solve your problem

נושא		תגובות	צפיות
Prevent users from changing their Full Names Feature	23	1874	2 במאי,‏ 2023
Letting users choose whether to show Full Name Feature	18	1860	3 בפברואר,‏ 2021
FB Login - Do not allow Full name to be changed Feature	3	643	18 במאי,‏ 2020
Hide full name if not logged in Development	10	1898	13 במרץ,‏ 2020
Allow site operators to control full name suppression on posts Feature	49	10331	27 באפריל,‏ 2018

Disabling full name changes

נושאים קשורים