Best practice forum (Archived)

Este foro de discusión ha sido eliminado.

 
Esta publicación en el foro ha sido eliminada.
Wednesday, 19 de February de 2014, 12:06
El contenido de esta publicación del foro se ha eliminado y ya no se puede acceder a él.
? ?
Re: Face to Face notifications sending incorrectly
de ? ? - Wednesday, 19 de February de 2014, 13:37
 

Hi John,

Yes, the issue with the notifications sending out emails to all users booked on all historic sessions was fixed recently in 2.4.17 and 2.5.7. Sorry for the inconvenience!

David Curry (Core Developer)
Re: Face to Face notifications sending incorrectly
de David Curry (Core Developer) - Wednesday, 19 de February de 2014, 18:39
Grupo Totara

Hey John,

I've had a closer look and you are right, something strange is going on with that "no shows only" setting. I'll file a bug and try get a patch in a release soon.

As for the sending to historic facetofaces, the patch included recently fixed this for "Before Session" notifications, because it was fairly easy to see when to cut off the notifications (when the session starts). However where would you suggest setting the cut off for "After Session" notifications? x days after the notification... but not for ones over a week old? And then you have to start wondering about things like, what if they want to send it to everyone 8 days after sessions, or if they want to send it to 2 week old sessions. The only way I can see to make this work for everyone would be to add yet another setting to that page. I'll add a separate enhancement bug for that.

Cheers,
David

Esta publicación en el foro ha sido eliminada.
Thursday, 20 de February de 2014, 08:16
El contenido de esta publicación del foro se ha eliminado y ya no se puede acceder a él.
? ?
Re: Face to Face notifications sending incorrectly
de ? ? - Monday, 10 de March de 2014, 19:47
 

A fix for the "no shows" issue was included in today's (11th March 2014) release of Totara 2.4.18

? ?
Re: Face to Face notifications sending incorrectly
de ? ? - Monday, 17 de March de 2014, 21:17
 

A fix for this issue was included in today's (18 March 2014) release of Totara 2.5.10