Hello!

I'm new to Drupal and new to TAC, so please bear with me.

In setting up my site, I have created an "administrator" role which I have assigned to a single user (me) which I use for routine maintenance. This is a separate user from UID1 (superuser) created when I installed Drupal.

With TAC, I can only see the "Taxonomy Access Permissions" menu option if I am signed in as the superuser and not as my "administrator" user (UID3). The UID3 user has permissions checked for every option under all modules (everything is checked). However, there doesn't appear to be a TAC module that can have permissions applied.

Is there something special that has to be done to provide this non-superuser "administrator" role with the ability to administer TAC permissions or is this something that can only be done by the superuser?

I am running this under 6.0, so TAC may not be 100% compatible with it yet (I am running the HEAD version from 2008-Feb-23).

Thanks,
phlepper

Comments

Anonymous’s picture

Hi,

I want this funcionality too, then I searched this forum and found this link: http://drupal.org/node/89102, but its resolve problem for v 5.x. I don't known much about PHP or writing modules for drupal, but found temporary solution for me:

Edit taxonomy_access.module, search for function taxonomy_access_menu().

Before this block add this:

function taxonomy_access_perm() {
    return array("administer taxonomy access-rights");
}

Then in function taxonomy_access_menu() change 3 exactly same lines
'access arguments' => array('administer access control'),
to
'access arguments' => array('administer taxonomy access-rights'),

Then, disable/enable taxonomy access module (maybe try to run update.php). Then, go to <your_site>/admin/user/permissions#module-taxonomy_access under true admin and enable it for your administrator role. After it, users with administrator role have Taxonomy access permissions item in menu, like install admin user. That's all.

It's probably ugly hack with some errors, but it works good for me, until somebody write it better. And sorry for my english ;-)

dracik

PS: Thanks for this very useful module!

ifoundthetao’s picture

Hey man, you guys are awesome. I just ran into this error today too and it was totally trying to throw salt in my game. Anyway, I'm going to try this and see if I can confirm it works.

Thanks,

Tim

EDIT:

It did not work! :( This stinks. I'll be back in a few hours.

EDIT 2:

I got it to work. I actually had to type it out by hand, and when I did that I changed it..
Here is how it looks now

function taxonomy_access_perm(){
    return array(
    'administer taxonomy access-rights',);
    }
/**
 * Implementation of hook_menu
 */
function taxonomy_access_menu() {
  $items = array();

  $items['admin/user/taxonomy_access'] = array(
      'title' => t('Taxonomy access permissions'),
      'description' => t('Taxonomy-based access control for content'),
      'page callback' => 'taxonomy_access_admin',
      'access arguments' => array('administer taxonomy access-rights'),
    );
  $items['admin/user/taxonomy_access/delete'] = array(
      'type' => MENU_CALLBACK,
      'page callback' => 'drupal_get_form',
      'page arguments' => array('taxonomy_access_admin_delete_role'),
      'access arguments' => array('administer taxonomy access-rights'),
    );
  $items['admin/user/taxonomy_access/edit'] = array(
      'type' => MENU_CALLBACK,
      'page callback' => 'drupal_get_form',
      'page arguments' => array('taxonomy_access_admin_form'),
      'access arguments' => array('administer taxonomy access-rights'),
    );

  return $items;
}
cpugeniusmv’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

summit’s picture

Hi,
Is this also fixed for Drupal 5 (2*.dev version)?

greetings,
Martijn

cpugeniusmv’s picture

I only changed the permission used to account for the 5 -> 6 permission rename. So 5 wasn't affected by this.

In other words, #89102: Add "Administer Taxonomy Access Control" option in Access Control ("permissions") is still active.