This is an excellent module.

Please may I request an option whereby notifications would behave more like the notifications on systems like Simple Machines Forum and vBulletin: i.e. the system sends out a single notification for each node, no matter how many comments are added to the node. The system doesn't send any more notifications until the user visits the node again.

Here's a use-case to better explain what I mean.

User A posts a new forum topic on Monday morning and then doesn't visit the site again until Wednesday morning.
On Monday afternoon, 5 replies are posted but user A only receives a single notification. But this notification is sent immediately after the first reply is posted.
User A re-visits the node on Wednesday and then doesn't visit the site again until Friday.
On Wednesday afternoon, another few replies are posted. The site sends user A another single notification on Wednesday afternoon.

Such a feature would be really useful, IMHO!

Comments

dan_aka_jack’s picture

dan_aka_jack commented
Title: Send 1 notification then wait for user to log in » Send 1 notification per node then wait for user to visit node

I'm developing some ideas for how this feature might work (I'm relatively inexperienced at coding so I might be barking up completely the wrong tree!)... please let me know if this sounds sensible:

Examining the database tables, it looks like the history table records the time each user visited a particular node and that the notifications table records every subscription (please let me know if this is incorrect)

My proposal is that I'd add a column to the notifications table to record when each notification was last acted upon.

Whenever the module is asked to send a notification, the code would compare the $notifications->timestamp with $history->timestamp for the node and user in question. If $notifications->timestamp is less than $history->timestamp then the user has visited the node since the last notification was sent and hence a new notification should be sent and $notifications->timestamp should be updated.

I'm assuming it's relatively trivial to find the relevant node ID for each SID, although I haven't figured out how yet!

I'd also propose that this functionality would be configurable on a user-by-user basis (i.e. each user would be able to enable or disable this behaviour) and that the site admin would be able to configure the default setting for new users.

Of course, a complete patch would also have to modify the module update code to make sure that the module adds the new timestamp column to the notifications table when the module is updated and I guess would also have to fill the timestamp column with some default value (possibly 0 would be acceptable?).

tsi’s picture

tsi commented

How come there is no action on this thread ?
This seems to me like a very important feature. I just got 11 notifications for a single node.
Hope it will get some attention soon.

sagannotcarl’s picture

sagannotcarl commented

I've got this working on a site with a new subscription type that only notifies people of the initial post, and then doesn't subscribe them until they comment on it or specifically subscribe to it. I started an issue a while ago about this #341500: Notify users of specific node events and got some help implementing it.

I'll try to post up what I've got there.

Personally I wouldn't want to be subscribed to all the comments on a node just by visiting it if I hadn't done something else to participate on the thread (like commenting or clicking a subscribe link), but maybe that's just me.

tsi’s picture

tsi commented

We are not talking about subscribing to a node just by visiting it, but only the ones the user participated on.
The issue is about sending a notification and then wait for the user to visit the node without sending any other notifications even if there is activity on the node.
I posted here , hope it will happen someday soon.

jose reyero’s picture

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

... which means "reopen if you have a patch".

jdln’s picture

jdln commented

subscribing