I've taken a look at the notifications autosubscribe module and it seems like it should work with the notifications module (and the notifications_content module was ported to 6 already so the dependencies are there) - should the info file then be updated as well?

dependencies[] = notifications
dependencies[] = notifications_content

Comments

btmash’s picture

Ack...I realized that the module had not been ported over...I'm porting it over at the moment and will post here if it starts to work.

btmash’s picture

Assigned: Unassigned » btmash

I guess there are a couple of questions that I have regarding the autosubscribe (and notifications_content)...I think I have it working but I'm not sure:

1) Who does a notification message go to when someone adds a comment content? I see it ties to notifications_content which can have subscriptions by content type...so if I create a node of type 'page', would I be subscribed to that? Would someone else who has subscriptions to nodes of type page also get subscribed to that?
2) If a user is set to autosubscribe and they post a comment on someone else's node, are they then subscribing to that node?

I basically need to set up a system where the owner of a node is notified (automatically signed up to all their nodes) when someone posts a comment (and only the owner of said node) - is it possible via autosubscribe and notifications_content?

I still plan to update notifications_autosubscribe once I understand exactly what it does but if it doesn't do that, I'll create a separate module (which utilizes notifications) to get it to that stage.

mrtoner’s picture

All very good questions, BT.

A notification should go to anyone who is subscribed when a comment is made to a node. Don't think that has anything to do with autosubscribe.

If you create a node of type "page," you should automatically be subscribed if autosubscribe is enabled for you.

If you create a node of type "page," other users with subscriptions to content type "page" will be automatically subscribed anyway. Autosubscribe is not involved.

And it looks like posting a comment to a node subscribes you to that node.

All of this based on how I'm reading notifications_autosubscribe. Funny thing, though: I've got it enabled and the option doesn't appear on either the notifications settings page or the user account page. I'm not sure what the problem is there.

jackbravo’s picture

Title: notifications_autosubscribe module info file not updated » drupal 6 port of notifications_autosubscribe module
StatusFileSize
new1.99 KB

Here's a patch to port this module to drupal 6.

mrtoner’s picture

Status: Active » Needs work

You'll want to make sure that all the required parameters for hook_form_alter are included. Also, that they're properly spelled.

jackbravo’s picture

StatusFileSize
new1.51 KB

Ok, I see what you mean.... i spelled sate instead of state =P.
Also, i had altered the function:

function notifications_autosubscribe_notifications_node_form_alter()

which I thought was an implementation of hook_form_alter or hook_form_$form-id_alter (http://drupal.org/node/144132#form-id-alter). But now I see that it isn't. Its an implementation of hook_notifications_$type_alter which is defined on the notifications.module file. So I don't think it needs to be changed.

mrtoner’s picture

Have you actually tested this yourself? It appears you're just guessing at what needs to be done, since your form_id is wrong and the checkbox doesn't show up where it needs to. Also, you should be using diff -up original.php new.php > filename.patch or diff -urp original_directory new_directory > filename.patch -- see http://drupal.org/patch/create

jackbravo’s picture

StatusFileSize
new872 bytes

I did tested this on my computer. The form ID changed on drupal 6 for the user edit form: http://www.lullabot.com/articles/modifying-forms-5-and-6

And the checkbox does show up where it should on my machine. The fieldset changed name from notifications for drupal 5, to this version of notifications ('messaging' instead of 'notifications'). Check notifications.module file.

The diff format is what git-diff gives me. I'm not using CVS. Here's in a different format according to what you said.

mrtoner’s picture

Well, color me embarrassed! Sorry, my initial test went awry and the checkbox didn't show. Looks like it works, now.

I'm not figuring out where notifications_autosubscribe_notifications_node_form_alter() gets used. I haven't used the D5 version, so I don't know what to expect.

jackbravo’s picture

No problem. And same here, I don't know what that function is supposed to do, or where its supposed to show up if its working.

jackbravo’s picture

Assigned: btmash » Unassigned

I guess its up to one of the developers of this module to take charge of this issue.

geodaniel’s picture

Status: Needs work » Needs review

See also the patch in #310726: Updating autosubscribe code to d6 and adding subscription feature. I think the other patch adds an additional option to allow people to opt in or out of their autosubscribe default on a per node basis.

jose reyero’s picture

Status: Needs review » Fixed

The module is already updated, this one no longer applies.

Let's merge with this other thread, and reopen if I'm missing something here, #310726: Updating autosubscribe code to d6 and adding subscription feature

Thanks

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.