Q. Can Plugin Organizer be used with caching plugins?
Another example would be a caching plugin that creates a static version of pieces of the page. Again lets say we have the same plugins and the same posts. When someone visits http://www.yourdomainnameyouuse.com/post-1/ static pages are created with the content from plugins A and C. This cache has a lifetime of 300 seconds for example. When someone visits http://www.yourdomainnameyouuse.com/post-2/ it has the content for plugins A and C but it is missing Plugins B and D because the cache hasn’t expired. This can cause unexpected content and errors.
There are different ways that caching plugins work and they can work together with Plugin Organizer. These are only 2 examples to give an idea. But you have to understand how they work and how you are affecting your cache by disabling plugins.
Q. Are there any known conflicts with other plugins?
A. Yes. A malicious plugin named WP Spamshield targets the settings used by Plugin Organizer to disable it. It also targets various other plugins and changes how they behave or disables them entirely. All of this is done without the users knowledge or consent. This plugin was removed from the WordPress Plugin Directory because of this malicious code but it may still exist on some users sites. It will also likely be released from a different repository in the future and start targeting plugins again. You should remove WP Spamshield not only to make sure that Plugin Organizer runs correctly but to ensure the security of your website is not compromised.
Q. When should I change the load order of my plugins?
A. The only time you should change the load order of your plugins is if there is a conflict. This plugin was originally written as a custom piece of code for a project I was working on. There were 2 plugins that conflicted with each other when loaded in the alphabetical order that the wordpress core uses by default. I changed the wordpress option in the database manually but wordpress kept putting the order back to alphabetical which caused the site to crash. So I created a plugin that would prevent WordPress from reordering the plugins and allow me to order them in any way I wanted. A few months later I released Plugin Organizer to the public. Changing the load order in the wrong way can crash your site. So be very careful about changing it and always make a database backup before you do.
Q. How do I disable plugins on the WordPress admin?
A. Follow the documentation page for disable plugins on wp-admin.
Q. I upgraded and the metabox has disappeared from the post edit screen where I can enable/disable plugins.
A. Go to the Plugin Organizer settings page and click the button under selective plugin loading to turn it on. During the upgrade process selective plugin loading got turned off.
Q. How do I enable the selective plugin loading functionality?
A. Go to the Plugin Organizer settings page and click the button under selective plugin loading to turn it on. Then visit your homepage. Finally return to the Plugin Organizer settings page and see if the button is still set to on. If it is not then you are running an old version of the MU component. Copy the PluginOrganizerMU.class.php file to the mu-plugins folder then deactivate and reactivate the plugin. Repeat these steps to ensure that the plugin is working. Remember that you will need to update the PluginOrganizerMU.class.php file whenever the plugin is updated and check your settings afterward.
Q. Does this plugin work with wordpress multi-site?
A. Yes it has been tested on several multi-site installs. Both subdomain and sub folder types.
Q. Does this plugin work with custom post types?
A. Yes it has been tested with custom post types. You can add support for your custom post types on the settings page.
Q. Does this only apply to WP MU or all types of WP installs?
“IMPORTANT: To enable selective plugin loading you must move the /wp-content/plugins/plugin-organizer/lib/PluginOrganizerMU.class.php file to /wp-content/mu-plugins or wherever your mu-plugins folder is located. If the mu-plugins directory does not exist you can create it. The plugin will attempt to create this directory and move the file itself when activated. Depending on your file permissions it may not be successful.”
A. The mu-plugins folder contains “Must Use” plugins that are loaded before regular plugins. The mu is not related to WordPress MU. This was added to regular WordPress in 3.0 I believe. I only placed this one class in the MU folder because I wanted to have my plugin run as a normal plugin so it could be disabled if needed.
Q. In what instance would this plugin be useful?
Example 1: If you have a large number of plugins and don’t want them all to load for every page you can disable the unneeded plugins for each individual page. Or you can globally disable them and enable them for each post or page you will need them on.
Example 2: If you have plugins that conflict with eachother then you can disable the plugins that are conflicting for each indivdual post or page.
Example 3: If you have plugins that conflict with eachother then you can disable the plugins globally and activate them only on posts or pages where they will be used.
Note: If you are having troubles you can view the documentation by going to http://www.jsterup.com/dev/wordpress/plugins/plugin-organizer/documentation/
Q. How do I target the homepage of my site if it isn’t a page post type?
A. Create a plugin filter with your home page url. Like http://www.jsterup.com/. Then enable or disable the plugins you want with that filter.
Q. Can I use wildcards in a plugin filter permalink?
A. Yes. You can use limited wildcards in the permalink structure. For instance you can match the url http://www.jsterup.com/some/pretty/permalink/ by entering http://www.jsterup.com/some/*/permalink/. You can also match the url by entering http://www.jsterup.com/*/pretty/permalink/ as the permalink. The only character that is recognized is the * character. It can only replace one piece of the url in between the / characters.
Q. Can I enable/disable plugins based on post type?
A. Yes. Go to the Post Type Plugins page under Plugin Organizer in the admin menu. Here you can select the post type you want to change and disable/enable plugins for that post type as long as the setting hasn’t been overridden on the individual posts.
Q. How do I disable a plugin on the front end and still have it enabled on the admin pages?
A. To load a plugin only in the admin you need to enable selective plugin loading for the admin areas and fuzzy url matching. Then globally disable the plugin you want to turn off on the front end. Next create a plugin filter with the permalink set to your admin url. Like http://www.jsterup.com/wp-admin/. Then enable the plugin for that plugin filter and select also affect children. Now the plugin should only be loaded in the admin.
Q. Can I disable plugins by role?
A. Yes. Go to the Plugin Organizer settings page and check the box next to each of the roles you want to be able to disable/enable plugins with. THen a separate container will appear on the post edit screen for you to disable/enable plugins with.
Q. I have disabled a form plugin globally and enabled it on a specific page where it is used. The plugin loads on the page but then it doesn’t work when I submit the form.
A. When the form is submitted it is not submitting to the page you are viewing. It is submitting to an ajax endpoint. Which is a different URL. You need to enable the plugin on that URL to get the form working. Here are 2 examples of how to do that.