One of WordPress' biggest bottlenecks is that it loads every single plugin that \nis active on your WordPress installation on every single post\/page no matter \nwhether they are needed for that post\/page or not. This plugin will allow you \nto create simple rewrite rules to exclude a plugin or plugins from any URI \npattern match. This is a great way to reduce the memory footprint, SQL queries \nrun at page load, load times, and improve site response speed.<\/p>\n\n
This is NOT a normal WordPress plugin, but an mu<\/em> (must use) plugin and requires\nspecial installation instructions. Please see the installation section<\/a> for more\ninformation.<\/p>\n\n Requirements:<\/strong> PHP5+, WordPress 2.9.x+<\/p>\n\n\n Create a Populate your rules using regular expression pattern matches and plugin base\nnames on each line of your rules file. For example, to exclude the Hello Dolly<\/em>\nand Akisment<\/em> plugins from being loaded on your home page, you would write \na rules file that looks like:<\/p>\n\n You will need to write a rule for each plugin that will be excluded for each\npattern that you wish to exclude that plugin from. C style comments are \nallowed in your rules file to document your rules.<\/p>\n\n\n This is pretty easy to do, just two pieces to each line - the regular expression pattern and the plugin's basename (usually the folder or file name of the plugin). See the installation section for an example of how this might look.<\/p><\/dd>\n This plugin is made to run with multisite in mind, but it has not been tested with a multisite installation yet.<\/p><\/dd>\n If you're asking this question, you may want to consider a different plugin to help manage your site's plugin use, but you can check out the following resources:<\/p>\n\n Unfortunately, I really can't do much support for this plugin, but time permitting I will continue to develop it. I am considering an admin interface for easier management, but thats down the road a bit.<\/p><\/dd>\n\n<\/dl>\n\n\n\/wp-content\/mu-plugins\/disable-plugins-rules<\/code> directory if the plugin\nhas not created one for you already. Create a rules file for each site your\nWordPress installation is running, naming the file after the host name for\nthe site followed by a .rules<\/code> extension. For example mywordpresssite.com.rules<\/code>\nwould be a rules set for mywordpresssite.com<\/code>.<\/p>\n\n# Prevent the Hello Dolly plugin from loading on the home page\n^\\\/$ hello\n# Prevent the Akisment plugin from loading on the home page\n^\\\/$ akismet\n<\/code><\/pre>\n\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n