Subscribing to Views

please Help! How I download Subscriptions with Views?

Yes! Anyone care to supply a patch?

I second this. Would be very, very interested in it.

Views and Subscription, that would be great.

#269472: Subscriptions View

This does not appear to be a duplicate of #269472: Subscriptions View, which is asking for a view of subscriptions, rather than subscriptions to a view.

#197146: Subscriptions_Views Interface and #252152: Views Integration? are duplicates of this, so I've changed this one back to "active", as it's the oldest.

I've taken the liberty of upping the version, as Views 2 is just a completely different beast to Views 1, and I think implementing comparable functionality on both platforms would be a big ask.

Happily, Views 2 allows you to create queries which can return nodes, terms, or users, and subscriptions is designed to allow you to subscribe to particular nodes, nodes in particular terms, or nodes by particular users (well, blog posts at least), so it seems like a better fit than Views 1.

I see your point. What I don't see is how you can tell whether a view has changed since the last time that you looked at it.

I don't think you'd want to get the same view content over and over again, or do you?

I think the way to look at it would be to say that when you subscribe to a view, you're not literally subscribing to the HTML output of the view, but to the nodes, users, terms, or whatever that the view returns. The subscriptions module periodically executes the view (via cron), checks for new items against a record of the items returned the last time the view was run, and subscribes people to those items if they've "subscribed" to the view.

Ok, then what does a "record of the items returned the last time" look like, such that you can find the new ones?

What about updated items? deleted items?

I haven't thought it through very thoroughly (obviously), and I'm just about to hop on a plane and be away from my computer for a fortnight. I was thinking a table with the view name and just a serialized array of nids, tid, or uids. I'm not a chx, so I couldn't say how well that would scale. I expect a whole lot of in_array()s over a lot of views with large result sets might be sub-optimal.

As you're really subscribed to the item, not the view, updated items (and deleted items as in the actual node/user/term being deleted rather than just not appearing on the view any more) will be handled in the usual way by the subscriptions module.

As for items not deleted, but just not returned by the view any more, I suppose you could present the user with an option to delete or retain subscriptions to items that drop off the view at the time they subscribe. That's also problematic, as you could be have been subscribed to that item prior to it turning up in the view. I am not familiar with how subscriptions works; perhaps you already have a way of dealing with such clashes.

For that matter, you could implement this in the same way that RSS is done in views and iCalendar is done in the Calendar module. Subscriptions provides a display type which can be attached to another display; ie. a little link icon will appear on the bottom of the page, block, or whatever, which will take you to the subscription UI for that view/display.

Hmm, what you're describing is not "subscribing to a view", but using a view as a meta-subscription, i.e. creating (thread?) subscriptions to the nodes in the view.

I took #6 to be about sending updated view contents whenever the view changes, which is something completely different.

I'm confused...

Hello, I would like this feature as well. Though I have no idea how it would be implemented.

I think it is better not to use subscription and get this out in an own module. I have started a thread in ther forum to discuss ideas.

http://drupal.org/node/319972

RSS feeds already track the new arrivals in a View (using the views_rss module). It seems that it would be the same kind of idea to track and email new content, rather than simply posting it via RSS. I had been using an rss-to-email conversion script to do this, but it's fragile, and I'd rather have this functionality within the Drupal module.

This could be a good pointer, but where is views_rss?

Post # 14 mentions that views rss already tracks new views content, this is a great point. This would be a great enhancement for our site and would certainly promote return visits on any site extensively using views. It doesn't look like there has been any discussion on this since December of last year, I'm wondering if there is still interest...

Views and RSS works great.

I think the main idea was a subscription via Email to a view.

RSS Feeds are simple for a view. There are several ways to provide a RSS Feed over views results, but no simple solution to subscribe via email.