Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reminder Emails Should Not Go Out on Not Published Courses and Sessions #1308

Closed
dartajax opened this issue Feb 1, 2016 · 0 comments · Fixed by #1309
Closed

Reminder Emails Should Not Go Out on Not Published Courses and Sessions #1308

dartajax opened this issue Feb 1, 2016 · 0 comments · Fixed by #1309
Assignees

Comments

@dartajax
Copy link
Member

dartajax commented Feb 1, 2016

Only Published events should trigger an email reminder to be sent.

This Course ...

https://curriculum.ucsf.edu/courses/879

... was reported to have never been published and it was also reported that email reminders were being sent out.

This is the top part of the email message received by one faculty member.

-----Original Message----- From: irocket@ucsf.edu [mailto:irocket@ucsf.edu] Sent: Monday, February 01, 2016 4:00 AM

I looked in our Staging environment which was last updated on Friday (1/30/16) and the Course in question (879) was in Not Published status along with the corresponding Sessions so provided this was never Published, the email should not have been sent.

It is possible (although the reporters of this bug have denied this and I have been unable to so far to prove) that the course at one point in time had been Published and then later set to Not Published.

From the audit_log table on prod (final value for this object) ...

user_id 4796 action update
createdAt 2016-02-01 15:47:37
objectID 879
valuesChanged directors,cohorts,topics,objectives,meshDescriptors
objectClass Ilios\CoreBundle\Entity\Course

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants