WIP: Trac-27994: Bypass plugin file exists check when user visits plugin.php

[vishalkakadiya]

Details

This PR will fix the first step of the track ticket related to bypassing the plugin file exists check, so if the user has multiple WP instances running, working with various branches and on renaming the plugin directory, the active plugins will not be directly deactivated on visiting wp-admin/plugins.php

Next steps

As discussed in the ticket, we need to implement logic to show all the plugins in the list which have been renamed or removed, and the admin can manually deactivate those plugins. From the technical side, we need to call deactivate_plugins() and pass the plugin file's path, which is removed or renamed, to remove that from the active plugin's list.

Trac

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

[github-actions]

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: @[email protected].

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

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

[github-actions]

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

• The Plugin and Theme Directories cannot be accessed within Playground.
• 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.