WordPress.org

Support

Support » Multisite » bad behavior plugin on multisite installation

bad behavior plugin on multisite installation

  • I’ve searched through the forums and on the bad behavior site and haven’t seen any clear indication of whether a) it works with v3 multisite and b) where to install the plugin on a multisite installation.

    I’m hoping that someone here can provide some insight.

    Thanks in advance…

    mw

Viewing 15 replies - 1 through 15 (of 42 total)
  • It should work. Have you tried it yet?

    Just wondering if the plugin goes in the mu-plugins folder or the plugins folder? I want it to be installed on every instance….

    Seems to work. I installed it in the plugins folder and clicked the network activation link. The plugin is active in the sites and appears to be working….

    I suspect it wouldn’t work in mu-plugins, because the plugin needs to create at least one MySQL table during activation.

    In plugins with network activation is the way to go.

    Unfortunately, it has to go in the plugins folder and be activated network wide. It’s not really optimized for multiuser because it creates an SQL table for every blog and stores it’s options per blog – you would have go into each individual blog’s dashboard to see whats been blocked or change the options making it impossible to use the blacklist api feature.

    That’s why I created a modified version for WPMU – it’s working great for my blog network. You can put this one in mu-plugins and manage options/logs network wide instead of per blog. Thought I might as well share it.
    http://rapidshare.com/files/413778697/bad-behavior.zip

    @mrbrian:

    giving your mod a testrun right now, thanks for sharing.
    Would you elaborate what exactly you changed in its behaviour?

    May I also suggest you submit the changes to the author so maybe he can work on a multisite compatible version too?

    oh and how would I verify if BB is active on all my blogs?

    MrBrian – Have you contacted the dev about that? He might be willing to incorporate it into the main BB plugin 🙂

    I use it per-site right now, which is annoying, but keeps idiots out.

    oh and I found out that a normal admin, not only site-admins have access to http://yourblog.yourdomain.ro/wp-admin/tools.php?page=bb2_manage and can see the total number of blocks plus details about who and why was blocked.

    I really think this menu should be hidden from users and made inaccessible via a is_site_admin check or similar OR if it can be done only show blocks that occurred for this particular blog the user is logged in and has admin rights for!

    Just realized that the BB settings are also accessible to any admin. they can even see my http:BL Access Key !?

    MrBrian

    @mrbrian

    @ovidiu: The only things I changed in it’s behavior was moving the menus to Site Admin (so they are only accessible by siteadmins) and changed the database table and plugin options to store site wide instead of per blog. I also had to move around some files and code so that it would work in the mu-plugins folder. In it’s current state, bad bahaviour isn’t feasible for multisite for all the reasons mentioned already, so hopefully the author will make the needed updates for it. Use my modified version for the time being unless you don’t mind your bloggers managing it’s options, not knowing sitewide stats, and not being able to use http:BL without adding the key to every blog in your network – oh and “bad bahaviour statistics in the blog footer” is enabled by default so it’s displayed in the footer of all the blogs in your multisite. The main reason I made the mod was because it creates a database table for every blog, and for a blog network like mine with more than 10,000 blogs.. that’s a lot of unneeded database tables.

    You’ll know BB is active on all your blogs by looking at the BB logs, but as long as the menus are showing up under Site Admin you’ll know it’s working. Since it’s in the mu-plugins folder, there’s no need to “activate network wide” and it won’t show up in the plugins menu.

    oh and I found out that a normal admin, not only site-admins have access to http://yourblog.yourdomain.ro/wp-admin/tools.php?page=bb2_manage and can see the total number of blocks plus details about who and why was blocked.

    I really think this menu should be hidden from users and made inaccessible via a is_site_admin check or similar OR if it can be done only show blocks that occurred for this particular blog the user is logged in and has admin rights for!

    Just realized that the BB settings are also accessible to any admin. they can even see my http:BL Access Key !?

    THAT was still valid, I just checked again. Any administrator, not site-admin can see and change the options.
    Just re-uploaded your plugin again. I am talking about your plugin not the original one.

    Which wp version are you using? I am using wp 3.0.1 with vhost based multi-side…

    MrBrian

    @mrbrian

    Oh I see what I did there.. still had the code for the old menus in there for non-siteadmins. Fixed in this version.

    http://rapidshare.com/files/417767287/bad-behavior-wpmu.zip

    thanks.
    now we are talking, works great and no options accessible for normal admins 🙂

    btw. why does the number of records within the log file differ on the bb options page from the number shown on the bb configuration page?

    (I am talking about the two menus added by the plugin, they show different counts)

    MrBrian

    @mrbrian

    The configuration page has the count for ‘blocked’ requests while the count on the log page is for ‘all requests’ which include permitted ones, so its normal for the numbers to be different.

    I must say spam has really gone down on my blog network… sure takes the load off of akismet for comment spam – blocked over 50,000 baddies in the past 7 days.

    thanks for the clarification and the mod 🙂 works well on my install too, except for the issues with the menu appearing for normal admins which is fixed now.

    cheers
    ovidiu

    let me throw another one at you.
    I finally managed to see a bb blockpage.
    it contains (in my case) this detail:

    <p>If you are unable to fix the problem yourself, please contact <a href="mailto:ovizii+nospam@nospam.zice.ro">ovizii at zice.ro</a> and be sure to provide the technical support key shown above.</p>

    can I customize that somewhere? I am sure most people won’t be able to realize that the link text is the correct email address and not the mail.to link, so I’d rather replace +nospam@nospam with -delete-this-@

Viewing 15 replies - 1 through 15 (of 42 total)
  • The topic ‘bad behavior plugin on multisite installation’ is closed to new replies.