Full name at Sign Up went missing

Player1 · January 5, 2025, 1:01pm

Hi all!

Total discourse noob here - bear with me
I’m knee-deep in the process of setting up an instance for a small community of around 80 people. I was supposed to have this up and running come 2025

We need people to Sign up with their full name. When I initially set Discourse up, I had Full name required and everything was working as expected.
Now the Sign up form does not show the field at all and I’m not sure at what point it went missing.
The only change I have made since is installed this plugin Majal / discourse-available-locales · GitLab to narrow down the languages available.
I have tried removing the plugin but the full name field was still missing.
I have Full name requirement set to “Required at signup”.
Adding a custom user field works as expected.

Any help would be appreciated

CocoQuark · January 5, 2025, 1:16pm

Welcome

You can ensure this by visiting admin/logs/staff_action_logs. Maybe you missed some setting change that could cause your issue?

Also a bit off topic, but you may want have a look at Available Locales Plugin - #5 by angus since it seems to provide the same feature as your plugin, but is maintained (yours seems not).

Moin · January 5, 2025, 1:22pm

Could you take a look at that setting again? Last week a new feature was added. The setting is now called full_name_requirement.

github.com/discourse/discourse

FEATURE: Add option to hide full name input at signup

discourse:main ← discourse:feature/option-for-optional-name-at-signup

opened 09:55AM - 26 Dec 24 UTC

OsamaSayegh

+217 -42

This PR replaces the `full_name_required` setting with a new `full_name_requirem…ent` setting to allow more flexibility with the name field in the signup form. The new setting has 2 options, "Required at signuo" and "Optional at signup", which are equivalent to the true/false possibilities of the old setting, and a third option "Hidden at signup" that hides the name field from the signup form, making it effectively optional too. New sites will have the "Hidden at signup" option as the default option, and existing site will continue to use the option that maps to their current configuration. Internal topic: t/136746.

Also, check whether the enable_names site setting is enabled as well.

Player1 · January 5, 2025, 1:51pm

This staff action log seems super helpful. Hadn’t even noticed it before
I’ll start looking through the logs more closely.

Also, I’ll def. switch to the maintained plugin thanks.

Player1 · January 5, 2025, 3:58pm

Thanks for the link.

I have triple-checked all settings but still cannot get the full name field to appear.

Full name requirement: required at signup
Enable names: checked

I am stumped.

EDIT:
I had a look around on github, wonder if this PR could have anything to do with my issue??

github.com/discourse/discourse

FIX: Allow signups when full names are disabled

discourse:main ← discourse:fix/allow-signup-when-names-disabled

opened 07:16AM - 04 Jan 25 UTC

OsamaSayegh

+77 -11

Follow-up to https://github.com/discourse/discourse/pull/30471 When the `enab…le_names` setting is false and the `full_name_requirement` setting is set to `required_at_signup`, the name field in the signup form should effectively be not required (and hidden). However, that is not actually the case at the moment because the `name-validation.js` mixin only checks for the `full_name_requirement` setting when determining whether the name field should block a new signup. This PR fixes the issue by making the `full_name_required_for_signup` and `full_name_visible_in_signup` site attributes check for the `enable_names` setting themselves. This spares any consumers of these properties from having to remember to include a check for the `enable_names` setting.

CocoQuark · January 5, 2025, 7:26pm

I updated my instance to check out the new setting.

I set the same values:
Full name requirement: required at signup
Enable names: checked

And the name field appears on the sign up page.

Btw, the placeholder is just “Name”, which isn’t clear enough to me (I’m aware there’s a setting to show a description below the field), so I changed it to “Full Name” in admin/customize/site_texts after doing this test.

Player1 · January 5, 2025, 8:23pm

Thanks for taking the time to help

Could the plugin I added have broken something?
After I installed it, I removed all languages exept 3.
That was why I installed it.

CocoQuark · January 5, 2025, 9:44pm

If:

Safe mode doesn’t change anything
You don’t see anything related in admin/logs/staff_action_logs
You don’t see anything related in non-default setting values
You don’t see anything in logs/
There’s no clue in JS console or in the network tabs of your browser’s dev tools
Don’t see anything in the HTML code (in case some CSS or browser extension would hide the field)
Updating Discourse (ideally, rebuilding from the command line) doesn’t fix it
If you don’t have any recent backup in which the field was visible

