Skip to content

Users: Fix Generate Password button requiring two clicks on Add New User screen#9674

Open
taninakond wants to merge 4 commits intoWordPress:trunkfrom
taninakond:ticket/63897-generate-password-fix
Open

Users: Fix Generate Password button requiring two clicks on Add New User screen#9674
taninakond wants to merge 4 commits intoWordPress:trunkfrom
taninakond:ticket/63897-generate-password-fix

Conversation

@taninakond
Copy link

@taninakond taninakond commented Aug 29, 2025

This patch fixes the issue where the Generate Password button requires two clicks on the Add New User screen.

  • Moves generatePassword() inside the AJAX callback.
  • Ensures the password field is updated immediately after the new password is generated.
  • Prevents user confusion and improves usability.

Trac ticket: https://core.trac.wordpress.org/ticket/63897


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

…e password field on the Add New User screen.

The password was previously set before the AJAX response returned, resulting in the first click not updating the password field. This change moves the `generatePassword()` call inside the AJAX callback to ensure the password is always updated immediately.

Props taninahmed.
Fixes #63897.
@github-actions
Copy link

Hi @taninakond! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions
Copy link

github-actions bot commented Aug 29, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props taninakond.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@taninakond taninakond marked this pull request as draft August 29, 2025 20:20
@taninakond taninakond marked this pull request as ready for review August 29, 2025 20:20
Move the block at lines 264–268 to line 63, directly under the generatePassword call. This ensures that:

1. The password field is always initialized with the value set in $pass1.data('pw'), which comes from PHP and is set at line 32.

2. Any network request to fetch a new password happens after the initial password is set, so there is no delay in showing a password on page load.

3. When the user clicks the "Generate Password" button, a new password is fetched and stored in data-pw, ensuring the latest password is always available.
The block at lines 533–542 that triggered the "Generate Password" button click on page load is no longer needed. Passwords are already automatically filled via the bindPass1 function, which calls generatePassword() on initialization.
@taninakond
Copy link
Author

Refactor automatic password generation for improved UX and code clarity on the Add New User and Reset Password pages

Remove redundant code:
The block at lines 533–542 that triggered the "Generate Password" button click on page load is no longer needed. Passwords are already automatically filled via the bindPass1 function, which calls generatePassword() on initialization.

Move network password generation:
Move the block at lines 264–268 to line 63, directly under the generatePassword call. This ensures that:

  1. The password field is always initialized with the value set in $pass1.data('pw'), which comes from PHP and is set at line 31.
  2. Any network request to fetch a new password happens after the initial password is set, so there is no delay in showing a password on page load.
  3. When the user clicks the "Generate Password" button, a new password is fetched and stored in data-pw, ensuring the latest password is always available.

Result:
On both the Add New User and Reset Password pages, the password field is immediately filled from the server-provided value. If a new password is needed, it is fetched without delaying the initial UI, and any user-initiated password generation fetches a fresh value as expected.

Wrap the `generate-password` AJAX call in a conditional check to ensure it
only runs when the `.wp-generate-pw` element is present. This avoids
unnecessary requests on pages such as:

- Settings → Writing
- Installer "Information needed" screen (which could result in 404 errors)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant