Plugin Toggle

By Cedaro

★ 4.8/5 (18 ratings)500+ active installationsVersion 1.3.1

Quickly toggle plugin activation status from the toolbar.

Description

For those times when you’re too lazy to visit the Plugins screen to toggle a plugin on or off.

It’s also helpful when troubleshooting:

This simple plugin is awesome, especially when it comes to diagnosing problems. One of the tenants of troubleshooting WordPress is to disable every plugin and re-enable them one by one in a process of elimination.

Generally, this is accomplished by having the plugin management page in one browser tab with the front end of the website in another. When a plugin is deactivated, switch browser tabs and refresh to see if the problem disappears. Depending on the speed of your site and the number of plugins installed, this can be a cumbersome experience.

— Jeff Chandler, WP Tavern

Additional Resources

Installation

Install Plugin Toggle like any other plugin. Check out the codex if you have any questions.

Screenshots

Changelog

1.3.1 – December 27, 2016

  • Listed plugins vertically in columns to make scanning easier and decrease disruption when adding or removing plugins.
  • Attempt to detect scenarios where the admin screen being viewed is unavailable after deactivating a plugin and redirect to the Manage Plugins screen instead.

1.3.0 – December 1, 2016

1.2.0

  • Internationalize the plugin to add support for language packs.
  • Only load JavaScript and CSS files on the frontend when the toolbar is enabled.

1.1.6

  • Increase the opacity of inactive plugins and bold active plugins to improve legibility.

1.1.5

  • Set up the plugin on init instead of plugins_loaded to prevent issues with calling current_user_can() too early.

1.1.4

  • Check for changes to the plugins directory or list of active plugins to determine if the cached plugins list should be refreshed.

1.1.3

  • Display an error on the plugins screen if there’s an issue during (de)activation.

1.1.2

  • URL encode redirect URLs to prevent query string conflicts.

1.1.1

  • Prevent a fatal error on activation due to stomping a variable passed by reference.

1.1.0

  • Refactored the codebase to improve performance and legibility.

1.0.0

  • Initial release.