User Field Requirement (2)

Contribute Bug
,

AI-generated summary

User Field Requirement Issue

Eloïse_Barrège is experiencing an issue where some users receive an error message when filling in mandatory signup fields, even though they are set to “on signup” mode. This issue also affects older members who have the fields set to “editable”.

Eloïse_Barrège reached out to JammyDodger for assistance, who suggested checking if the fix mentioned in another topic was applied. However, after updating to Discourse 3.3.0 beta4, the issue persists.

Aaron_Walsh confirmed the bug and noted that it requires navigating back to the user profile to bypass. The issue prevents users from sending chat messages if the field is not filled out.

A fix for this issue was merged by ted in GitHub pull request 28541. The fix addresses cases where the issue occurs due to a mix of “on signup” and “for all users” fields or users gaining access through other means.

1

I'm afraid you have not actually provided an image for me to analyze and describe yet. Please upload an image and I'll be happy to describe it in a single sentence. (Captioned by AI)
I'm afraid you have not actually provided an image for me to analyze and describe yet. Please upload an image and I'll be happy to describe it in a single sentence. (Captioned by AI)1380×854 110 KB

Hello
Some users (not all) get an error message when filling in fields, even though they are setup in “on signup” mode, and for those who have been there for a long time, I have activated “editable”. But nothing happens. Can you please help me make sure that these mandatory signup fields don’t affect older members?

Problem not solved and linked:

1 Like
User Fields - weird signup behavior
4

@JammyDodger maybe you’ve got an idea?

1 Like
5

Here is the set up

Screenshot 2024-07-29 at 17.30.42
Screenshot 2024-07-29 at 17.30.421704×1292 197 KB

Screenshot 2024-07-29 at 17.30.57
Screenshot 2024-07-29 at 17.30.571716×1200 187 KB

(& there is an Automation to add them in a group according to what they answer)

6

Hmm. :thinking: 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. :eyes:

4 Likes
11

Just to double-check, have you updated to pull in the fix I mentioned in the other topic?

https://github.com/discourse/discourse/pull/27888

2 Likes
12

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 :frowning:

1 Like
13

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.

16

Hello! :wave:

I just merged a fix for this issue here:

https://github.com/discourse/discourse/pull/28541

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. :pray:

2 Likes
17

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.