Repository navigation
Conversation
…ame. `email_exists()` now matches email addresses case-insensitively regardless of the database collation, so a second account cannot be created with an address that only differs in letter case (for example `abc@example.com` and `ABc@example.com`). With the default case-insensitive collation of the users table, the existing lookup already ignores letter case and uses the `user_email` index, so no extra query is made. The `LOWER()` fallback, which cannot use the index, only runs when the `user_email` column has a case-sensitive collation or the collation cannot be determined. This is detected once per request by the new private `_wp_is_user_email_case_sensitive()` function, and can be overridden with the `wp_is_user_email_case_sensitive` filter. The Users list table also flags users on the current page whose email address is shared with another account, ignoring letter case, so that existing duplicates can be found and cleaned up. The lookup only uses the addresses on the current page and is index-friendly on case-insensitive collations. See #66238.
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
Please add the AI disclosure to the PR description: wordpress-develop/.github/pull_request_template.md Lines 22 to 33 in 79ff428 |
| function _wp_is_user_email_case_sensitive() { | ||
| global $wpdb; | ||
|
|
||
| static $is_case_sensitive = array(); |
There was a problem hiding this comment.
Why is this an array when it only ever has one item in it?
There was a problem hiding this comment.
Good point. The users table is global, so it's now a single cached value. Fixed in e0f0583.
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
* Return a list of user IDs from get_duplicate_email_user_ids() instead of an ID-keyed map. * Cache the collation check in _wp_is_user_email_case_sensitive() as a single value, since the users table is global. See #66238.
|
Thanks @westonruter! Just a heads-up: my fork was created from another fork (ravikumarup/wordpress-develop) rather than directly from WordPress/wordpress-develop, so "Allow edits by maintainers" may not let you push to this branch. To avoid that, I've invited you as a collaborator on rvpatel/wordpress-develop. Once you accept the invitation, you should be able to push changes directly to the |
|
@westonruter The PR has been updated to address the review feedback: the LOWER() lookup now runs only when the user_email column uses a case-sensitive collation, so the default *_ci setup keeps using the index. It's also up to date with trunk and all checks pass. Ready for another review when you have time. |
westonruter
left a comment
There was a problem hiding this comment.
The changes look good to me. But I don't have a lot of experience with users, so best if I let someone else pick this up the review from here.
| * | ||
| * @return bool True if user email comparisons are case-sensitive, false otherwise. | ||
| */ | ||
| function _wp_is_user_email_case_sensitive() { |
There was a problem hiding this comment.
| function _wp_is_user_email_case_sensitive() { | |
| function _wp_is_user_email_case_sensitive(): bool { |
There was a problem hiding this comment.
🟡 Changes recommended
A list-table test passes IDs where user objects are required, and successful fallback lookup remains untested.
2 open findings
What changed in this PR
Makes email uniqueness checks case-insensitive across database collations and identifies legacy duplicate addresses.
Changes:
- Adds collation-aware email lookup fallback.
- Highlights duplicate emails in the Users table.
- Adds related PHPUnit coverage and styling.
| File | Description |
|---|---|
src/wp-includes/user.php |
Adds collation detection and case-insensitive fallback. |
src/wp-admin/includes/class-wp-users-list-table.php |
Detects and displays duplicate-email warnings. |
src/wp-admin/css/list-tables.css |
Styles duplicate-email warnings. |
tests/phpunit/tests/user.php |
Tests email lookup and insertion behavior. |
tests/phpunit/tests/admin/wpUsersListTable.php |
Tests duplicate detection and display. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| }; | ||
| add_filter( 'query', $collect ); | ||
|
|
||
| $flagged = $method->invoke( $this->table, array( $original, $unique ) ); |
| $this->assertSame( $user_id, email_exists( 'mixedcase@example.com' ), 'Lowercase variant should match.' ); | ||
| $this->assertSame( $user_id, email_exists( 'MIXEDCASE@EXAMPLE.COM' ), 'Uppercase variant should match.' ); |
- Pass `WP_User` objects to `get_duplicate_email_user_ids()` in the test, matching the updated signature. - Add a `bool` return type to `_wp_is_user_email_case_sensitive()`. - Add a test covering a successful `LOWER()` fallback when the exact lookup misses.
|
Comment on old #14053. It should already be closed automatically because you deleted the fork, but it still accepts comments |

Trac ticket: https://core.trac.wordpress.org/ticket/66238
What
email_exists()now matches emails case-insensitively regardless of the DB collation, soABc@example.comcan't be registered whenabc@example.comexists. The Users list table flags existing case-variant duplicates so they can be cleaned up.Index tradeoff (from Trac feedback)
The
LOWER(user_email)lookup now only runs when theuser_emailcolumn has a case-sensitive collation (*_bin,*_cs) or the collation can't be determined. With the default*_cicollation, the existing indexed lookup already ignores case, so no extra query is made.The list table check only queries the email addresses on the current page, using
user_email IN (...)on*_cicollations so the index is used.Collation detection is cached per request in the private
_wp_is_user_email_case_sensitive()and can be overridden with thewp_is_user_email_case_sensitivefilter.Testing
npm run test:php -- --group 66238(covers both the case-insensitive and case-sensitive paths).abc@example.com, then try to addABc@example.com: it should be rejected with "This email address is already registered".Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Reworking the patch to address the Trac feedback (limiting the LOWER() lookup to case-sensitive collations), the list table query, PHPUnit tests, and running PHPCS/PHPUnit/PHPStan; also the latest review fixes. I reviewed and tested the final implementation and take responsibility for it.