Skip to content

Trac 66238 : Users: Treat email addresses that differ only in letter case as the same. - #14209

Open
rvpatel wants to merge 12 commits into
WordPress:trunkfrom
rvpatel:trac-66238
Open

rvpatel wants to merge 12 commits into
WordPress:trunkfrom
rvpatel:trac-66238

Conversation

@rvpatel

@rvpatel rvpatel commented Oct 12, 2026

Copy link
Copy Markdown

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

Replaces #14053, which was opened from a nested fork. Previous review history is there.

What

email_exists() now matches emails case-insensitively regardless of the DB collation, so ABc@example.com can't be registered when abc@example.com exists. 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 the user_email column has a case-sensitive collation (*_bin, *_cs) or the collation can't be determined. With the default *_ci collation, 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 *_ci collations 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 the wp_is_user_email_case_sensitive filter.

Testing

  1. npm run test:php -- --group 66238 (covers both the case-insensitive and case-sensitive paths, including a successful LOWER() fallback when the exact lookup misses).
  2. Create a user abc@example.com, then try to add ABc@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.

rvpatel and others added 12 commits October 6, 2026 20:41
…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.
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.
- 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.
@github-actions

Copy link
Copy Markdown

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 ravipatel, westonruter.

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

@github-actions

Copy link
Copy Markdown

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

  • 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.

@westonruter

westonruter commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

I did several rounds of review on the #14053 which was migrated over to this new PR.

Per #14053 (review):

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.

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.

2 participants