Answers.Body: <ol>
  <li><p>There was a bug in Craft such that when saving a user, if the username / email / password failed validation first, content validation would never get a chance to run.</p>
  
  <p>Have just fixed that locally and it will go out in the next release.</p></li>
  <li><p>The way you have your dropdowns defined (userCountry and occupation), they'll never fail validation because there will always be a value selected and submitted in $_POST.</p></li>
  <li><p>The first name and last name fields on a user account are somewhat “<a href="https://plus.google.com/u/0/+BenParizek/posts/isVyC5MnQs1" rel="nofollow">special</a>” fields.  There is currently no way to set them as required.  We've got some plans to revamp how user names are handled on “The List”™ for a future update.  In the meantime, if you want to make them required fields, you can create actual custom fields for them.</p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-21T07:15:15.587Z
Answers.Text: Thanks Brad - that will solve it - do you know when I can integrate this fix - I have a client **desperate** for the custom fields to work as required.
Answers.UserDisplayName: Dan G
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-17T16:58:27.357Z
Answers.Text: Is there any update Brad on being able to make first name and last name fields required? I was researching how to do that and found this answer. For now I'll just use custom fields as you suggest.
Answers.UserDisplayName: Dave Joyce
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-14T15:00:10.837Z
Answers.Text: Will this be in Craft 3?
Answers.UserDisplayName: Andrea DeMers
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-29T19:08:49.143Z
Answers.Text: Apparently not, I cannot find anywhere in craft 3 that allows you to force the first and last name to be required.
Answers.UserDisplayName: Rick Kukiela
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-26T16:50:32.137Z
Answers.Text: Kind of ridiculous you can't set this fields as required. There are many scenarios where someone would want this data and be sure it's in there for registration
Answers.UserDisplayName: Cat Named Dog
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-02T22:13:10.560Z
Answers.Text: Agreed. It is kind of ridiculous that we can't set first and last name as required and that this issue is nearly seven years old.
Answers.UserDisplayName: Mosswalker
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-18T23:43:18.957Z
Answers.LastActivityDate: 2014-07-18T23:43:18.957Z
Answers.UserDisplayName: Brad Bell
Body: <p>We have a user signup form (see <a href="http://thinkdif.co/me/signup" rel="nofollow">http://thinkdif.co/me/signup</a>) that has some extra required fields. When a craft field us missed out, the error code below works, however when a custom User field is not completed, the page does not save, but no error is presented. </p>
  
  <p>We require errors on custom user signup fields, and also on the 'Update your profile' page that is presented later in the workflow. </p>
  
  <p>Thanks for any help or examples. End goal is to have good required fields throughout the user workflow.</p>
  
  <p>Dan</p>
  
  <p>Example error code:</p>
  
  <pre><code>    {% if account is defined %}
      {{ _self.errorList(account.getErrors('occupation')) }}
      {% endif %}
  </code></pre>
  
  <p><strong>Edit</strong>:</p>
  
  <p>Here is a gist of the full page. <a href="https://gist.github.com/slipstreamstudio/d8dd801d722c3f275b74" rel="nofollow">https://gist.github.com/slipstreamstudio/d8dd801d722c3f275b74</a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-07-17T12:50:47.310Z
Comments.Text: Have you set the field as required in the Control Panel?
Comments.UserDisplayName: Bryan Redeagle
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-07-18T20:30:26.520Z
Comments.Text: Yes - all set but errors are not returning for custom fields.
Comments.UserDisplayName: Dan G
Tags: <users>
Title: Required Fields for User Signup
ThreadText: # Required Fields for User Signup
  
  (Asked by: username_0 on 2014-07-17)
  
  We have a user signup form (see <http://thinkdif.co/me/signup>) that has some extra required fields. When a craft field us missed out, the error code below works, however when a custom User field is not completed, the page does not save, but no error is presented.
  
  We require errors on custom user signup fields, and also on the 'Update your profile' page that is presented later in the workflow.
  
  Thanks for any help or examples. End goal is to have good required fields throughout the user workflow.
  
  Dan
  
  Example error code:
  
  ```
      {% if account is defined %}
      {{ _self.errorList(account.getErrors('occupation')) }}
      {% endif %}
  
  ```
  
  **Edit**:
  
  Here is a gist of the full page. <https://gist.github.com/slipstreamstudio/d8dd801d722c3f275b74>
  
  **Tags:** users
  
  > **Comments:**
  > **username_1**: Have you set the field as required in the Control Panel?  
  > **username_0**: Yes - all set but errors are not returning for custom fields.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2014-07-18. Score: 2
  
  1. There was a bug in Craft such that when saving a user, if the username / email / password failed validation first, content validation would never get a chance to run.
  
     Have just fixed that locally and it will go out in the next release.
  2. The way you have your dropdowns defined (userCountry and occupation), they'll never fail validation because there will always be a value selected and submitted in $\_POST.
  3. The first name and last name fields on a user account are somewhat “[special](https://plus.google.com/u/0/+BenParizek/posts/isVyC5MnQs1)” fields. There is currently no way to set them as required. We've got some plans to revamp how user names are handled on “The List”™ for a future update. In the meantime, if you want to make them required fields, you can create actual custom fields for them.
  
  > **Comments:**
  > **username_0**: Thanks username_2 - that will solve it - do you know when I can integrate this fix - I have a client **desperate** for the custom fields to work as required.  
  > **username_3**: Is there any update username_2 on being able to make first name and last name fields required? I was researching how to do that and found this answer. For now I'll just use custom fields as you suggest.  
  > **username_4**: Will this be in Craft 3?  
  > **username_5**: Apparently not, I cannot find anywhere in craft 3 that allows you to force the first and last name to be required.  
  > **username_6**: Kind of ridiculous you can't set this fields as required. There are many scenarios where someone would want this data and be sure it's in there for registration  
  > **username_7**: Agreed. It is kind of ridiculous that we can't set first and last name as required and that this issue is nearly seven years old.  
  
  ---
  
  