Subscribe OG module [#2406413]

I found that when any admin views subscription tab of other user then he/she see's his own subscriptions where he/she should be able to view subscriptions of that user. I found the og fix at https://www.drupal.org/node/1983226

I made a views handler change in flat at https://www.drupal.org/node/1473716#comment-9505947 , this will allow manipulating flags option to admins. I am attaching a patch for the og_subscribe_email view, same can be copied to other subscribe views.

Thanks,
Sadashiv.

Comment	File	Size	Author
#3	Subscribe_Og-2406413-3.patch	34.49 KB	sadashiv
#1	Subscribe_Og-2406413-1.patch	34.44 KB	sadashiv
	admin_can_not_see_subscriptions.patch	9.06 KB	sadashiv

Comments

Comment #1

sadashiv commented 15 January 2015 at 07:47

Title:

Allow admins to see subscriptions of other users

» Subscribe OG module

Status	File	Size
new	Subscribe_Og-2406413-1.patch	34.44 KB

Hi,

I went ahead and created a separate module which handles notifications for group content create and comment post on group content for og. I am attaching a patch for the module which should be helpful.

Note that it still needs the flag module change patch from https://www.drupal.org/node/1473716#comment-9505947

Hth,
Sadashiv.

Comment #2

rsbecker commented 15 April 2016 at 12:02

Status:

Needs review

» Active

Once I got this working I was somewhat surprised/appalled that it does not respect node/message status. It sends an email regardless of whether the node or comment is published. Two fixes are needed.
Change line 20 from:

  if (og_get_group_type('node', $node->type, 'group content')) {

  if (og_get_group_type('node', $node->type, 'group content') && $node->status == '1') {

and change line 42 from:

  if (isset($group_content->{OG_AUDIENCE_FIELD})) {

  if (isset($group_content->{OG_AUDIENCE_FIELD}) && $comment->status == '1') {

Comment #3

sadashiv commented 15 April 2016 at 12:08

Status:

Active

» Needs review

Status	File	Size
new	Subscribe_Og-2406413-3.patch	34.49 KB

Thanks for testing this and reporting this issue. Made that change in the patch. Please test and update if it works.

Hth,
Sadashiv.

Comment #4

rsbecker commented 15 April 2016 at 16:54

I'm afraid I goofed a little, and didn't expect such a fast response. There's a syntax error in both fixes. They should be:

... $node->status == 1) {

... $comment->status == 1) {

But this brings up a further question, which may just be a small feature addition. If you start with an unpublished node, the module should kick in once the node is published to send messages. Otherwise, I need to create a rule to send the message after a moderator/editor publishes the node.

Thanks

Comment #5

liquidcms commented 20 January 2017 at 23:53

Any hint as to what this does?

I am looking for a way to have og members notified of og content updates. Does anyone know if there is a solution which does not require writing a new module? I do not think this module does this does it? Or possibly still requires the crazy flag setup defined here: https://www.drupal.org/node/2205741 ?

Comment #6

rsbecker commented 21 January 2017 at 14:40

You need to set up the message message_notify and message_subscribe modules to do this. It is a little complicated because you also need the flag module. Amiti Burstein has a good video to get you started.
https://pantheon.io/blog/drupalcon-portland-video-amitai-burstein-organi...

Comment #7

liquidcms commented 21 January 2017 at 21:54

cool.. thanks for the link.. funny video. sadly only about 5 min out of the 40 related to this; with a lot of "and i'll leave that up to you" or "you need to write the drush code to do that"... but i think this may answer my question - which i think is that there is no complete solution to handle notifications of OG content (was sure that existed in D6 version; but been a while now).

before posting i had tried to set up message, message_notify and message_subscribe modules but they also do not seem to do anything plus any guides i have found end up causing numerous errors.. but perhaps just config missing which i can sort out through trial and error (some of which is covered in the video you linked above).

i'll let my client know that there is likely code required to tie this all together and then get started sifting through what each of these pieces does. thanks again.