Deactivate Plugins Per Page v1.14.3 – Improve WordPress Performance
Download Free Deactivate Plugins Per Page – Improve WordPress Performance v1.14.3 Nulled
Deactivate Plugins Per Page – Improve WordPress Performance Free Download Nulled 1.14.3 – CodeCanyon | Deactivate Plugins Per Page v1.14.3 – Improve WordPress Performance is a premium tool that helps you a lot for making your site faster on the web. You can easily disable plugins on certain WordPress pages with “Deactivate plugins per page” (or on all except a selected page).
This is useful to speed up your site mainly because many JavaScript and CSS plugins are loaded on every page, even if you use them on one page.
For active plugins, you can add deactivation rules. You can for instance just add a rule to disable a contact form plugin on all URIs, except on the contact page.
A brief introduction to the plugin
If you are like most WordPress users, you have plugins that you use and plugins that you don’t. Some you activate and others you deactivate. But is there a way to improve WordPress performance by deactivating plugins per page?
Yes, there is! By deactivating plugins per page, you can reduce the amount of data that WordPress needs to process in order to display your blog posts and pages. This can improve your WordPress performance by reducing the load time of your website.\n
To deactivate a plugin using the wp_enqueue_plugin() function, include the following code in your theme’s functions.php file:
wp_enqueue_plugin( ‘deactivate-plugins’, array( ‘version’ => ‘1.0’ ) );
You can also deactivate plugins using the deactivate-plugins plugin. After installing the plugin, click on its toolbar button and select Deactivate Plugins From Page. Then enter the Plugin name (without the .php extension) or ID into the dialog box that appears and click Activate.
Why do you need this plugin?
Plugin deactivation can improve WordPress performance by freeing up memory and resources.
Plugin deactivation can also help you keep your WordPress site clean and organized.
How to deactivate plugins per page?
To deactivate a plugin per page, open the Plugins admin panel and select the plugin you want to deactivate. Then click the Deactivate button next to the Plugin Name field.
Group plugins that work together
You must add these plugins in a plugin group, and add deactivation rules in that group if you have a plugin that requires that another plugin is active to operate. If only one of these is disabled, the other plugin might cause errors or disability globally.
Don’t deactivate plugins required by your theme
Certain subjects require some plugins to function correctly. You may have problems if you disable these plugins.
Final Tips
If you’re looking to speed up your WordPress site, you may want to consider deactivating plugins per page. This simple optimization can help reduce the load time of your site by clearing out unnecessary files and dependencies.
By deactivating plugins on a per-page basis, you can prevent plugin conflicts from occurring and ensure that each plugin loads only when it’s actually needed. Here are a few tips for disabling plugins per page:
- Use the wp_plugins table to disable plugins. This is the most efficient way to disable plugins because it doesn’t require any PHP code or database access. To disable a plugin using the wp_plugins table, enter its name into the WordPress database table and press Enter. The following code disables the Yoast SEO plugin:
wp_plugin_disabled(“yoast_seo”);
- Use the Disable Plugin function in the admin panel. This function allows you to disable a specific plugin without affecting any other plugins or settings. To use the Disable Plugin function, go to Settings > Media > WP Security and click on the Disable Plugin link in the Security section. The following code disables the Contact Form 7 plugin:
disable_plugin(“contactform
https://codecanyon.net/item/deactivate-plugins-per-page-improve-wordpress-performance/23801359
Nulled Deactivate Plugins Per Page 1.14.3
Changelog Deactivate Plugins Per Page Nulled Improve WordPress Performance
1.14.3 - 14 April 2022
FIXED:
- The settings were not showing correct values in Firefox after importing new values due to Firefox trying to autocomplete the old values after page reload.
1.14.2 - 9 April 2022
FIXED:
- Assets not loading and incorrect paths when used in WAMP on Windows, due to incorrect directory separator. The PHP constant DIRECTORY_SEPARATOR has been removed now from the plugin.
1.14.1 - 16 January 2022
ADDED:
- An option to choose the priority of the hook we use to change the active_plugins option. In some cases changing this value will solve a conflict with another plugin (but may also cause a conflict with a different plugin).
REMOVED:
- The fix of the conflict with BuddyBoss plugin in combination with MemberPress Plus and MemberPress + BuddyPress Integration is removed by default. To enable it change the new option called “Priority†to 0.
UPDATED:
- Language files.
1.14.0 - 15 January 2022
ADDED:
- A new rule action that allows you to copy and paste rules from one plugin or group to another.
ADDED:
- An option to hide plugins with no rules if they are in at least one group.
FIXED:
- If there were skipped page rules when importing, the page IDs were not listed after the import.
- If an ajax request failed to be made due to a server error, it would show loading forever. Now shows an error.
- The plugin no longer works inside the visual editor screen of Elementor, Divi, and WPBakery Page Builder.
- A conflict with the BuddyBoss plugin in combination with MemberPress Plus and MemberPress + BuddyPress Integration.
- A conflict with Tutor LMS Pro in combination with the GeoDirectory plugin.
REMOVED:
- Support for custom REST-API address when trying to skip affecting it by our rules, was removed due to plugin conflicts.
UPDATED:
- Language and documentation files.
Categories: CodeCanyon, Plugins, Utilities
← Back home