saucy/app/views/notification_mailer/expired_30d_ago.text.erb

<%= render partial: "greetings", locals: { member: @member } %>

A tua inscrição como membro da ANSOL expirou há um mês e ainda não recebemos
a tua contribuição anual.

Dependemos exclusivamente da contribuição dos nossos membros para suportar as
nossas actividades. Gostaríamos de continuar a contar com a tua participação.

<%= render partial: "payment", locals: { payment: @payment } %>

Caso não recebamos o pagamento até dia <%= @member.cancelled_on
%>, cancelaremos permanentemente a tua inscrição. Estamos disponíveis para
esclarecer qualquer dúvida através do endereço direccao@ansol.org.

<%= render partial: "cheers"  %>
Improve branding mechanisms 2023-09-20 13:19:35 +00:00			`<%= render partial: "greetings", locals: { member: @member } %>`
Add first iteration 2022-06-25 12:48:46 +00:00
			`A tua inscrição como membro da ANSOL expirou há um mês e ainda não recebemos`
			`a tua contribuição anual.`

			`Dependemos exclusivamente da contribuição dos nossos membros para suportar as`
			`nossas actividades. Gostaríamos de continuar a contar com a tua participação.`

Adds payment page Instead of sending all the payment details by email, we're now sending only a link to a page on this platform. This is to help reduce questions of whether the emails are from scammers or real. 2023-07-12 18:13:08 +00:00			`<%= render partial: "payment", locals: { payment: @payment } %>`
Add first iteration 2022-06-25 12:48:46 +00:00
Redo notification system Previously, saucy generated each member's future notification every day (marked as scheduled). And every day saucy would deliver every unsent notification scheduled for that day. This means that each member with expiration date in the future had ~6 notifications scheduled for them in the database. This was troublesome because if the cron job that delivers notification was down or the server was down for more than 24h, notifications were silently skipped and we had no easy way of detecting it: we had to check every member for missing sent notifications. It also had the disadvantage that we were deleting and recreating hundreds of database entries for no good reason. To fix this, the new system no longer stores future scheduled notifications. Instead, it now only stores sent notifications and notifications currently being delivered. Every day, the deliver task checks every member if there's a notification that needs to be sent in that day, by checking if we're past the date of sending a particular notification type and checking if in that window of time no notifications of that type have been sent. Let's suppose we send 6 notifications, one per month starting 60 days before the membership expires until 90 days after: -60d -30d t=0 30d 60d 90d ----\|------\|------\|------\|------\|------\|------ A B C D E F If we're on day t=-60d, we need to deliver a notification of type A. But first we check if no notifications of type A have been sent to that member on that day. From days t=-59d to t=-31d, we check if in the time range t=[-60d, -31d] any notification of type A was sent to that member. If not, we need to deliver it. If we're on days t=[-30d, -1d], we do the same but for notification of type B. 2024-03-23 15:22:04 +00:00			`Caso não recebamos o pagamento até dia <%= @member.cancelled_on`
Add first iteration 2022-06-25 12:48:46 +00:00			`%>, cancelaremos permanentemente a tua inscrição. Estamos disponíveis para`
			`esclarecer qualquer dúvida através do endereço direccao@ansol.org.`

Adds payment page Instead of sending all the payment details by email, we're now sending only a link to a page on this platform. This is to help reduce questions of whether the emails are from scammers or real. 2023-07-12 18:13:08 +00:00			`<%= render partial: "cheers" %>`