# User Fields - weird signup behavior

**URL:** https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146
**Category:** Bug
**Tags:** stable, user-custom-fields
**Created:** [August 5, 2024, 11:32am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146 "2024-08-05T11:32:46Z")
**Posts on this page:** 17
**Page:** 1

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 5, 2024, 11:32am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/1 "2024-08-05T11:32:46Z")

</div>

Hello, since the 3.3.0+3 (stable) update I see the new Custom Fields settings for “optional”, “signup” and “for all users”, but it does not completely work: when a user logins in they see the “you need to provide information” field (but not the missing field). When they click save they get the profile (and no field missing marked). They then regularly (always when going to /) get the same reminder. There is however none of the fields marked as “all users”. Some of the fields (especially one which is absent for some older users) is “on signup” and “not edit” and “not display”.

My understanding is, that it should not cause this-reasking.

I clicked around and changed many of the field attributes back and forth, it didnt improve the situation, but it somehow felt it did not always take immediate action. Do I maybe need to run a rebuild-job?

The “unhelpful” message looks like this:

 ![image](https://global.discourse-cdn.com/meta/original/4X/5/f/6/5f641780aa30becd7565e4c10f87a7373cb745bf.png)

Whats interesting is that when I click on “Save” i get my standard profile page shown but without any of the user fields (not the missing ones and not the ones actually marked as editable).

If an admin fills out the missing fields (even though they are marked as sign-up), the user can see their full profile again.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [August 5, 2024, 11:45am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/2 "2024-08-05T11:45:00Z")

</div>

This is similar to this reported bug - [User Field Requirement (2)](https://meta.discourse.org/t/user-field-requirement-2/318968), though I think the fix for it should have been included in the latest `stable` release. 🤔 Perhaps there is more going on than we thought. Let me see what I can find out.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 5, 2024, 11:47am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/4 "2024-08-05T11:47:04Z")

</div>

thanks! let me know if you need commands executed or logs.

I am not sure if the problem was directly after the update or only after i started to customize those fields with the new options.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 5, 2024, 11:54am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/5 "2024-08-05T11:54:39Z")

</div>

btw would be nice to have optional “signup only” or “all user” fields, i.e. they are asked once but can be empty.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 5, 2024, 12:07pm UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/6 "2024-08-05T12:07:31Z")

</div>

not sure if it is relevant, but some of the users might have been signed up with the “invite” or “automatically accept” and “add to grroup by email” function. But most of them might be older than the user field in question (as it is empty for them).

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 12, 2024, 11:52am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/7 "2024-08-12T11:52:25Z")

</div>

Do you have an update on this? ITs a bit cumbersome to fill all the empty comments and using optional is not an option (sic) since it wont show on the signup screen for new members.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 21, 2024, 11:39am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/8 "2024-08-21T11:39:49Z")

</div>

Any news here - in case this drags on I will have to do some mass changes to all users to make sure they dnt complain one after another…

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [August 21, 2024, 11:42am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/10 "2024-08-21T11:42:37Z")

</div>

Let me give someone a nudge and see if I can find out anything. 👍

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [August 21, 2024, 11:55am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/11 "2024-08-21T11:55:08Z")

</div>

FWIW I did get a repro for this, but when I deleted the user field and attempted a second go the new fields showed up on the page as expected.

 ![image](https://global.discourse-cdn.com/meta/original/4X/7/8/b/78b246373658db94afb4abcc8afe5d185838d742.png)

Something may be going wonky with the ‘editable after sign up’ default for existing fields? 🤔

* * *

Okay, I think I was reproing the wrong way round. I’ve had a cup of tea and a regroup.

I now have a user field set as On signup & not editable afterwards:

 ![image](https://global.discourse-cdn.com/meta/original/4X/4/e/0/4e01f6e0d04337e6578f51fb7e16e6e4fcefd44d.png)

This causes my existing test user to bork out in a similar way:

 ![image](https://global.discourse-cdn.com/meta/original/4X/3/d/5/3d5a2ee764e37edc2cbf07a727c1f4eb37729214.png)

---

<div class="post-metadata">

### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)
#### Post date: [August 26, 2024, 6:34am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/13 "2024-08-26T06:34:19Z")

</div>

Hello, @ecki! 👋

Thanks for the report. I’ll look into this.

> [@ecki](#):
>
> not sure if it is relevant, but some of the users might have been signed up with the “invite” or “automatically accept” and “add to grroup by email” function.

I suspect this is the key. There may be an assumption that all users with an account have at some point “signed up”, which might be causing issues.

Will get back to you once I’ve done some more investigating.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 28, 2024, 7:04pm UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/14 "2024-08-28T19:04:06Z")

</div>

Ah yes, they are not editable in my case as well. It’s an initial signup justification and a customer number (which should only be changeable upon request with admin review).

I could make them editable if there where some easy change tracking - come to think of it

---

<div class="post-metadata">

### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)
#### Post date: [August 29, 2024, 2:46am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/15 "2024-08-29T02:46:52Z")

</div>

I found what is probably the root cause of this, and fixed it in a PR that has already been merged:

[https://github.com/discourse/discourse/pull/28541](https://github.com/discourse/discourse/pull/28541)

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [September 10, 2024, 11:53am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/17 "2024-09-10T11:53:28Z")

</div>

Cool, I just got proposed the 3.3.1 stable branch update, but seems to not be included yet. Is there an easy way to test out such commits without changing the update channel?

---

<div class="post-metadata">

### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)
#### Post date: [September 17, 2024, 2:34am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/19 "2024-09-17T02:34:51Z")

</div>

@ecki Sorry. I missed the fact that you’re on `stable`. I have opened a PR to back port this fix. 🙏

[https://github.com/discourse/discourse/pull/28939](https://github.com/discourse/discourse/pull/28939)

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [September 17, 2024, 4:44pm UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/20 "2024-09-17T16:44:43Z")

</div>

ah thanks, that is kind.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [September 24, 2024, 10:16am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/21 "2024-09-24T10:16:09Z")

</div>

I have installed your fix in our stable update and so far no complaint (however I cant replicate the problem (cant empty a comment field intentionally), so I am not sure if not somebody is still affected we did not manually fix. But it looks good so far! thanks.

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [October 3, 2024, 9:54am UTC](https://meta.discourse.org/t/user-fields-weird-signup-behavior/320146/22 "2024-10-03T09:54:35Z")

</div>

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