OG is a popular node access module where everyone inside a group are given access to view a node.

Will this work with OG such that
1. The author can give permission to only a few members inside OG to view a node?
2. Can author give permission to someone outside the group to view a node (non public node)? (I hope not. It would be negating the whole reason OG exists)
3. OG has a feature where Author can make a node view only, outside group (make it public). In such case can author make a node public but give access to only certain users outside the group to view page? So everyone inside group can see but only a few people outside group can see.(I hope yes as that would be correct behaviour)

Comments

danielb’s picture

danielb commented
Status: Active » Closed (won't fix)

Sorry I don't know OG and therefore don't understand your post.

ajayg’s picture

ajayg commented
Category: support » feature
Status: Closed (won't fix) » Active

OG (Organic groups)is one of the popular node access modules and used by 8000+ sites. Please consider supporting OG as a feature request.

It is also used for intranet and extranet by some large companies. It is also one of the key modules for the new Atrium distribution.

http://drupal.org/project/og

ajayg’s picture

ajayg commented
Title: Does this work well with OG module » Support for OG module
danielb’s picture

danielb commented
Status: Active » Closed (won't fix)

I don't intend to do anything about this. This module is a node access module and it does it's job correctly, supporting outside functionality is totally out of scope. If you need to do something with OG and it's access - please create it as an OG feature request. If you need new ways to restrict who can be referenced by a CCK field then I think you will need to build a custom module for that.

WorldFallz’s picture

WorldFallz commented
Category: feature » bug
Status: Closed (won't fix) » Active

The problem is this module doesn't work as designed with og. On your project page you say "Please note that this module will remove the default view access people have on a node" -- however, with og this is not true. Once a post belongs to an organic group all members of that group have view access regardless of the nodeaccess_userreference field config.

I spent some time on this but couldn't figure out how to fix it. If you don't / can't support og that's fine, it's your module, but you might want to mention it on the project page so people don't waste hours trying to figure out why it doesn't work.

I stumbled across this while helping a user in the forums-- just thought you should know.

danielb’s picture

danielb commented
Category: bug » feature
Status: Active » Closed (fixed)

Please don't reopen this issue unless you're willing to address the points that I made in #4, AND you are either a user of this module or you maintain your own node access module. The fact that you call not explicitly supporting a contrib module a 'bug' is just counter-productive. Show me what I've done wrong in terms of supporting DRUPAL - show me documentation I haven't followed - show me something in the API that says I have to consider organic groups.
It's quite obvious to me - if you want to do something with organic groups then you post about it in the issue queue for organic groups - you don't pick one random node access module and demand support for some obscure use-case. I'm not convinced any of you require the functionality provided by this module let alone whether any of you have actually downloaded it. Additionally show me that modules like Nodeaccess has already added such support - and why you aren't posting about this there.

WorldFallz’s picture

WorldFallz commented

wow-- i just thought you might want some more info on this issue-- i appreciate these kinds of posts in my issue queue. Not sure where all that hostility is coming from, but no worries-- you won't fine me helping out in your issue queues anymore.

ajayg’s picture

ajayg commented

@danielb
your module provides what other node access modules do not so we haven't asked there. I get the request from my users (who are members of organic groups) quite often that they wish instead of everyone in the group having access to a node, there was a way they could give access to only a few members. My original request was a feature request and and I respected your decision to support it. Anyway that matter ends here from my side.