Module Disable Plugin For Debug: test your WordPress site without breaking everything

When you're working on a WordPress site in production, it's never pleasant to have to deactivate plugins just to do a test. This can disrupt visitors, break functionality or impact SEO. To solve this problem, we've developed the Disable Plugin For Debug in WPMasterToolKit.

This module allows you to temporarily disable all or some WordPress plugins for your use onlybased on your IP address, a cookie or a special link. So you can debug your site without affecting other users.

Which plugins can Disable Plugin For Debug replace?

This module replaces plugins such as "Debug Mode or "Plugin Organizerwhich allow you to control the loading of certain plugins. What's the difference?
WPMasterToolKit integrates this function natively, lightly and above all conditionally - without burdening your site or executing unnecessary code.

An intelligent approach with MU-plugin

Technically, this module creates a Must-Use Plugin (MU-plugin).
This type of plugin loads before all the others, allowing it to check the list of active extensions as soon as WordPress starts.

Depending on your settings, the module can :

• Load only the plugins selected for the debugging session ;
• Ignore all others, without actually disabling them in the administration.

Visitors continue to see the site with all active pluginswhile youThanks to your access conditions, see a lighter version ideal for testing.

Flexible activation conditions

You can choose how the module recognizes a "debugging session":

• IP address activates debug mode for a specific IP (often yours);
• Cookie activates the mode via a cookie stored in your browser;
• IP or Cookie (dual mode): more practical for multi-device testing.

It is also possible to generate a single debug link.
This link contains a secure token which, once opened, automatically adds the debug cookie to your browser. From then on, your debug session is active until you close your browser.

Choose which plugins to keep during debugging

The module displays a complete list of the site's plugins - both active and inactive - and allows you to check off the ones you want. keep active in the test session.

For example:

• You can activate only WPMasterToolKit and Elementor to test a page layout ;
• Or insulate WooCommerce to examine a bug without interfering with other extensions.

This granular approach provides a total control over the debugging environmentwithout ever altering the actual configuration of the site.

How to use the Disable Plugin For Debug module

1. Activate the in WPMasterToolKit.
2. Go to WPMasterToolKit → Disable Plugin For Debug.
3. Select condition type (IP, Cookie, or both).
4. Copy the debug link or enter your IP.
5. Select plugins to keep active during the session.
6. Open your link or visit the site from the configured IP - you're now in private debugging mode!

Visitors, on the other hand, continue to see the full site, unchanged.

Our technical choices

We opted for an architecture based on a MU-plugin autonomous :

• This plugin is automatically copied into the mu-plugins when the module is activated.
• It acts via native filters option_active_plugins and option_active_sitewide_pluginswhich guarantees perfect compatibility with WordPress multisite.
• No additional SQL queries are performed, and the system consumes no resources when deactivated.

In addition, the URL parameter used for the debug link (?wpmtk-disable-plugin-for-debug=) is filterable via the hook :

apply_filters( 'wpmastertoolkit/disable-plugin-for-debug/debug-param', 'wpmtk-disable-plugin-for-debug' );

This allows developers to customize parameter name according to their needs.

Conclusion

The module Disable Plugin For Debug WPMasterToolKit is a real revolution for WordPress developers and integrators.
With it, you can :

• Test configurations without disturbing your visitors;
• Quickly identify the source of a conflict between plugins ;
• Simulate staging environments directly on an online site.

An elegant, secure and 100 % solution that respects WordPress best practices.
A must-have for any WordPress site in production.