Download: Deactivate Plugins Per Page – Improve WordPress Performance Free Nulled

Preview: Deactivate Plugins Per Page – Improve WordPress Performance

Short Description

With “Deactivate Plugins Per Page” you can easily disable plugins on certain WordPress pages (or on all except a selected page).

This is useful for speeding up your site mainly because many front-end plugins will load their JavaScript and CSS assets on every page, even if you use them on one page.

How it works?

You can add deactivation rules for active plugins. For example for a contact form plugin, that you only use on the contact page, simply add a rule to deactivate it on all URI except on the contact page.

Deactivation Rules Options

1. Deactivation Type
– Deactivate on selected URI
– Deactivate on all URI except selected

2. URI selection type
– Page
– Custom

3. [Page] Select pages to extract URI from (it will update automatically if the page slug changes)

3. [Custom] Custom URI condition
– URI equals …
– URI does not equal …
– URI contains …
– URI does not contain …
– URI starts with …
– URI does not start with …
– URI ends with …
– URI does not end with …

4. Affected devices
– All
– Desktop
– Mobile

Plugin Groups

Create groups of multiple plugins in order to add deactivation rules that affect them all.

Debug Mode

Enable debug mode to see what is the URI and which plugins are active/inactive on the current page on the front-end. This will help you create rules and test current ones. A debug box will appear on the front-end if you are an administrator user.

Does it affect the Back-end?

There is an option (not enabled by default) that makes all rules with Custom URI selection to also affect the back-end. Some back-end pages will still not be affected in order to avoid problems, like the pages that control plugin activation, deactivation, updates, and installation.

Plugin Settings

Some things to keep in mind

When plugins are deactivated via my plugin, the actual deactivation function is not called, and the deactivation hooks will not run. Instead, to make it work per page, plugins are just dynamically removed from the list of active plugins before the page loads. This means that if a plugin has some actions that it performs when it is deactivated, these actions will not run when it is deactivated via my plugin.

For example, some plugins add code to your ”.htaccess” file when they are activated, and when they are deactivated, they remove it. In this case if you add a deactivation rule with my plugin to stop the plugin on a certain page, the ”.htaccess” code will still be there and work on that page, even though the plugin will not be active on it.

Feedback / Support / Questions

Use the support section (requires sign-in), or my email [email protected]

Changelog

1.10.0 – 30 January 2020

ADDED: In debug mode you can now perform quick plugin actions for the current URI: deactivate on the current URI, deactivate on all except the current URI, add a plugin to an existing group.

ADDED: A button in the top right of the debug box that reloads the page.

IMPROVED: A notice about caching plugins is shown when changing the affected devices menu in the add/edit rule box.

FIXED: When importing the rules and settings, an error about invalid import data sent was shown, if one of the plugins has a name starting with an empty space.

FIXED: When WP CLI is used, a warning was generated: Warning: in_array() expects parameter 2 to be array, null given…

UPDATED: Language files.

1.9.0 – 13 November 2019

ADDED: Global actions to export or import all rules, groups, and settings of “Deactivate Plugins Per Page”.

FIXED: The width of some drop-down boxes in WordPress 5.3.

UPDATED: Language files.

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 text field to find pages when adding or editing a rule.

IMPROVED: Inactive plugins are now shown in red, when adding or editing groups.

IMPROVED: Removed this plugin from the active plugins section.

IMPROVED: Changed the icon for deleting a group, so it is different from the one for deleting rules.

IMPROVED: Better responsive design for some elements on the admin page.

IMPROVED: If enabled, the debug box is now visible on the back-end regardless of the setting for custom URI selection rules affecting the back-end.

UPDATED: Language and documentation files.

1.7.0 – 7 September 2019

ADDED: An option to ignore URI parameters when applying rules with custom URI selection. Popular tracking parameters like fbclid, fb_source, gclid, utm_medium, utm_source, and others are ignored by default.

ADDED: The sections in the admin page are now collapsible. You can show and hide them. The sections are: active plugins, inactive plugins, plugin groups, settings.

ADDED: An icon that indicates which plugins are already part of at least one plugin group, when creating or editing a group.

