Project

General

Profile

Feature #18

Manage Bad Behavior from Wordpress "Network Settings" page

Added by Chris Fryer almost 6 years ago. Updated almost 4 years ago.

Status:
Accepted
Priority:
Normal
Target version:
Start date:
04/11/2013
Due date:
% Done:

0%


Description

It would be really useful to be able to define some default settings that will be applied to all blogs in a Wordpress Network. I'm thinking especially of the reverse proxy address, the Http:BL key, whether to allow posting from offsite, etc. It's a bit of a pain to have to do this for every new blog that gets created.

Thanks for creating such a great product.

History

#1 Updated by Paul Herring almost 6 years ago

Chris Fryer wrote:

It would be really useful to be able to define some default settings that will be applied to all blogs in a Wordpress Network. I'm thinking especially of the reverse proxy address, the Http:BL key, whether to allow posting from offsite, etc. It's a bit of a pain to have to do this for every new blog that gets created.

Thanks for creating such a great product.

Question:

Technically, shouldn't each blog owner have their own Http:BL key, rather than the network using a shared one? (I'm presuming that you're maintaining the network, and have other people running the blogs)

How would the owner of the key (i.e. you) stop admins for a particular blog (i.e. your users) copying then (ab)using the key elsewhere thus breaking all the blogs when the key gets rescinded?

Besides - now presuming this doesn't matter - doesn't Wordpress have the concept of a 'skeleton' where you can place a default BB ini file/config in which has the key present?

#2 Updated by Chris Fryer almost 6 years ago

Paul Herring wrote:

Question:

Technically, shouldn't each blog owner have their own Http:BL key, rather than the network using a shared one?

Possibly, but our bloggers are not interested in such matters. They want to write, and they want me to take care of the service. Keeping spammers from commenting on their posts is part of that service.

How would the owner of the key (i.e. you) stop admins for a particular blog (i.e. your users) copying then (ab)using the key elsewhere thus breaking all the blogs when the key gets rescinded?

By not displaying that option to the blog admin, perhaps? I use another plug-in (a modified version of wpCAS-w-ldap) that has this model. If a setting is found in an ini file, the corresponding element is not even displayed on the plugin configuration form.

Besides - now presuming this doesn't matter - doesn't Wordpress have the concept of a 'skeleton' where you can place a default BB ini file/config in which has the key present?

I don't know anything about this feature. The Mediawiki integration has support for a "settings.ini", but I don't see anywhere in the Wordpress integration that reads that file. I suppose I could hack line 122 of bad-behaviour-wordpress.php to load in my own defaults array, but that wouldn't survive BB updates.

#3 Updated by Bill Murray almost 6 years ago

If each site should have its own options, there is a simple way to address that in WP - don't network activate the plugin and let each site activate it as needed.

I think Chris's suggestion makes great sense when the plugin is network activated. To add to this, when the plugin is network activated, all logs should not be in the tables for each site. Instead, they should be in the tables for the main site.

The point of network activation is to allow centralized management for those that want it. Individual site activation is appropriate for those that want control of settings on a site by site basis.

On a network with a lot of sites or where site admins have handed over network admin to the network, it's not efficient to give site admins control over settings that they don't want or might screw up.

#4 Updated by Michael Hampton almost 6 years ago

  • Target version set to 3.0

It's a commonly requested feature that, due to its complexity, I've put off for 3.0.

A multisite WordPress can be run in one of two ways:

  1. A single administrator runs all sites on the network.
  2. Each site is administered independently of the others.

While the existing code covers the second case well enough, the first case is what we need to handle.

#5 Updated by Bill Murray almost 6 years ago

Thanks as always for the update, Michael. If some funding would move that up on the priority list, let me know what $ would produce what time savings.

We run BB on the main site in our network and have let site admins activate it (your #2), but it would really shine with #1.

#6 Updated by Michael Hampton almost 6 years ago

  • Assignee set to Michael Hampton

Hi Bill,

Thanks for the offer of a donation. As you might imagine, I hesitate to recommend any specific donation amounts, though I certainly won't turn down one! Feel free to contribute any amount you think is appropriate.

#7 Updated by Michael Hampton almost 6 years ago

  • Status changed from New to In Progress

#8 Updated by Michael Hampton about 4 years ago

  • Status changed from In Progress to Accepted

#9 Updated by Chris Fryer almost 4 years ago

It occurs to me that if the Wordpress version of bad behavior parsed settings.ini, you would get network-level settings for free.

Also available in: Atom PDF