Granular role-based permissions

Well, as soon as you start with this, it generates a boatload of new feature requests… From less to more granular:
- 'add new items to hierarchical select' permission
- configure this per implementation
- configure this per hierarchical select
- configure this per level, per hierarchical-select

I'm inclined to mark this as postponed. Wil leave it open for now.

Postponed for sure. Sorry.

It might, but I doubt it.

subscribing

Through this single issue I'll implement *every* permission one could ever want. When I have the time. Which won't be until a *long* time. At least it's organized already :)

This makes the following issue obsolete: #261423: Role-based item creation permissions.

You can look forward to it, but don't expect it any time soon ;) Many months, possibly more than a year of waiting.

Hi Wim,

I understand that the role-based permissions system is complex and not available for now on in HS.
The point is that only admin is now allowed to create new terms (at least in my config it's working in that way - I have 3 levels hierarchy and only admin can add new terms, although all the users have the "administer taxonomy" privileges set).
Instead of controlling creating permissions per role, it would be good to give creating terms permission to all the users regardless the role they have. Otherwise if admin is the only person able to create new terms, it makes the usage of this feature very limited.

Let me reply to my own post.

I have just discovered the root of the problem. In fact IE is guilty. Creating new terms works under Firefox and it doesn't under IE6 and IE8. It is not related to the role permissions; I was testing the module with admin account under firefox and regular user under IE - hence the wrong conclusions. Sorry.
On the top of that it looks like the problem occurs only with specific themes...

Bah! Please open a new issue for that!

Any progress with role-based permissions? I, too, would love to be able to grant one role the ability to add new terms via HS, but keep other authenticated users from doing this.

Thanks!

Tagging for HS4. Included in the HS4 roadmap: http://drupal.org/node/1052670.

This will happen in the 7.x branch.

0.0
i am unfamiliar with drupal big documentation and i just discover your roadmap and it is impressive!!
i subscribe to the possibility of add permissions base on roles since it would be very useful in a magazine where the editor can create a new number and the writer can assign an article to the section on that number adding a level for the order of that article inside the section.

thanks a lot for your module :)

For anyone seeking a bare-bones implementation of role-permissions in the 6.x version of HS, here's what worked for me.

I created a new role "skiphierarchicalselect'. Users of this role won't be shown the HS taxo-fields on node creation.

I edited:

modules/hs_taxonomy.module
# function hs_taxonomy_form_alter(&$form, $form_state, $form_id)

and applied a code diff resembling:

@@ -336,6 +340,16 @@
           }
         }
 
+	global $user;
+	if ($user->roles['6']) { // skiphierarchicalselect
+		$form_function='taxonomy_form';
+	}
+
+

The above resets the taxonomy form function to 'taxonomy_form' (the Drupal method) for users that have a specific role ID. This bypasses the HS method.

A few months ago I built a custom module for my employer who is always keen to provide patches to the community. The module has a settings page for allowing certain roles and certain content types to use Hierarchical Select. Roles that are ticked in the settings page will use the default drupal menu which you see when creating new nodes.
Is this what you are after? I regret it was not created as a patch rather than a separate module. Please let me know, if a separate module is not very useful, I'm sure my employer will let me work on it again to provide a patch after a week or two. Let me know.

Hi,

I have added my first module: hierarchical select access. It has a settings page for preventing certain roles from accessing the Hierarchical Select menu when creating node types.

If you intend to use the module please make sure you have a backup copy of your site before trying it.

I hope it helps solve what's being discussed in this issue.

Thanks,

Yousif

Hi,

I have added my first module: hierarchical select access. It has a settings page for preventing certain roles from accessing the Hierarchical Select menu when creating node types.

If you intend to use the module please make sure you have a backup copy of your site before trying it.

I hope it helps solve what's being discussed in this issue.

Thanks,

Yousif

Yousif, thanks! Hope anyone finds it useful!

Stefan, thanks for reviewing the hs_access module and assisting in the project application.

Next on my list is the taxonomy terms bit.

This is now covered by contrib