setPasswordPath being ignored

Question

Any idea why the following would be ignored following a frontend new password form? The user group does not have access to the control panel.

'setPasswordPath' => 'account/login/password/new',

The following success path on the next line works fine:

'setPasswordSuccessPath' => 'account/login/password/done',

The user workflow:

1. Start on frontend Register form with firstname, lastname, email and password.
2. Account created and user is logged-in. No email confirmation needed.
3. User logs out.
4. User completes Forgotten Password form and email is sent.
5. User clicks password link in email and sees the Craft CMS password form.

I've tried this with and without the email address having a pre-existing Craft Commerce order associated with it. The result is the same.

Answer 1

Picking this up with another project, it looks like the problem was me not specifying a template path as the 'setPasswordPath' config setting. Instead, I was passing a route. I was doing this because I wanted to use the same password template to handle everything to do with passwords. This isn't possible, by the looks of it, because the controller is looking for the existence of a file (as opposed to a template being returned from a route or URI).

As soon as I changed it to a strict template path everything worked fine, and the following line in UsersController.php no longer returns false:

if (craft()->templates->doesTemplateExist($templatePath))

So this is solved.

Answer 2

In case someone is still having issues. setPasswordPath is actually expecting a template path and not a route.

'setPasswordPath' => 'myauth/set-password'

I have a file that lives in here:

MyCraftProjectFolder > templates > myauth > set-password.twig

Some may get confused because of the name "Path" at the end of setPasswordPath as many other config names include the word Paths and is expecting a route path. In this case setPasswordPath is expecting a template path.