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?
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.
This is similar to this reported bug - User Field Requirement (2), 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.
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).
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.
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
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?
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.
Perhaps there is more going on than we thought. Let me see what I can find out.
