I need help of someone who knows the Organic Groups module (og.module). Though it does a lot of great things, it unfortunately renders all node access modules useless, at least this is what its descriptions says.
I need the following access methods. Probably I could emulate them by writing action scripts that create groups on themselves, add the users to it that are allowed to perform an action, set the permission rights and remove them again - if I combine it with the workflow module, it could be possible. However, I don't know the OG module good enough to decide how much work it would be. I'd like to know from an insider how doable the following access methods would be:
- Some users in a group only can "view" posts, others can edit all posts. This is important for certain types of announcement postings that need updating from a group of dedicated helpers without giving everyone in a group the possibility to mess with posts from anyone.
- A book page can be set on status "consider for inclusion" with the workflow module. Once it is set on this status, a group discussion via mailing list ensues. As long as the node is set on this status, the author should not be allowed to edit the node since it would invalidate the ongoing discussion if the content was to change without announcing it first and stopping the discussion.
- Using the "userpoints" module, users can do workshops (essentially read book pages). However, each book page costs userpoints that are substracted. Only users that engage in community activities can continue to read those workshops. How could I handle those access rights? Probably I could reate groups like "workshop_#1_unit_1" to "workshop_#1_unit_20" for every workshop and if a users wants to read unit 2, he has to join the next group (and on joinig userpoints are subtracted), but this seems very clumsy.