Custom URL Settings, How to Deactivate Plugins by Custom URL
With the Custom URL Settings, you can disable specific plugins based on the page URL.
You can use the asterisk (*) as a wildcard to replace any group of characters.
Example:
http://localhost/freesoul_development*example/
will match URLs such as:
http://localhost/freesoul_development/an-example/http://localhost/freesoul_development/another-example/
You can also disable plugins based on URL query parameters.
Example:
*?example-parameter=true*
will match URLs such as:
http://localhost/freesoul_development?example-parameter=truehttp://localhost/freesoul_development/page-example/?example-parameter=true
Behavior in the PRO Version
In the PRO version, if you activate the filter (as shown in the image), the plugins that are unchecked in that row will be disabled when the URL matches the pattern.
However, the active plugins will still be determined by all the other FDP settings (such as Singles, Post Types, etc.).
Example:
As shown in the image, the plugins Query Monitor, All In One WP Migration, All In One WP Migration Unlimited Extension, and All Pages In Customize are disabled when the URL includes /blog — for example, https://yoursite.com/blog.
This means:
For any URL that contains
/blog, never load these plugins.
You are not specifying which plugins should be loaded — only which ones should not be loaded when the URL matches the pattern */blog.
If the filter is not activated, FDP will instead load only the plugins that are checked in that specific row, ignoring the other settings (like Singles and Post Types).