<p>I have an issue. I have custom fields in the user profile, some of them are required.</p>

<p>I also have a change your password page and a change your email password.</p>

<p>A user can create an account (Without the custom fields).</p>

<p>But when he/she tries to change the password without completing the profile (In the change password page), the password won't be saved as there are some required fields empty.</p>

CC BY-SA 4.0
2019-02-26T19:43:33.087Z
Would it be an option to create a custom controller and a few lines of PHP to set the password without the other fields? That's how I usually handle it
Robin Schambach
CC BY-SA 4.0
2019-02-27T09:16:28.773Z
Yes, that's definitely an option, that was actually my solution but I've found that Craft usually has everything I need and that I should try to reinvent the wheel (Learnt that the hard way). So I wanted to make sure first that there's nothing there already.
Jorge Anzola
CC BY-SA 4.0
2019-02-27T09:23:16.200Z
You could create a feature request but for now the only time Craft sets the scenario `password` and not `scenario live` (which will validate fields) is during a public registration process or after a user receives a password reset mail.
Robin Schambach
<templating><user-profile><registration>
A user cannot change the password without completing the profile
# A user cannot change the password without completing the profile

(Asked by: username_0 on 2019-02-26)

I have an issue. I have custom fields in the user profile, some of them are required.

I also have a change your password page and a change your email password.

A user can create an account (Without the custom fields).

But when he/she tries to change the password without completing the profile (In the change password page), the password won't be saved as there are some required fields empty.

**Tags:** templating, user-profile, registration
> **Comments:**
> **username_1**: Would it be an option to create a custom controller and a few lines of PHP to set the password without the other fields? That's how I usually handle it  
> **username_0**: Yes, that's definitely an option, that was actually my solution but I've found that Craft usually has everything I need and that I should try to reinvent the wheel (Learnt that the hard way). So I wanted to make sure first that there's nothing there already.  
> **username_1**: You could create a feature request but for now the only time Craft sets the scenario `password` and not `scenario live` (which will validate fields) is during a public registration process or after a user receives a password reset mail.  

---

## 0 answers

