Nodeaccess limited to a single role

You've added a check for operation view and status. However this check can be removed and the return can be placed in the switch case
You only want to return something here if it is relevant to that role.

function nodeaccess_node_access($node, $op, $account) {
  if (!isset($account->uid)) {
    global $user;
    $account = $user;
  }

  // Only do something if the user has a role that nodeaccess is doing something for.
  $nodeaccess_enabled_roles = array_keys(array_filter(variable_get('nodeaccess-roles', array())));
  if (empty(array_intersect($nodeaccess_enabled_roles, array_keys($account->roles)))) {
    return NODE_ACCESS_IGNORE;
  }
  switch ($op) {
    case 'update':
    case 'delete':
      // We check if the role has particular access to this node.
      $grants = nodeaccess_get_grants($node);
      foreach ($account->roles as $rid => $role) {
        if (
          (
            isset($grants['rid'][$rid]['grant_update']) &&
            $grants['rid'][$rid]['grant_update'] &&
            $op == 'update'
          ) ||
          (
            isset($grants['rid'][$rid]['grant_delete']) &&
            $grants['rid'][$rid]['grant_delete'] &&
            $op == 'delete'
          )
        ) {
          return NODE_ACCESS_ALLOW;
        }
      }
      break;

    case 'view':
      // If the node is not published. We check other permissions.
      if (!$node->status) {
        // If the current user is the author and not anonymous.
        if ($node->uid == $account->uid && $account->uid > 0) {
          // We check to see if they have access to view own unpublished.
          if (
            user_access('view own unpublished content', $account) ||
            user_access('bypass node access', $account)
          ) {
            return NODE_ACCESS_ALLOW;
          }
        }
        elseif (user_access('bypass node access', $account)) {
          return NODE_ACCESS_ALLOW;
        }

        return NODE_ACCESS_IGNORE;
      }
      else {
        return user_access('access content', $account) ? NODE_ACCESS_ALLOW : NODE_ACCESS_IGNORE;
      }
      break;

  }
  return NODE_ACCESS_IGNORE;
}

Note to revisit, possibly for #3033025: Nodeaccess 7.x-1.7 release.

I've rerolled the patch from #5 against the latest dev.

Cool ideas, @paulvandenburg, and thanks for the reroll, @TVoesenek!

Do you two feel like you still want this functionality -- and do you want it for D7, or not really anymore -- or definitely still want it? Just checking! (@TVoesenek are you using the patch on a site, or providing rerolling services? Again, just checking :) )

Initial thoughts, skimming through the changelog comment (awesome -- thanks for writing!), haven't skimmed through code or tested the patch yet:

• (Preface: yeah should probably break this up, but I totally get where you were coming from -- starting by just getting it all out there! And, cool of you to share back what you did for your use case.)
• Eek that "disabling" function *is* odd! Also, the "disable" function in .install -- I'm not sure, but I feel like maybe this was a "norm" or even a requirement of D6/D7 modules "way back when"...?
• I wonder how the "Preserve hidden grants" and "Give node grants priority" settings fit in with what you're going for.
• Your use case -- you're looking to prevent managing users from applying nodeaccess settings to users who *don't* have the specific role, is that the impetus for this functionality? If not, could you clarify the use case/needs?

.............
(Meanwhile, just fyi: I'm going to remove from the "also considering" list for 7.x-1.8, just because it's so much new functionality to consider -- I think if we roll any of it into the module, it'll be in pieces.)

@paulvandenburg Gotcha, thank you so much for explaining!

I'm doing to say "needs work" b/c if it's going to be committed, it'll be in pieces -- not to oblige y'all to actually do that, just to reflect the status of the issue.

Fixed a bug in this patch (#3195324: Column 'uid' in where clause is ambiguous).

Column 'uid' in where clause is ambiguous because a condition on uid and not on u.uid is added.

Drupal 7 security support has ended as of 5 January 2025.

We are doing some housekeeping on the nodeaccess issue queue and moving all Drupal 7 issues to "postponed (maintainer needs more info)". See https://www.drupal.org/project/nodeaccess/issues/3516593.

If this issue persists on the latest dev branch of nodeaccess (2.0.x-dev) then please feel free to comment and we will change the version against this issue. If we do not hear any feedback within 2 weeks (9th October 2025) we will go ahead and close this issue as outdated.

Thank you.

As per the above, as there has been no response we will now close this issue as outdated.

If this issue persists on the latest dev branch of nodeaccess (2.0.x-dev) then please feel free to update the version on this issue and reopen it.

Thank you.