Where's the subscribe link ???

Hi pictogram,

Yeah, basically you are missing the end user documentation we still haven't had the time to write... :-) That's also why this module is tagged as a developer's preview yet.

So, answering your question, and maybe I can reuse this for the documentation :-), here's how it works:

- First you enable the UI module and the modules providing subscription types (I.e. notifications_content)
- Then you enable the subscription types you want to see in Administer > Notifications > UI ....
- Then you go to the content types administration and enable it for your content type. Only the Links option is already fully working.

Then you'll have plenty of Subscribe/Unsubscribe links for each node depending on which type it is.

Just don't forget to come back and let us know if that's working for you. Thanks.

Hey thanks for your reply,

I was missing the third part. It works now. I'm building an multilingual intranet and user subscriptions will be very useful. I tried working with "Subscriptions" but it was a nightmare trying to have the "Mail Templates" working correctly. I found yours and (even if looks alike) seems to be promising especially with email template managing and multilingual capabilities. For when do you plan the "Support for message localization for multiple languages" ?

Thanks.

Hi Jose,

Great sounding module. I'm trying to use it to notify admins of my site when certain types of content are created by users.

So I tried the same thing and still cannot find the subscription links ... they're supposed to be on the node pages themselves? Or they show up somewhere else?

Thanks
Noah

Same here. Did all three steps and no subscribe links. ARGH

NM, missed step 2. Ugh. This is overly complex and the lack of documetation makes it nearly unusable.

I did the three steps, though not in that order (the UI I did last). The confirmation that something was running I got from the content type story which offered three options for the location of the subscription form.
When I tried to make a new story there was nothing that reminded of notifications (maybe intended) and when I tried to submit the story I got the error message below:

user warning: Unknown column 's.conditions' in 'having clause' query: INSERT INTO GRK_notifications_queue (uid, sid, eid, send_interval, send_method, cron, created) SELECT DISTINCT s.uid, s.sid, 3, s.send_interval, s.send_method, s.cron, 1202242069 FROM GRK_notifications s INNER JOIN GRK_notifications_fields f ON s.sid = f.sid WHERE s.event_type = 'node' AND ((f.field = 'nid' AND f.value = '170') OR (f.field = 'type' AND f.value = 'story') OR (f.field = 'author' AND f.value = '1')) GROUP BY s.uid, s.sid, s.conditions HAVING s.conditions = count(f.sid) in /home/www/klimatosoof/includes/database.mysql.inc on line 172.

The main reason I need the module is to let commenters know someone reacted to their comment.

Thanks

Theo Richel

I'm seeing both links and forms though links are turned on via the content type definition. Perhaps I am mistaking a separate form that's just for comments? If so, why have both, or why not have control over the comment form?

See screen shots. Ignore the coloring of the second. When I activate Screengrab, a Firefox plugin, it changed some CSS somehow. I've seen it a couple of times, but don't know why it happens. Anyway, the info is the same.

EDIT: I thought that maybe the post2.png stuff was for the 'thread' messaging option, but unchecking it seems to have done nothing. I still see the fieldset.

I'd also like to suggest that the controls that are currently within the content type edit page be moved to a central location. You see, why not just use the "Omitted content types" from the admin/notifications/settings/content page, or "Allowed content types" from the admin/notifications/settings/group page? Actually, it's probably bad for to have one be omitted and the other allowed. You should probably select one method a stick to it.

I hope you don't mind all of my comments in the various posts today that I've made. I'm very excited about this module and would like to help get it finished.

It seems the post2.png above is in fact tied to the comment. So that means that even having set "As form below the node content", I am not seeing any form when viewing nodes since I changed the comment form (as a test) to be on a separate page.

So, in other words, when I first installed and enabled everything, I was seeing the subscription form, which I thought was for the node, but which is for the comment instead - even though I had NOT gone into the content type settings and enabled the subscription UI for that type. Setting that control to "As node links" works, as my post1.png shows.

So this all begs another question: or comment subscriptions separate from node subscriptions and will they only show posts 'under' that comment, or all comments for that node? There is an option for "To this post", but I'm asking for clarification on the word "post" in this context.

Thanks.

I've committed some changes to have easier defaults, so i.e. links will show up as a default now. These changes will make getting started much easier.

However the UI module is just a generic approach for handling all types of subscriptions. Agreed we can make some usability improvements for the settings pages but options in that module are there to stay and possibly there'll be a few more in the future.

It doesn't pretend to be simple but to allow lots of options. It is a 100% pluggable UI so it can be replaced by a simpler one, only no one has coded it yet :-). But the whole idea behind this framework is that you can plug-in any custom UI you need -as long as you're able implement it- and we'll be only providing a generic one, that may do for lots of cases, but it will be also complex to set up (flexibility++)

What we are doing for sure is better documentation and help pages, that will be coming soon. The form option is currently broken, will be fixed. And the full UI definitely needs some polishing.

Thank you for all this feedback.

I'll check for new versions regularly and post comments to changes in appropriate threads. Thanks for your work. I know how this module release/maintenance thing is. D.O. people can be a tough crowd.

Just committed lots of UI improvements, and some more have gone in during last week. Hope everybody can find the links now. I'll mark this as fixed, reopen if still having trouble

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