Skip to content

bugfix: allow valid special chars in email#9522

Open
JDeepD wants to merge 4 commits intoWordPress:trunkfrom
JDeepD:fix/specialchars-in-email
Open

bugfix: allow valid special chars in email#9522
JDeepD wants to merge 4 commits intoWordPress:trunkfrom
JDeepD:fix/specialchars-in-email

Conversation

@JDeepD
Copy link

@JDeepD JDeepD commented Aug 19, 2025

This commit fixes problems associated with emails containing valid special characters. See #54416 for more details.

Trac ticket: #54416

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.

@github-actions
Copy link

github-actions bot commented Aug 19, 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 jdeep, mindctrl.

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

@github-actions
Copy link

Hi @JDeepD! 👋

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

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.

@mindctrl
Copy link

@JDeepD if you update your fork with the latest trunk changes and then rebase your PR, the test suite will run as intended.

@JDeepD JDeepD force-pushed the fix/specialchars-in-email branch from 529afec to 786d1f8 Compare August 26, 2025 17:35
@JDeepD
Copy link
Author

JDeepD commented Aug 26, 2025

@JDeepD if you update your fork with the latest trunk changes and then rebase your PR, the test suite will run as intended.

Done

This commit fixes problems associated with emails
containing valid special characters. See #54416
for more details.
@JDeepD JDeepD force-pushed the fix/specialchars-in-email branch from 786d1f8 to 2d1ec28 Compare September 9, 2025 10:17
// Escape data pulled from DB.
$user = add_magic_quotes( $user );
$user = add_magic_quotes( $user );
$user['user_email'] = wp_unslash( $user['user_email'] );
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've noted that this doesn't change anything in the result. If the email comes sanitized from user-edit.php it will be updated correctly.

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.

3 participants