Are you asking us where that information is stored?
Thread Starter
oiler
(@oiler)
Yes I was. And I later found it.
Much to my disappointment, there doesn’t seem to be anything capabilities assigned to the super admin. It’s just a boolean yes or no. Why not make it a part of the regular Roles.
Because it has to exist network wide, and regular roles are per-site.
Thread Starter
oiler
(@oiler)
That’s fine, but why not offer capabilities for the super admin inside at least in sitemeta?
It’s not even something that’s pluggable. The ‘is_super_admin’ function is in includes/capabilities so it’s purely a on/off switch.
This plugin comes close, http://wordpress.org/extend/plugins/extended-super-admins/ , but is buggy and just can’t pull off what we need it to.
Anyhow, thanks for responding.
You’re confusing NETWORK and SITE again. Or still. Hard to say.
Roles/Capabilities, like Admin, Contributor, Editor, etc, are all per site. I can be an Admin on one site, an editor on another, and so on and so forth.
However the SuperAdmin (aka Network Admin) has the power to edit themes, plugins and do whatever they want on all site.
So all it needs to be is an on-off to say “I have the power!” or not. There’s no need to offer capabilities, and it prevents the unwary from screwing things up.
This plugin comes close, http://wordpress.org/extend/plugins/extended-super-admins/ , but is buggy and just can’t pull off what we need it to.
How about you try telling us what you NEED it to do 🙂
Thread Starter
oiler
(@oiler)
Right… that may help.
I understand the Network vs Site clarification… but when you’re in a Network, certain admin capabilities – like install plugins or themes – get sucked up out of the Site admin and into the Network admin.
Specifically, we’re looking for something that can work similar to how the Founder works in phpbb. A super admin over all super admins.
The Founder, then in this scenario, is able to do everything the super admin can now do. And the revised super admins have the ability to manage the Network blogs and users (add, delete, assign, etc) but not install-edit-update plugins or themes or update core.
but when you’re in a Network, certain admin capabilities – like install plugins or themes – get sucked up out of the Site admin and into the Network admin.
Yes, because if you let per-site admins install themes and plugins, they can destroy your whole network. It’s a huge risk, especially on an open network.
users (add, delete, assign, etc)
Actually you can turn that on so every admin can do that on their own site.
manage the Network blogs
You mean add/remove blogs?
Thread Starter
oiler
(@oiler)
Yes, because if you let per-site admins install themes and plugins, they can destroy your whole network. It’s a huge risk, especially on an open network.
Agree 100% and that’s actually why we’re investigating all of this.
We don’t want site admins to be able to install themes and plugins but they DO still need to be able to manage/add blogs and users across the whole Network, not just for a single blog.
The scenario is…. a newspaper has a set of blogs that run on a Network.
The newspaper’s dev team manages the blogs. They are the Founder and do all the heavy lifting. But the newspaper’s editors and managers handle all the day to day add blog, edit blog, assign users, etc. We, the developers want to give the editors and managers that ability but don’t want them also installing plugins and themes.
So these managers and editors need to work across the Network as site admins, but can’t be allowed to do things that the developers can do.
We don’t want site admins to be able to install themes and plugins but they DO still need to be able to manage/add blogs and users across the whole Network, not just for a single blog.
That’s sort of a case where you’re kinda using MultiSite for the wrong thing.
MultiSite is for separate, not connected, sites. Which is why it’s made the way it is. And why you’re going to have a headache.
Now. You COULD set up your site so that all new blogs are moderated, and you have to okay the blog before it goes live. Then whomever created the blog is the ‘admin’ and can add users to that site as they want.
* http://wordpress.org/extend/plugins/moderate-new-blogs/
Or go sideways. Install a membership plugin, network wide, and set up a special domain group for people who should be admins of all the blogs. Then use a plugin to force those settings down for all blogs:
* http://wordpress.org/extend/plugins/yd-wpmu-sitewide-options/
Thread Starter
oiler
(@oiler)
That’s sort of a case where you’re kinda using MultiSite for the wrong thing.
MultiSite is for separate, not connected, sites. Which is why it’s made the way it is. And why you’re going to have a headache.
Trust me when i say that these people treat their blogs as separate, not connected sites!
Either way, how we set it up doesn’t expose the fact that the is_site_admin boolean doesn’t offer the granular capability options that it probably should.
This plugin comes close, http://wordpress.org/extend/plugins/extended-super-admins/ , but is buggy and just can’t pull off what we need it to.
Then work with the author (he’s a nice guy I promise) to help get it fixed and do what you want.
Thread Starter
oiler
(@oiler)
Yeah, I did leave a comment on his plugin page but it wasn’t answered. So after waiting an appropriate amount of non-stalking time, I wrote him an email yesterday.
Looks like I got what I needed and am hacking his plugin to be applicable to our needs.
