[ad_1]
To get this product on 50 % low cost contact me on this link
Short Description
With “Deactivate Plugins Per Page” you’ll be able to simply disable plugins on sure WordPress pages (or on all besides a specific web page).
This is beneficial for dashing up your web site primarily as a result of many entrance-finish plugins will load their JavaScript and CSS belongings on each web page, even for those who use them on one web page.
How it really works?
You can add deactivation guidelines for energetic plugins. For instance for a contact type plugin, that you simply solely use on the contact web page, merely add a rule to deactivate it on all URI besides on the contact web page.
Deactivation Rules Options
1. Deactivation Type
– Deactivate on chosen URI
– Deactivate on all URI besides chosen
2. URI choice kind
– Page
– Custom
3. [Page] Select pages to extract URI from (it can replace mechanically if the web page slug modifications)
3. [Custom] Custom URI situation
– URI equals …
– URI doesn’t equal …
– URI incorporates …
– URI doesn’t include …
– URI begins with …
– URI doesn’t begin with …
– URI ends with …
– URI doesn’t finish with …
4. Affected units
– All
– Desktop
– Mobile
Plugin Groups
Create teams of a number of plugins as a way to add deactivation guidelines that have an effect on all of them.
Debug Mode
Enable debug mode to see what’s the URI and which plugins are energetic/inactive on the present web page on the entrance-finish. This will assist you create guidelines and take a look at present ones. A debug field will seem on the entrance-finish in case you are an administrator person.
Does it have an effect on the Back-end?
There is an possibility (not enabled by default) that makes all guidelines with Custom URI choice to additionally have an effect on the again-finish. Some again-finish pages will nonetheless not be affected as a way to keep away from issues, just like the pages that management plugin activation, deactivation, updates, and set up.
Plugin Settings
Some issues to bear in mind
When plugins are deactivated through my plugin, the precise deactivation operate shouldn’t be known as, and the deactivation hooks won’t run. Instead, to make it work per web page, plugins are simply dynamically faraway from the listing of energetic plugins earlier than the web page masses. This implies that if a plugin has some actions that it performs when it’s deactivated, these actions won’t run when it’s deactivated through 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. In this case for those who 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 energetic on it.
Feedback / Support / Questions
Use the support section (requires signal-in), or my e mail [email protected]
Changelog
1.10.0 – 30 January 2020
ADDED: In debug mode now you can carry out fast plugin actions for the present URI: deactivate on the present URI, deactivate on all besides the present URI, add a plugin to an present group.
ADDED: A button within the prime proper of the debug field that reloads the web page.
IMPROVED: A discover about caching plugins is proven when altering the affected units menu within the add/edit rule field.
FIXED: When importing the foundations and settings, an error about invalid import knowledge despatched was proven, if one of many plugins has a reputation beginning with an empty area.
FIXED: When WP CLI is used, a warning was generated: Warning: in_array() expects parameter 2 to be array, null given…
UPDATED: Language recordsdata.
1.9.0 – 13 November 2019
ADDED: Global actions to export or import all guidelines, teams, and settings of “Deactivate Plugins Per Page”.
FIXED: The width of some drop-down containers in WordPress 5.3.
UPDATED: Language recordsdata.
TESTED: Compatibility with WordPress 5.3.
1.8.0 – 15 October 2019
ADDED: Five plugin (or group) actions: Front-end Deactivate, Back-end Deactivate, Start Plugin Rules, Pause Plugin Rules, Delete Plugin Rules.
ADDED: A textual content discipline to seek out pages when including or modifying a rule.
IMPROVED: Inactive plugins at the moment are proven in purple, when including or modifying teams.
IMPROVED: Removed this plugin from the energetic plugins part.
IMPROVED: Changed the icon for deleting a bunch, so it’s totally different from the one for deleting guidelines.
IMPROVED: Better responsive design for some parts on the admin web page.
IMPROVED: If enabled, the debug field is now seen on the again-finish whatever the setting for customized URI choice guidelines affecting the again-finish.
UPDATED: Language and documentation recordsdata.
1.7.0 – 7 September 2019
ADDED: An choice to ignore URI parameters when making use of guidelines with customized URI choice. Popular monitoring parameters like fbclid, fb_source, gclid, utm_medium, utm_source, and others are ignored by default.
ADDED: The sections within the admin web page at the moment are collapsible. You can present and conceal them. The sections are: energetic plugins, inactive plugins, plugin teams, settings.
ADDED: An icon that signifies which plugins are already a part of at the very least one plugin group, when creating or modifying a bunch.
FIXED: On the plugin admin web page, the again-finish notices from different plugins have been proven additional down on the web page (as an alternative of on the prime).
FIXED: A couple of spelling errors.
UPDATED: Language recordsdata.
1.6.0 – 9 August 2019
ADDED: An choice to ignore all URI parameters (aka the question string) within the present web page URI, when making use of the deactivation guidelines with Page URI choice. This method when some monitoring parameters are added to the URI (like for instance ?utm_source=fb&utm_medium=submit) the web page will nonetheless be recognised accurately by the plugin. Does not have an effect on plain permalink construction. This will probably be enabled by default.
FIXED: In the 1.5.Zero model, if debug mode was enabled and if we couldn’t copy mechanically the should-use plugin file to its folder, there was a PHP deadly error.
UPDATED: Language recordsdata.
1.5.0 – 5 August 2019
ADDED: An choice to additionally have an effect on the again-finish dashboard space by all guidelines with Custom URI choice.
ADDED: An possibility to regulate the trailing slash of Page URIs used contained in the deactivation guidelines.
IMPROVED: Changed some phrases within the admin space to be extra clear.
UPDATED: Language recordsdata.
1.4.1 – 9 July 2019
FIXED: When modifying a plugin group and a few of the plugins are presently not put in, although they present as chosen (inexperienced and with a checked checkbox), they don’t seem to be truly chosen.
1.4.0 – 8 July 2019
ADDED: The motion to edit a rule.
ADDED: The motion to edit a plugin group.
UPDATED: Language and documentation recordsdata.
1.3.0 – 25 June 2019
ADDED: The capability so as to add a number of customized situations in a single rule. This makes it doable for instance to deactivate a plugin on all URI besides if: the URI incorporates one thing, or if it ends with one thing, or another situation, and so forth.
ADDED: Links to filter pages by WPML language and in addition the flexibility to pick out pages from a number of languages within the Add New Rule field (if WPML is energetic).
ADDED: An possibility within the Add New Rule field to mechanically choose all translated pages with WPML of chosen pages (if WPML is energetic).
ADDED: An possibility to point out the Plugin Groups part earlier than the Active Plugins.
IMPROVED: The URI values of pages at the moment are up to date when the permalink construction is re-saved, even when there are not any precise modifications to it. This is useful when some plugin modifications the URIs and says to re-save the permalinks. Then we can even catch the URI change made by that plugin.
IMPROVED: In the foundations tables, the URI situations and URI values are in a single column now, with URI values in daring.
FIXED: Extracts incorrect URI of a web page translated with WPML.
FIXED: Adding the identical rule for a similar plugin, however with pages chosen in a distinct order, is not doable.
FIXED: A PHP warning about array_key_exists() expects parameter 2 to be array, bool given.
UPDATED: Language and documentation recordsdata.
1.2.0 – 4 June 2019
ADDED: A strategy to rapidly discover a plugin by typing part of its title in a textual content discipline. The different plugins are filtered out quickly.
ADDED: Global actions: pause all guidelines, begin all guidelines, and delete all guidelines.
ADDED: The capability to create plugin teams. Group two or extra plugins as a way to add deactivation guidelines that have an effect on all of them.
ADDED: An choice to take away all the information of this plugin upon its deletion (not for multisite).
ADDED: A warning within the plugin admin web page if the model of the should-use plugin file doesn’t match the model of the traditional plugin.
FIXED: One affirmation message and in addition the URI situation within the guidelines tables weren’t translatable.
FIXED: The language recordsdata will probably be loaded even when they’re solely current within the “languages” folder contained in the plugin folder and never current within the “wp-content/languages” folder.
FIXED: A small battle with the Autoptimize plugin that induced an arrow within the debug field to be seen when it must be hidden.
UPDATED: Language and documentation recordsdata.
1.1.0 – 14 May 2019
FIXED: When deciding on a number of pages for a rule that deactivates on all besides chosen, it might deactivate all over the place as an alternative.
UPDATED: Language recordsdata.
1.0.0 – 13 May 2019
Initial launch
[ad_2]
To get this product on 50 % low cost contact me on this link
