I understand (I think) the two options that Moderate Bypass offers, but I can't seem to find where to set them. I've looked in the following places:

  • User Management > Permissions
  • Site Configuration > Modr8
  • Content Management > Forums > Settings
  • Content Management > Forums > Individual Forum settings
  • Content Management > Content Types > Forum Topics

I can't seem to find any relevant settings in any of these places. What am I missing?

Comments

johngriffin’s picture

The settings page should appear under Site Configuration > Modr8 > Modr8 Bypass.

The path is: admin/settings/modr8/bypass

steven9’s picture

johngriffin, I found the settings for Modr8 Bypass, but I can not find where to set the roles that will bypass the modr8. Where do you set that? No new permissions options appeared in the list of permissions. What am I missing?

johngriffin’s picture

You will need to enable Modr8 on at least one content type first before the permissions will show up.

steven9’s picture

And where do I do that? I went to one content type and in the "Workflow settings" I checked "In moderation queue". Is there anything else I have to do?
From the module documentation "Moderate bypass works by exposing a permission for each moderated content type" NO permissions are exposed.

steven9’s picture

I fixed it

    /**
     * Implementation of hook_perm().
     */
     function modr8_bypass_perm() {
     $perms = array();
     foreach (node_get_types() as $type) {
-     if ($type->module == 'node') {
      $name = check_plain($type->type);
      $node_options = variable_get('node_options_'. $name, array('status', 'promote'));
      if (in_array('moderate', $node_options)) {
        $perms[] = 'bypass '. $name .' moderation';
-      }
    }
  }
  return $perms;
}

I took out the 2 lines with a minus above and now the permissions are exposed. Cheers!

johngriffin’s picture

Hi Steven9,

Thanks a lot for that. I've applied that patch and and released a new version - 1.2.

steven9’s picture

john, I just downloaded the 1.2 version but in the code I see that the patch was not applied. And I manually went again with my patch. Just thought you might want to know.

johngriffin’s picture

What a butterfingers.

You're absolutely right, the latest release - 1.3 - should now contain the fix.

Sorry about that.

John

johngriffin’s picture

Status: Active » Closed (fixed)

Closing as this issue has been confirmed fixed in http://drupal.org/node/693914