Quick Description
With “Deactivate Plugins Per page” you may simply disable plugins on sure WordPress pages (or on all besides a particular web page). That is helpful for rushing up your website primarily as a result of many front-end plugins will load their JavaScript and CSS belongings on each web page, even if you happen to use them on one web page.
The way it works?
You possibly can add deactivation guidelines for lively plugins. For instance for a contact kind plugin, that you just solely use on the contact web page, merely add a rule to deactivate it on all URI besides on the contact web page.
Deactivation Guidelines Choices
1. Deactivation Kind
– Deactivate on chosen URI
– Deactivate on all URI besides chosen
2. URI choice sort
– Web page
– Customized
3. [Page] Choose pages to extract URI from (it’ll replace robotically if the web page slug adjustments)
3. [Custom] Customized URI situation
– URI equals …
– URI doesn’t equal …
– URI comprises …
– URI doesn’t include …
– URI begins with …
– URI doesn’t begin with …
– URI ends with …
– URI doesn’t finish with …
– URI matches the common expression.
Plugin Teams
Create teams of a number of plugins in an effort to add deactivation guidelines that have an effect on all of them.
Debug Mode
Allow debug mode to see what’s the URI and which plugins are lively/inactive on the present web page on the front-end. It will show you how to create guidelines and take a look at present ones. A debug field will seem on the front-end in case you are an administrator person.
Does it have an effect on the Again-end?
There’s an choice (not enabled by default) that makes all guidelines with Customized URI choice to additionally have an effect on the back-end. Some back-end pages will nonetheless not be affected in an effort to keep away from issues, just like the pages that management plugin activation, deactivation, updates, and set up.
Export/Import Guidelines and Settings
Since model 1.9.0 you may export all of your deactivation guidelines and settings of the plugin and import them on one other website. Guidelines with Web page URI choice sort, might be skipped if the identical pages (each similar ID and slug) don’t exist on the vacation spot website. In a multisite you may import into a number of websites directly.
Customized PHP perform as situation
Since model 1.15.0 you may add the identify of your personal PHP perform to a deactivation rule so it’s used as a further situation. The rule will solely work in case your perform additionally returns true. The perform should be loaded in a should use plugin so it’s obtainable earlier than common plugins load.
Precautions
Group plugins that work collectively
You probably have a plugin that requires one other plugin to be lively in an effort to work, it is advisable to add these plugins in a plugin group, and add deactivation guidelines to that group. Deactivating solely considered one of these may result in errors or the worldwide deactivation of the opposite plugin.
Don’t deactivate plugins required by your theme
Some themes require sure plugins in an effort to work correctly. Should you deactivate these plugins it’s possible you’ll expertise issues.
Deactivation hooks won’t run
When plugins are deactivated by way of my plugin, the precise deactivation perform is just not known as, and the deactivation hooks won’t run. As an alternative, to make it work per web page, plugins are simply dynamically faraway from the record of lively plugins earlier than the web page masses. Because of this if a plugin has some actions that it performs when it’s deactivated, these actions won’t run when it’s deactivated by way of my plugin.
For instance, some plugins add code to your ”.htaccess” file when they’re activated, and when they’re deactivated, they take away it. On this case if you happen to add a deactivation rule with my plugin to cease the plugin on a sure web page, the ”.htaccess” code will nonetheless be there and work on that web page, although the plugin won’t be lively on it.
Don’t use this plugin to cover delicate information
It’s not made to work securely for that. It’s primarily made for website velocity optimization and it may also be used for debugging or fixing plugin compatibility points.
Backup your website
Deactivating plugins per web page is just not a pure factor for WordPress, and plugin and theme builders should not anticipating that. It really works nice usually, however typically can result in issues, to different plugins being deactivated or settings being modified. At all times have a latest backup of your website and if you happen to can, take a look at your adjustments in a staging website.
Demo: https://codecanyon.net/item/deactivate-plugins-per-page-improve-wordpress-performance/23801359
Download Deactivate Plugins Per Page
See also:
