Plugin activation options

Just another question I would like to get clarity on:

So with mu-plugins folder plugins are automatically activated for all sites and plugins folder it is on a blog-by-blog basis.

However, when you upload a plugin to plugins directory you still get to either activate it or activate it sitewide.

Does this mean if you just activate it, it is available only for main site only and if you activate it sitewide it is available for all sites?

The thing that is getting me confused is that BuddyPress is activated sitewide, which makes me doubt what I concluded to be the differenc

  • AquaPebble

    Some plugins don't say how it should be activated and have left me unsure which is the correct option. I need some point of reference to make a judgement, hence my question. They usually say load into plugins directory, but not how to activate them.

    Why would there be an option for plugins, in the plugins directory, to be simply activated or network activated ?

    I am even more confused then by the point of the mu-plugins directory if the same can be achieved by putting plugins in the plugins directory.

    Sorry about the ongoing questions, but this is not clear in my mind.

  • drmike

    Honest answer: It's a judgement call. There's really nothing to point at and say "This works better in the plugins subdirectory" Usually though plugins that create their own individual database tables, like wp-polls, go in the plugins directory. Something like a shortcode filter plugin for videos can go in mu-plugins because it doesn;t modify anything.

    But then of course we've modified wp-polls to create their databases whenever a new blog is created. For us, it goes into mu-plugins. For us, if it creates it's own databases tables for individual blogs, it goes in plugins. That's not ironclad though.

    This is one of the reasons why you should be running a testbed if you're not.