Add test coverage for network cache clearing on domain/path update

[Copilot]

Adds test coverage to validate cache behavior when updating a network's domain/path via the update_network() function.

Changes:

• Add test coverage: Added test_update_network_clears_cache() test case to validate that cache is properly cleared after network update

public function test_update_network_clears_cache() {
    // Create a test network.
    $network_id = $this->factory->network->create(
        array(
            'domain' => 'example.com',
            'path'   => '/test/',
        )
    );

    // Get the network to populate cache.
    $network = get_network( $network_id );
    $this->assertEquals( 'example.com', $network->domain, 'Network should have original domain' );
    $this->assertEquals( '/test/', $network->path, 'Network should have original path' );

    // Update the network with new domain and path.
    $result = update_network( $network_id, 'newdomain.com', '/newpath/' );
    $this->assertTrue( $result, 'Network update should succeed' );

    // Get the network again - it should reflect the updated values.
    $updated_network = get_network( $network_id );
    $this->assertEquals( 'newdomain.com', $updated_network->domain, 'Network should have updated domain without manual cache flush' );
    $this->assertEquals( '/newpath/', $updated_network->path, 'Network should have updated path without manual cache flush' );
}

This test ensures that the cache clearing mechanism works correctly when a network's domain and path are updated.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Sticky cache after changing a network's domain/path</issue_title>
<issue_description>After changing the domain/path of a network via

wp-multi-network/wp-multi-network/includes/functions.php

Line 634 in 66ac5b8

function update_network( $id, $domain, $path = '' ) {

, the old URL was still being populated via

wp-multi-network/wp-multi-network/includes/metaboxes/edit-network.php

Line 22 in 66ac5b8

$domain = ! empty( $network->domain )

until running wp_cache_flush.

We run clean_network_cache, which sounds like it should take care of it, but didn't. Still digging around on it.</issue_description>

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

@JJJ I've made a few modifications here.

Instead of calling refresh_blog_details() we are now calling clean_blog_cache() directly.

Curious if you have a better experience once 2.5.0 is released. 🙏</comment_new>

• Fixes Sticky cache after changing a network's domain/path #115

---

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

[JJJ]

@copilot Keep the tests but remove the changes to update_network() as they aren't quite right.

[Copilot]

@copilot Keep the tests but remove the changes to update_network() as they aren't quite right.

Reverted the update_network() changes in commit 2ed5b68. The test has been kept.

[Copilot]

Pull request overview

This pull request adds test coverage to validate that network cache is properly cleared when updating a network's domain and path through the update_network() function. This test addresses a previously reported issue where cache would remain stale after network updates, requiring manual cache flushing.

• Adds test_update_network_clears_cache() to verify cache clearing behavior
• Tests the complete update flow: create network, populate cache, update network, verify updated values
• Validates that the clean_network_cache() call in update_network() works correctly

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.