FIXED: On the plugin admin page, the back-end notices from other plugins were shown further down on the page (instead of at the top).

FIXED: A few spelling mistakes.

UPDATED: Language files.

1.6.0 – 9 August 2019

ADDED: An option to ignore all URI parameters (aka the query string) in the current page URI, when applying the deactivation rules with Page URI selection. This way when some tracking parameters are added to the URI (like for example ?utm_source=facebook&utm_medium=post) the page will still be recognised correctly by the plugin. Does not affect plain permalink structure. This will be enabled by default.

FIXED: In the 1.5.0 version, if debug mode was enabled and if we could not copy automatically the must-use plugin file to its folder, there was a PHP fatal error.

UPDATED: Language files.

1.5.0 – 5 August 2019

ADDED: An option to also affect the back-end dashboard area by all rules with Custom URI selection.

ADDED: An option to control the trailing slash of Page URIs used inside the deactivation rules.

IMPROVED: Changed some words in the admin area to be more clear.

UPDATED: Language files.

1.4.1 – 9 July 2019

FIXED: When editing a plugin group and some of the plugins are currently not installed, even though they show as selected (green and with a checked checkbox), they are not actually selected.

1.4.0 – 8 July 2019

ADDED: The action to edit a rule.

ADDED: The action to edit a plugin group.

UPDATED: Language and documentation files.

1.3.0 – 25 June 2019

ADDED: The ability to add multiple custom conditions in one rule. This makes it possible for example to deactivate a plugin on all URI except if: the URI contains something, or if it ends with something, or some other condition, etc.

ADDED: Links to filter pages by WPML language and also the ability to select pages from multiple languages in the Add New Rule box (if WPML is active).

ADDED: An option in the Add New Rule box to automatically select all translated pages with WPML of selected pages (if WPML is active).

ADDED: An option to show the Plugin Groups section before the Active Plugins.

IMPROVED: The URI values of pages are now updated when the permalink structure is re-saved, even if there are no actual changes to it. This is helpful when some plugin changes the URIs and says to re-save the permalinks. Then we will also catch the URI change made by that plugin.

IMPROVED: In the rules tables, the URI conditions and URI values are in one column now, with URI values in bold.

FIXED: Extracts incorrect URI of a page translated with WPML.

FIXED: Adding the same rule for the same plugin, but with pages selected in a different order, is no longer possible.

FIXED: A PHP warning about array_key_exists() expects parameter 2 to be array, bool given.

UPDATED: Language and documentation files.

1.2.0 – 4 June 2019

ADDED: A way to quickly find a plugin by typing a part of its name in a text field. The other plugins are filtered out temporarily.

ADDED: Global actions: pause all rules, start all rules, and delete all rules.

ADDED: The ability to create plugin groups. Group two or more plugins in order to add deactivation rules that affect them all.

ADDED: An option to remove all the data of this plugin upon its deletion (not for multisite).

ADDED: A warning in the plugin admin page if the version of the must-use plugin file does not match the version of the normal plugin.

FIXED: One confirmation message and also the URI condition in the rules tables were not translatable.

FIXED: The language files will be loaded even if they are only present in the “languages” folder inside the plugin folder and not present in the “wp-content/languages” folder.

FIXED: A small conflict with the Autoptimize plugin that caused an arrow in the debug box to be visible when it should be hidden.

UPDATED: Language and documentation files.

1.1.0 – 14 May 2019

FIXED: When selecting multiple pages for a rule that deactivates on all except selected, it would deactivate everywhere instead.

UPDATED: Language files.

1.0.0 – 13 May 2019

Initial release

TMDb Pro – Movie & TV Show Details Plugin For The Movie Database

Deactivate Plugins Per Page – Improve WordPress Performance

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industrys standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

Why do we use it?

It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using Content here, content here, making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for lorem ipsum will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).

Where does it come from?

Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of “de Finibus Bonorum et Malorum” (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, “Lorem ipsum dolor sit amet..”, comes from a line in section 1.10.32.

Where can I get some?

There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which dont look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isnt anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc.

Download Deactivate Plugins Per Page – Improve WordPress Performance Nulled

Download Deactivate Plugins Per Page – Improve WordPress Performance