Hi All,

I tried to resolve the issue explained in http://drupal.org/node/533118 using Organic Groups in this way:

  • There are 2 roles: Moderators and Authors.
  • Things are setted up as first Revisioning tutorial teach (http://drupal.org/node/408968) and all works fine.
  • I don't want that all moderators can manage all authors content without exception, so I used OG: my Departments now are GROUPS. In this way a moderator (associated to a Department) can view/edit/publish only his Editors content. In other words Moderator and editors are in the same group (or Department). Other moderators and other editors are in other groups/department and so on.

PROBLEM 1:

"Accessible content" tabs, particularly the "I can edit" and "I can views" tabs, doesn't respect Organic Groups Content Access restrictions showing contents in the list without exception. An EXAMPLE: pending list in "I can edit" tab of Moderator1 in Department1 show also others Departments Authors entries. Notice that is only a apparent problem, because if moderator1 click on the Content title in the list, he finally can not view the content because it's correctly blocked by Organic Groups limitation access (a "you can't view this content error appear").

PROBLEM 2:

When finally a pending revision is published, I need a trigger/action combination to make this content visible to ALL users, apart from Departments and Anonymous users. Notice that there is already a OG "Make post publicly visible" action, but its not integrated with Revisioning Triggers.

Can you help me?

Thank you very much for your work.

MXT
(always sorry for my bad english)

Comments

rdeboer’s picture

Hi MXT,
Yes if you feel you MUST use Organic Groups you'll run into trouble because of the way OG does its access control. As mentioned on the OG project documentation page (http://drupal.org/handbook/modules/og): "You cannot use this module with other node access modules."

Some substantial work will need to be done for this to work.

However if you don't mind using other modules and just want solve your business problem, then I feel that using Taxonomies for your Departments in a way similar to the tutorial Revisioning with categorized content might solve your problem.

Rik

mxt’s picture

Thank you for your answer,

yes, I used OG as the "last chance", I've tried other methods without it but without success. I know that using OG is a "too heavy" solution for my necessity, I really wouldn't use it: that's the reason why I also tried to propose an alternative here http://drupal.org/node/533118. This alternative is to realize a new module " USER HIERARCHY " that implements a "parent-child" user mechanism, so an hypothetical " Edit ONLY CHILDRENS content " permission can be assigned to moderators.

I think a module like that one is still missing in Drupal, and I think it can be a valid alternative to OG in some cases, and the right answer to a lot of other users requests like: http://drupal.org/node/217695, http://drupal.org/node/44965, http://drupal.org/node/123429, http://drupal.org/node/307833, http://drupal.org/node/159126 and so on...

I've also suggested to intruce "parent-child" user mechanism in a NEW and separate module because it could be useful for other reason in other situations in combination with others modules/projects.

I don't know, perhaps the SUBUSER MODULE (http://drupal.org/project/subuser) can give some inspiration.

Take my words simple as a suggestion: i Know that building a new module from scratch is a very hard work... I'm not a programmer but I can imagine it...

What I'll do now is to continue my experiments, with or without OG, other modules and so on.

Thank you anyway for time you have dedicate to read my vent!!!

MXT

eriktoyra’s picture

@MTX I would suggest you try to follow the instructions on Revisioning with state-based content access control. I have solved your first problem together with OG using that instruction. For your second problem, I have no idea.

ideafarm’s picture

I am working on a very similar problem, did you manage to solve it, if so I would interested to know how you did it

rdeboer’s picture

Status: Active » Closed (works as designed)

Discussion seems to have died. Closing.