Hello
Problem not solved and linked:
Hello
I’ve tested to set user field requirements for new and existing community members, and it reveals that all the existing members are now blocked to reach the forum even if they fill the fields. They have ‘error’ message.
I’ve deleted all these new fields, and they still have the error message (cf screenshot)
What can I do ?
[Capture d’écran 2024-07-15 à 12.09.40]
[Capture d’écran 2024-07-15 à 12.10.01]
1 Like
@JammyDodger maybe you’ve got an idea?
1 Like
Here is the set up
(& there is an Automation to add them in a group according to what they answer)
Hmm.
4 Likes
Just to double-check, have you updated to pull in the fix I mentioned in the other topic?
discourse:main ← discourse:fix/update-fields-required-on-signup
opened 06:05AM - 12 Jul 24 UTC
### What is the problem?
We have recently added a new option to add user fiel… ds required for existing users. This is in contrast to requiring fields only on sign-up.
This revealed an existing problem. Consider the following:
1. User A signs up.
2. Admin adds a new user field required on sign-up. (Should not apply to User A since they already signed up.)
3. User A tries to update their profile.
**Expected behaviour:**
No problem.
**Actual behaviour:**
User A receives an error saying they didn't fill up all required fields.
### How does this fix it?
When updating profile, we only check that required fields that are "for all users" are filled. Additionally, we check that fields that were required on sign-up and have previously been filled are not blanked out.
2 Likes
We just asked our hosting platform to complete the update. We are on Discourse 3.3.0 beta4 right now, but the bug is still there
1 Like
Hi, I can also confirm this is still a bug. When I clicked on “On Signup,” it still requires you to update existing customers. However, the field type is missing.
You have to save, then navigate back to the user profile to see this to bypass it. I’ve noticed that if you don’t fill it out, it stops you from sending chat messages.
ted
August 26, 2024, 7:35am
16
Hello!
I just merged a fix for this issue here:
discourse:main ← discourse:fix/required-fields-check
opened 07:07AM - 26 Aug 24 UTC
### What is the problem?
This check was checking the wrong scope, causing pro… blems in certain edge conditions, for example:
1. Admin adds an "on signup" field that isn't editable after signup.
2. Admin adds a "for all users" field.
3. User goes and fills up the "for all users" field from 2.
4. User is now stuck on the required fields page without any fields showing.
### How does this fix it?
We only consider "for all users" fields when asking if required custom fields are filled in.
The problem was only noticed by either creating a mix of “on signup” and “for all users” or by users who gained access by other means than “signing up”. This PR should hopefully address all cases.
2 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
It’s not immediately obvious to me what the issue could be. Let me see if I can get someone to take a deeper look. 