You can continue to search and wait for help, or maybe save some time and sweat by reinstalling Discourse. It’s not necessarily an overkill solution, especially if your installation is fresh.

But it’s also frustrating not understanding why this issue happens.

That said, to me, it looks like either a setting quirk, or a bug.

Player1 · January 6, 2025, 12:43am

Neither Safe mode or staff_action_logs yielded any results or clues.

However

First sign that something is fishy.
Screenshot from the Web developer tool in firefox

I obscured my domain. (and thensome cause i don’t know if it’s sensitive or not )

These errors go waaaay over my understanding.
Maybe somebody knows what to make of these?

Well,
I made a backup diskimage on the server, right after I got Discourse installed, so I can always get a fresh start.

But as you pointed out:

It really is.
I could have reverted to the fresh image long ago, and saved alot of time, but somehow I always take the long way home

CocoQuark · January 6, 2025, 12:45am

Do those errors happen only on the sign-up screen? Do they disappear in safe mode?
The URLs aren’t sensitive (the domain part is at your discretion though).

Player1 · January 6, 2025, 12:54am

No. They appear on every page. Even after refresh of page.

Yes they do!

pmusaraj · January 6, 2025, 4:40pm

I can’t reproduce your issue either. Can you look at the site settings page and check the “only show overriden” checkbox in the top right to see if there are any other adjacent settings that might affect your instance?

Player1 · January 6, 2025, 9:32pm

I reverted the server to an early (post Discourse install time) using a snapshot. The problem was still present.
I’m starting fresh and this time around be more careful with all settings and plugins I install.

Thanks to all who took the time to help me with this

EDIT: Oh shoot, my bad.
It was unintentional - won’t happen again

CocoQuark · January 6, 2025, 10:12pm

We don’t do this mistake here

sklob · January 7, 2025, 3:17pm

Were you able to fix the issue? I’m facing the same problem right after updating to Discourse 3.4.0.beta4-dev.

Both settings are correct:

Full name requirement: required at signup
Enable names: checked

But the full name field still doesn’t show up on the sign up screen like it did before…

Player1 · January 7, 2025, 6:28pm

Issue still alive and well.
I’ve been busy trying to pinpoint the cause.

Can you check something on your Discourse instance?
Does the name field re-appear to the signup form if you uncheck the “login required” box?

Moin · January 7, 2025, 6:39pm

I think you are correct. The login required setting is the game changer

Login required disabled, name field is shown as expected:

Login required enabled, name field is missing:

sklob · January 7, 2025, 9:05pm

It does come back! Super weird. Why on Earth are the two related? So, yes, to confirm, I uncheck the “login required” box and the full name field does appear again. Any additional thoughts on how to fix without having to make the community’s content wide open to the public? Thanks!

Osama · January 8, 2025, 12:09am

Thank you all for cracking this mystery, here’s a PR to fix the bug:

github.com/discourse/discourse

FIX: Name field should appear in the signup form for login-required sites

discourse:main ← discourse:fix/name-field-missing-login-required-sites

opened 12:05AM - 08 Jan 25 UTC

OsamaSayegh

+79 -2

Meta topic: https://meta.discourse.org/t/full-name-at-sign-up-went-missing/34566…2/17?u=osama The preloaded `site` object for anons on login-required sites is a stripped down version of the full object with just a specific set of attributes and doesn't use the site serializer. This results in the `full_name_required_for_signup` and `full_name_visible_in_signup` attributes not making it to the client app when a login-required site is accessed by an anon, causing the name field in the signup form to not be rendered, even when it's required. This PR includes those attributes in the stripped down version of the `site` object that's used for anons on login-required sites.

pfaffman · January 8, 2025, 12:30am

Yes. The first thing I would do is remove is and see if it’s the problem. Safe mode works to disable it only if they did everything right.

Edit: Oops. Apologies if you did remove it and I didn’t understand

Topic		Replies	Views
Full name @mentions Feature mentions	60	11700	March 15, 2022
Anonymizing user keeps email address and real name when "full name required" is on Bug	22	4161	March 19, 2016
Configure Facebook login for Discourse Integrations sso , how-to , social-auth	23	330349	July 31, 2024
Prevent users from changing their Full Names Feature	23	1240	May 2, 2023
Discourse Show Fullname in Mentions Theme component	29	2200	October 19, 2023

Full name at Sign Up went missing

Related topics