Skip to content

Networks and Sites: Add a Cancel link to site confirmation screens - #14227

Open
Sukhendu2002 wants to merge 1 commit into
WordPress:trunkfrom
Sukhendu2002:26861-site-delete-cancel
Open

Sukhendu2002 wants to merge 1 commit into
WordPress:trunkfrom
Sukhendu2002:26861-site-delete-cancel

Conversation

@Sukhendu2002

Copy link
Copy Markdown

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

Adds a Cancel link to the Network Admin site confirmation screens. Before this change they had only a submit button, so the only way back was the browser's back button.

As noted in comment:19, the explicit warning notice and the red "Delete Permanently" row action are already in trunk. A Cancel option is the remaining gap. This PR replaces the obsolete 26861.diff, which edited a msg query argument that no longer exists.

Testing instructions

  1. On a multisite install, go to Network Admin → Sites.
  2. Hover over a site and click Delete Permanently. Confirm that a Cancel link appears next to "Delete this site permanently".
  3. Click Cancel. You should return to the Sites list with your filters and paging kept, and the site should not be deleted.
  4. Open the confirmation URL directly, with no referer. Cancel should go to network/sites.php.
  5. Select several sites, choose Delete from Bulk actions, and click Apply. Confirm that Cancel appears and that clicking it deletes nothing.
  6. Repeat step 2 for Archive and Flag for Deletion.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude
Model(s): Claude Opus 5.5
Used for: Code review. Final implementation and tests were reviewed and edited by me.

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

@Sukhendu2002
Sukhendu2002 marked this pull request as ready for review October 13, 2026 07:48
@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 sukhendu2002.

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

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.

1 participant