Transition Technology: Ticket #568: TC blog: can't not send notifications

hours, totalhours changed

jim — Tue, 09 Jul 2013 10:03:03 GMT

hours changed from 0.0 to 0.15
totalhours changed from 0.0 to 0.15

As part of the 'stop sending updates for everything!' issue, I actually turned off the events that send on update for many content types that didn't seem to warrant it.

Go to https://www.transitionnetwork.org/admin/messaging/notifications/events and see what is on/off...

In other words, 'update' notifications are simply not sent any more for any blog or new types, only 'meaty' or time-relevant content types send updates.

Is this ok?

jim — Tue, 09 Jul 2013 10:32:15 GMT

Obviously notifications for creation of these nodes is still enabled...

ed — Tue, 09 Jul 2013 11:15:55 GMT

SO. Please confirm:

notification sent on creation of node - does this happen if it's created and 'not' published? or just when it is 'published'?
no updated notifications sent - ie drupal will not send notifications when author edits previously created node

attachment set

ed — Tue, 09 Jul 2013 11:25:08 GMT

attachment set to Screen Shot 2013-07-09 at 12.24.12.png

Screengrab of notifications option when adding normal blog post

ed — Tue, 09 Jul 2013 11:26:31 GMT

and question 3

if I create a post and do not publish it, how do i send a notification when it is pbulished?

hours, totalhours changed

jim — Tue, 09 Jul 2013 14:01:55 GMT

hours changed from 0.0 to 0.1
totalhours changed from 0.15 to 0.25

OK:

No idea, probably worth testing. I'd guess 'create' events go out, but since the publish is an 'update', that won't go.
On the content types not checked for 'Update' on https://www.transitionnetwork.org/admin/messaging/notifications/events, no update events will fire, so no emails sent.
We re-enable updates and write my tinkering off as a good idea poorly exectuted...

Basically, since the issue with comment spam is solved, we can re-enable update events on the content to get that back, together with the 'Do not send notifications for this update' checkbox.

If you can check https://www.transitionnetwork.org/admin/messaging/notifications/events and either tick the CTs you want to re-enable events for, then the previous behaviour will return. Or let me know you just want them all enabled and I'll do it.

It was the 'comment' events causing the issue with Rob's blog subbers, so leave that alone...

Let me know.

ed — Wed, 17 Jul 2013 11:17:32 GMT

it seems that the email alert is triggered on PUBLISH - ie we can work on items that are not published and that will not send email alerts - UNTIL PUBLISHEd...

updating items does not send update email alerts

this is no longer an issue

... I think... not closing yet though.

ed — Wed, 17 Jul 2013 17:01:53 GMT

following a panicked blog post going out with alerts and various view appearances around the site, we need to go back to where we were:

re-establish the 'do not send notifications for this update' tickbox on

1a. /news 1b. /blogs 1c. /stories

So we can be doubly sure for a while while the dust settles

hours, totalhours changed

jim — Wed, 17 Jul 2013 18:01:55 GMT

hours changed from 0.0 to 0.2
totalhours changed from 0.25 to 0.45

Done -- all CTs have their 'Updated' events notifications re-enabled on https://www.transitionnetwork.org/admin/messaging/notifications/events, which takes us back to the state we were in at the beginning -- BUT the comment notifications for blogs are still set to off so we don't 'spam' people.

The "do not send notifications for this update" box should now be back -- please confirm.

status changed; resolution set

ed — Wed, 17 Jul 2013 18:56:24 GMT

status changed from new to closed
resolution set to fixed

confirmed and closing

Transition Technology: Ticket #568: TC blog: can't *not* send notifications

hours, totalhours changed

attachment set

hours, totalhours changed

hours, totalhours changed

status changed; resolution set

Transition Technology: Ticket #568: TC blog: can't not send notifications