Fix wp core update-db --network to respect network ID in multinetwork installations

[Copilot]

• Understand the current implementation and issue
• Filter sites by the current network's site_id
• Fix get_current_network_id() to be called first
• Update documentation with multinetwork example
• Add proper two-network test
• Fix CI failure: correct approach for verifying multinetwork isolation

Root cause of the persistent CI failure

The SITE_ID_CURRENT_SITE constant swap in wp-config.php cannot change the active network context because wp-config.php also hardcodes BLOG_ID_CURRENT_SITE=1. During the WordPress multisite bootstrap, ms_load_current_site_and_network() detects that blog 1's site_id (1) does not match the SITE_ID_CURRENT_SITE value (2) and overrides $current_site back to network 1. get_current_network_id() therefore always returns 1, regardless of the SITE_ID_CURRENT_SITE change.

New test strategy

Rather than switching network context (which requires changing both SITE_ID_CURRENT_SITE and BLOG_ID_CURRENT_SITE to values we don't know statically), the test proves the filtering works by:

1. Setup: 5 sites total — 3 in network 1 (active, belong to the current context) and 2 in network 2 (moved via direct DB update)
2. Assert 3/3 not 5/5: Without the site_id filter, the old code would process all 5 active sites (5/5). Seeing 3/3 proves the filter is active.
3. Assert net2-site1 absent from STDOUT: Explicitly proves the network-2 site was not touched.

This is a valid regression test for the fix: it would fail on the un-patched code.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>wp core update-db --network only updates the first network for "multinetwork" install</issue_title>
<issue_description>Hello! I've been trying something but doesn't work fine.

I have a WordPress MultiNetwork installed (for a client) and I've been trying to do this command wp core update-db like a network, but doesn't update everything.

wp core update-db --network --path=/web/example.com/

This updates the "first" multisite, as expected.

But, there are 2 networks, and inside each one, there are some subsites. If I execute

wp core update-db --network --url="network1.com" --path=/web/example.com/

Or any other "url" it always executes the first multisite in the network.

I think there are 2 possibles solutions there. The first one (I think that will the best one) is to run

wp core update-db --network --path=/web/example.com/

and check all the subsites (whatever network they are). I think maybe check all the sites in the database active or not (because archived sites should also update the database tables).

The other case may be to use the --url parameter with the main hostname (in a multinetwork you have hostnames and then subfolders), so if you use the --url parameter, check al the sites for this network.</issue_description>

Comments on the Issue (you are @copilot in this section)

@danielbachhuber Thanks for the report, @javiercasares !

The other case may be to use the --url parameter with the main hostname (in a multinetwork you have hostnames and then subfolders), so if you use the --url parameter, check al the sites for this network.

I think this approach probably makes more sense.

Out of curiosity, how does WordPress core handle this for the web?</comment_new>

• Fixes wp core update-db --network only updates the first network for "multinetwork" install #224

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[codecov]

Codecov Report

❌ Patch coverage is 77.77778% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/Core_Command.php	77.77%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[swissspidy]

@copilot still failing, the update appears to be running on 3 sites, not 2.

001 Scenario: Update db targets only the specified network in multinetwork setup # features/core-update-db.feature:156
      Then STDOUT should contain:                                                # features/core-update-db.feature:201
        $ wp core update-db --network
        WordPress database already at latest db version 47018 on example.com/
        WordPress database already at latest db version 47018 on example.com/net1-site1/
        WordPress database already at latest db version 47018 on example.com/net1-site2/
        Success: WordPress database upgraded on 3/3 sites.
        
        cwd: /tmp/wp-cli-test-run--69b038d7460435.28429357/
        run time: 0.82551288604736
        exit status: 0
        
        --- Expected
        +++ Actual
        @@ @@
        -Success: WordPress database upgraded on 2/2 sites.
        +WordPress database already at latest db version 47018 on example.com/
        +WordPress database already at latest db version 47018 on example.com/net1-site1/
        +WordPress database already at latest db version 47018 on example.com/net1-site2/
        +Success: WordPress database upgraded on 3/3 sites.