Skip to content

Fixes issue with incorrect urls in signup and activation flow for mul… - #12257

Closed
hasukmistry wants to merge 6 commits into
WordPress:trunkfrom
hasukmistry:ticket-65506
Closed

hasukmistry wants to merge 6 commits into
WordPress:trunkfrom
hasukmistry:ticket-65506

Conversation

@hasukmistry

@hasukmistry hasukmistry commented Jun 22, 2026 •

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

Hi there! 👋

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

github-actions Bot commented Jun 22, 2026 •

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 meet_hasmukh, 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.

Comment thread src/wp-activate.php Outdated
Comment thread src/wp-signup.php Outdated

@westonruter westonruter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

Comment thread src/wp-activate.php
esc_url( wp_lostpassword_url() )
);
} else {
$url = ( is_ssl() ? 'https://' : 'http://' ) . $signup->domain . $blog_details->path;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

When analyzing at the changes in this PR with PHPStan, I found 3 errors:

  156    Binary operation "." between 'http://'|'https://' and mixed results in an error.
         🪪  binaryOp.invalid
  156    Cannot access property $domain on mixed.
         🪪  property.nonObject
  156    Cannot access property $path on WP_Site|null.
         🪪  property.nonObject

These are not introduced by this PR, but in the interest of cleaning such issues up as we go, I've added a couple commits to this PR to address type issues with the related code.

pento pushed a commit that referenced this pull request Jul 7, 2026
When an already-active signup is revisited, `wp-activate.php` hard-coded the `http://` scheme and passed the scheme-less domain and path through `esc_url()`, which prepended its own `http://` and produced a doubled, broken `http://http://` link. Build the full URL with the correct scheme from `is_ssl()` before escaping it.

Additionally, the signup confirmation heading in `wp-signup.php` now uses a scheme-relative `//` URL so the link honors the network's HTTPS configuration instead of forcing `http`.

This also hardens related code in `wp-activate.php` and `wpmu_activate_signup()` against type issues surfaced by PHPStan, including normalizing the signup meta to always be an array.

Developed in #12257.
Follow-up to r12603, r48672, r57625.

Props meet_hasmukh, westonruter.
See #64898.
Fixes #65506.


git-svn-id: https://develop.svn.wordpress.org/trunk@62651 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62651
GitHub commit: c236f38

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions Bot closed this Jul 7, 2026
markjaquith pushed a commit to markjaquith/WordPress that referenced this pull request Jul 7, 2026
When an already-active signup is revisited, `wp-activate.php` hard-coded the `http://` scheme and passed the scheme-less domain and path through `esc_url()`, which prepended its own `http://` and produced a doubled, broken `http://http://` link. Build the full URL with the correct scheme from `is_ssl()` before escaping it.

Additionally, the signup confirmation heading in `wp-signup.php` now uses a scheme-relative `//` URL so the link honors the network's HTTPS configuration instead of forcing `http`.

This also hardens related code in `wp-activate.php` and `wpmu_activate_signup()` against type issues surfaced by PHPStan, including normalizing the signup meta to always be an array.

Developed in WordPress/wordpress-develop#12257.
Follow-up to r12603, r48672, r57625.

Props meet_hasmukh, westonruter.
See #64898.
Fixes #65506.

Built from https://develop.svn.wordpress.org/trunk@62651


git-svn-id: http://core.svn.wordpress.org/trunk@61936 1a063a9b-81f0-0310-95a4-ce76da25c4cd
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