For the most part, users are either "trusted" or they are not. In actual use, "blog entry" is the one content type I would especially like to be able to bypass moderation. In practice, I would like the option of bypassing moderation of all content types by role.

Comments

johngriffin’s picture

I'm not sure if I misunderstand what you're asking for but are you aware that the module provides a permission to bypass each content type individually? This enables you to "bypass moderation of all content types by role".

johngriffin’s picture

Status: Active » Closed (fixed)
tarvid’s picture

Permissions only has entries for book, event, page, petition. Missing are announcements, blog, forum topic, page, etc. Anyway to reset the permissions menu?

johngriffin’s picture

Status: Closed (fixed) » Active

Hi Jim,

Please try upgrading to the latest version - 1.2. There was a bug which was causing permissions to not show up for some content types.

Thanks,
John

hargobind’s picture

Version: 6.x-1.1 » 6.x-1.2

I'm also seeing issues where permissions are showing up for built-in or custom content types (i.e. node types created by the "node" module), but any content types that have been added via other modules (such as the audio module) don't appear on the permissions page. On looking at the code that renders permissions visible, there appears to be a check for only content types created by the "node" module.

I commented out that check in the code and it appears to be working the way it's expected now:

function modr8_bypass_perm() {
  $perms = array();
  foreach (node_get_types() as $type) {
//  if ($type->module == 'node') { // ** Commented out
      $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';
      }
//  } // ** Commented out
  }
  return $perms;
}

Unless you really think that check is necessary, I suggest you remove it and release the next version ASAP.

Thanks for the great module!

johngriffin’s picture

Hi Linxor,

You're absolutely right, that was the change I meant to make in ver. 1.2, however it seems I screwed up the tagging somehow!

There is now a new release - 1.3 - which should solve this issue with exactly the fix you have suggested.

Thanks,
John

hargobind’s picture

Status: Active » Fixed

Sweet. Thank you!

johngriffin’s picture

Status: Fixed » Closed (fixed)