WordPress MU and registration warning

I'm setting up WPMU for a client's intranet. One of the key features they needed was the ability to create forms, for example, for running small surveys, getting feedback, etc.

Gravity Forms is fantastic for this and the training overhead is low, which really helps.

But we've hit something of a problem with Gravity Forms on MU.

1) On each MU blog or site you're asked for the registration key. It should be possible to enter this once, so long as it's a developer key, I guess.
2) If you click the uninstall Gravity Forms button on one blog, you'll deactivate the blog everywhere. That's dangerous and could cause issues, although it would seem that it doesn't actually delete forms and settings from other blogs.
3) Even bigger issue - only a site admin can access forms on a MU blog. It would be rather more useful if admins (and maybe editors) could access forms on a MU blog - this is when the plugin has been activated as a site-wide plugin.

Here's my installation settings for the development environment:

PHP Version 5.2.6
MySQL Version 5.0.67
WordPress Version 2.9-rc-1
Gravity Forms Version 1.3.8

That's WPMU 2.9-rc-1 by the way!

And just to add, I still think it's a very good plugin :-)

Thanks,

David.

OK, so it looks like the simple answer to the key setting is to create a little MU Plugin that copies the rg_gforms_key (and maybe other values) across the different wp_%_options tables.

The others...

Are you aware that you can have plugins selectable by blog admin, as well as sitewide? This is an important difference - if the plugin has been set to be selectable per blog then you don't want someone on one blog affecting another. Having said that, I haven't done a full and careful test on all the possible options so can't give a definitive analysis.

I was planning on installing Justin's Roles plugin on this site, but that was further down the list. I think it's just moved up the list! I do think that by default you should allow a blog admin forms access, but as MU hasn't been a priority for you I can also understand why you haven't done so.

Thanks for the prompt and thorough support, by the way. I'll come back with any feedback I find from the above, and will also make the mu-plugin code available to all.