어떤 nth-of-type을 사용해야 하는지 시행착오로 추측해야 해서 다소 번거롭지만, 제가 제안하는 것은 이 CSS가 모달을 올바르게 보이게 하던 스타일이 가끔씩 변경된다는 점입니다. 최근 beta6에서 변경된 것으로 보입니다. 이는 제 클라이언트에게 슬픈 일이었습니다. 필수 필드가 보이지 않아 사람들이 가입할 수 없었거든요. 누군가 불만을 메일로 보내서야 알게 되었습니다.
I don’t think it would be hard to add a class or data attribute that includes the custom field’s name, which would make it much less fragile to target with CSS. I can probably get to that within the next couple of days.
Took a quick look and it’s nearly identical to another PR I opened recently to add a class to tag groups. So here’s a PR for this… we might want to add a helper to sanitize class names before merging these?
I just realized that I never followed up after this was merged. Now on the signup page all user fields have a class in the form of user-field-name. So if you had a field with the name “terms and conditions” it would have the class user-field-terms-and-conditions.
You can also take a shortcut and hide all custom user fields at signup with
Thanks! I managed to get this done a week or two ago. You might edit that list to also include the css to un-hide a field or two after hiding the rest.
Here is a closed thread about solving this, which includes a css solution:
Right now for custom user fields, the options are:
Editable after signup?
Required at signup?
Show on public profile?
Show on user card?
I think another option would be quite useful:
Show on signup form?
or
Hide on signup form?
By default, without custom CSS modification, all custom fields (optional or not) will be displayed on the registration form. This somewhat limits the amount of custom fields that can be implemented as having too many will make the registration form overloaded and potentially intimidating to new users.
Sometimes it is nice to have a bunch of custom user fields to ask for information that you don’t want to bother people with on signup. For example, you might want to have the ability for someone to provide their address, zip code, or hair color, but on signup ask them only for their name and email address.
It would also be helpful to be able to differentiate sign-ups and invitees, especially if a field is mandatory for both or just for signups.
For example, we ask people to provide their “Reason for Joining” to help us decide their suitability and group. This is redundant when people arrive via an invite link, but it can’t be hidden if mandatory or it breaks the signup for them.
There are some user fields on my site which really dont need to be present at signup, such as socials.
I think we could benefit from a “Do not display at signup” option option, making it hide during signup and only be visible when editing your user profile.
Has something changed on the signup modal that might cause this CSS to not work anymore?
I can’t hide any custom fields on the signup page by using either the code in the first post by @pfaffman - nor can I hide all of the custom fields by using the code from @awesomerobot :
I’ve been applying the CSS to Themes > Common > CSS.