Closed (fixed)
Project:
Revisioning
Version:
6.x-2.7
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Jul 2009 at 09:53 UTC
Updated:
26 Sep 2009 at 15:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
rdeboerHi MXT,
So you want to integrate Revisioning with a hypothetical module....
That could be difficult...
I have read your comment at http://drupal.org/node/408018, but am unsure as to what exactly you're after. Would you be able to give a clear example?
Also, it sounds very much like a Taxonomy issue, rather than a Revisioning issue?
Rik
Comment #2
crea commentedHypothetically, it's possible.
Comment #3
mxtRdeBoer, Crea, thank you very much for your answers, sorry for my poor English, it's not my native language, that's why I apologise in advance if I'll be not so clear.
I'll try to explain my problem better: the "matrix" approach I've already explained in my comment here http://drupal.org/node/408018#comment-1779526 works very well in a situation where a moderator have to moderate only and only one department.
The problem rise when there's the necessity that a moderator have to moderate more than one department: in this case, with the configuration above, the moderator will see for revision not only contents from authors belonging to his department, but from others one too, and that's what i DON'T want.
EXAMPLE:
But doing so Moderator_2 will see also Moderator_1's authors contents in his pending table! While he have to see ONLY his authors contents.
That's why I suggested to resolve the problem with a "parent-child" user mechanism, so an hypothetical "Edit ONLY CHILDRENS content" permission can be assigned to moderators.
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.
That's all, thank you very much for your interest in this problem.
MXT
Comment #4
mxtIn attachment to this comment 2 images with diagram to try to explain my problem better.
MXT
Comment #5
rdeboerThanks for the clarification MXT,
I need some time to digest this.
Rik
Comment #6
crea commentedThis may help: #549414: Even more granular "view revisions" permissions.
Comment #7
crea commentedI believe what described here can be simply implemented using Taxonomy Access Control module or some other taxonomy access module.