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
Funnily we launched a new Dutch website this very week, milieucafe.nl It is not a 'news' website but operates in the context of local government. The layout focuses on content instead of...
Looking for examples of (local) news websites running on BackdropCMS
The answer is off topic, but I'll add a little. 1. Backend. Why you don't need links to other websites: Since you know the structure of your site and content, you can decide for...
Looking for examples of (local) news websites running on BackdropCMS
Hi Chrys, AI isn't always your best friend. A form alter hook is correct, but hiding by CSS isn't ideal. You could look at how the TinyMCE integration does it, which provides hiding...
CKEditor5: Here's how to prevent "Select Image from Library" from appearing