The MU forums have moved to WordPress.org

What makes .org plugins break? (2 posts)

  1. realistdreamer
    Member
    Posted 14 years ago #

    I'm impatient and don't want to wait for "the merge" so I will probably start on MU so I can get Buddypress functionality (I'm greedy) even though I want only one blog (with multiple categories).

    I know to expect some plugins not to work, but I'm trying to get an idea about what about MU would cause a plugin to not function correctly in a single blog environment? I searched and couldn't find a good answer.

  2. andrea_r
    Moderator
    Posted 14 years ago #

    Because it depends on the plugin and how it was coded. :)

    Some of it is functionality: some people expect a single WP plugin to magically gather sitewide data from across all member blogs when they really are just blog specific.

    Some is technical - plugin in the mu-plugin folder are executed so anything requiring activation will fail.

    And some won't save options - not a clear fix for this. We've just wound up writing in a new way to save the info.

    Or, it appears to work, but fails to notice the blogs are separate (a sitemaps plugin making one sitemap for the whole site, for instance)

    And finally, some are just harder to nail down. the biggest issues I've run into is the not saving options. If the plugin doesn't break outright, and any options just save, then it usually works on MU.

    But I'm finding more and more plugins that DO work than ones that don't. Half the time it's more about perception.

About this Topic

  • Started 14 years ago by realistdreamer
  • Latest reply from andrea_r