Skip to content

Fix/plugins list status text delete counts#11777

Open
alessioarzenton wants to merge 3 commits intoWordPress:trunkfrom
alessioarzenton:fix/plugins-list-status-text-delete-counts
Open

Fix/plugins list status text delete counts#11777
alessioarzenton wants to merge 3 commits intoWordPress:trunkfrom
alessioarzenton:fix/plugins-list-status-text-delete-counts

Conversation

@alessioarzenton
Copy link
Copy Markdown

Improvement to PR: #11752.
This PR refactors the rendering of the | separator between filter links in WP_List_Table::views() (the .subsubsub navigation — e.g. "All | Active | Inactive" on the Plugins screen).

Before: the separator was hardcoded in the PHP output via implode( " |\n", $views ) in wp-admin/includes/class-wp-list-table.php.

After: PHP emits clean markup, and the separator is drawn in CSS via a ::after pseudo-element.

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

Use of AI Tools


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.

andreas-am and others added 3 commits May 7, 2026 18:44
…uginSuccess.

  Decrement counts for groups registered via the plugins_list filter when
  a plugin is deleted via AJAX, so tabs whose label is supplied through
  plugins_list_status_text (introduced in #60495) stay in sync without a
  page reload.

  See #65191.
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @andreas-am.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

Core Committers: Use this line as a base for the props when committing in SVN:

Props alessioarzentondev.

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

github-actions Bot commented May 8, 2026

Hi @alessioarzenton! 👋

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
Copy Markdown

github-actions Bot commented May 8, 2026

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.

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