WordPress.org

Ready to get started?Download WordPress

Forums

Sitewide Roles and Capabilities (4 posts)

  1. johlie
    Member
    Posted 3 years ago #

    Hi all,

    I have a following scenario:

    For our Site-Network we need to have two roles of network-admins: a normal superadmin and supportadmin, who has still have sitewide capabilities, but just a little less, than a superadmin. For example he shouldn't be able to delete, deactivate or archive sites...

    Some of the needed functionalty has allready been added in 3.0 Beta 1 through the capabilities like: manage_sites, manage_network_users and manage_network_options. This is pretty awesome, the only problem is, that the manage_sites capability is just to powerful!

    It would be very helpful to either divide the capability in to smaller once, like delete_site, archive_site, mark_site_as_spam. Or just add extra hooks in the wp-admin/ms-edit.php everytime after the current_user_can('manage_sites') check, so that the plugin-developers could implement their owen routine to check for the custom capabilities. For example:

    if ( ! current_user_can('delete_sites')){
    wp_die(__('You are not allowed to delete Sites!!!'));}

    For the function above we would need a hook around line 309, something like: do_action( 'before_delete_site');

    I think this would be very helpful to a lot of people and allow much greater control over sitewide user roles.

    Thanks a lot and let me now what you think!

  2. File a trac ticket for it to be considered for 3.1.

    before this code, the only option was is_site-admin, so it's better than it was. ;)

  3. johlie
    Member
    Posted 3 years ago #

    Hi Andrea,

    oh yes, it's definitely much better, than in the previous version!

    Do you mean a ticket on the official WordPress Trac?! I wasn't sure whether this is the right thing to do, since it's more a request, than a bug...

    Do you know what's the right way to file this ticket?

  4. Login to trac with your credentials from here. State your case with as much details as possible, be sure to label it as an enhancement and with a future version.

Topic Closed

This topic has been closed to new replies.

About this Topic