Comments on: YD Network-wide Options

By: Griffith

Griffith — Thu, 02 Feb 2012 17:22:50 +0000

i think that is is easier to select all the options then go back through and deselect the options you wouldn’t want to transfer. Clicking about 600 times gets a little redundant… In regards this would only apply to the “Options to propagate” meta box.
Regardless i do appreciate all the work on this plugin! made my life easier.

By: Y.Dubois

Y.Dubois — Thu, 02 Feb 2012 17:18:49 +0000

@Griffith: there is no select all; but I don’t think you would really want to do that. Options to replicate have to be chosen carefully.

By: Griffith

Griffith — Thu, 02 Feb 2012 15:32:54 +0000

Maybe i am missing this setting somewhere, but is there a check/uncheck all button?

By: Zach

Zach — Wed, 01 Feb 2012 16:26:58 +0000

Appreciate the reply – yup, I can just make the manually change for the deprecated function (was interfering with some access rules I had setup for ‘manage_options’ – no biggy). Concerning your second comment – yeah, can completely understand that – and just figured out that Members is really just a nice GUI interface for what you can already do with code – so I just created my own plugin instead as a global MU plugin and modified from there Thanks!

By: Y.Dubois

Y.Dubois — Wed, 01 Feb 2012 15:16:20 +0000

@Zach: some plugins do not use regular WP option keys to store their settings, so depending on what mechanism that plugin uses, just propagating option changes might not be sufficient to spread the settings over the whole site network. Check out that the plugin does not use it’s own data structures. My plugin can also duplicate data structures (ie database tables) and contents. However, if the plugin you wish to make network-wide stores its settings elsewhere (in a file, or in user meta or post meta keys for example…), my plugin won’t be able to deal with it. You will then need some other approach to the problem.

By: Y.Dubois

Y.Dubois — Wed, 01 Feb 2012 15:12:11 +0000

@Zach: Yes, the use of deprecated functions is not exactly a bug. It does not prevent the plugin from working fine with later releases of WordPress, nor does it introduce vulnerabilities. This will be upgraded in a future release. Right now, the plugin works just fine, so there is no hurry.

By: Zach

Zach — Tue, 31 Jan 2012 16:27:19 +0000

Hi,
Also think I found a bug (or at least, a deprecated function that should be replaced). On line 145 of yd-wpmu-sitewide-options.php, you are using a capability number, “8″, instead of an actual capability, like “manage_options”. Any references like that should be changed. Thanks.