This is apparently a notify problem as Moshe has "declined" it in OG :-)
When 'notify' is turned on (notify.module) and then a new group is created, a notification email is generated. Subsequent content restricted to a group is not later notified.

The creation of the group should be excluded from being reported by notify.module. Merely the creation of the group might or might not be something the group creator wants to have announced.

gil

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented
Category: bug » feature

Well, you could create a config option that lets the admin chose which node types should be informed about.

I am not tempted to work on this myself as I think that group nodes are content just like anythign else. if they are not visible to a particular user, they will not be mailed.

Capnj’s picture

Capnj commented

I think I did not make myself clear.
I'm talking about the the GROUP itself is first created ... not the addition of a group-related node.

I see the problem as being that you might have a group to be created to collaborate on a super-secret project :-) that you don't even want the general users on the site to know about. Area-51 research for example. If the NOTIFY module tells everyone about the group then the cat is out of the bag.

Solution: if it is an invite only group, then don't notify about it.
gil

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Closed (won't fix)

I understood you well, I was talking about that group itself. :)

If that group is super-secret then the node access permissions should protect it from being seen by other people. Those permissions need to be set by the og.module and will automatically be honoured by notify.module.