This was brought up in https://github.com/backdrop/backdrop-issues/issues/4281#issuecomment-578...
@stpaultim
I notice that we only ask for a new password once when a user creates a new account. We only ask for a a new password once when an authenticated user chooses to change their password.
Should we ask for it twice when a user uses password reset to create a new password.
I don't feel strongly about this. But, it seems like Backdrop CMS has already made a decision that we don't want to require the double password thing. So, why not be consistent.
@indigoxela
Good point. As we're already working on it, why not switch to a single field?
$form['pass'] = array( '#type' => 'password', '#password_toggle' => TRUE, '#password_strength' => TRUE, '#required' => TRUE, );
...there's a concern: Changing the form field type could be a contrib-breaker, for instance for passphrase_policy module. This has to be evaluated, though.
Setting the same field to required is a task for a simple bugfix release, changing the form item type requires more evaluation and probably isn't appropriate for a bugfix release.
@stpaultim I'd rather recommend to create a new issue for the form field type change.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface