Review and improve the digest email

[mconf-daileon]

---

Author Name: Leonardo Daronco (Leonardo Daronco) Original Redmine Issue: 1292, http://dev.mconf.org/redmine/issues/1292

---

The code was never improved after migrated to Mconf-Web v2. A few things that can be done:

• Change the view from erb to haml.
• Instead of fetching all the resources individually (e.g. @Post.where()...@), use the user's recent activity. We could simply get all the recent activity items for the period asked and send them to the user.
• Verify if the option to change the frequency works (see #1042).
• Add more tests.

[mconf-daileon]

---

Original Redmine Comment Author Name: Lucas Zawacki (Lucas Zawacki) Original Date: 2016-04-07T21:22:10Z

---

Consider separating what constitutes:

• Notifications: Things happening in the portal that the user would be interested in knowing about. They're organized in chronological order and can be seen as a list, e.g., in the user page
• Emails: The method used to deliver the notifications to the user. This can be configured on or off and the frequency can be controlled. For example, a user may get their notifications emailed daily, or get an email each time a new one is created, or get no emails altogether by disabling it.

When thinking about changing this, we should consider having a good notification system (making RecentActivity better would be a good choice) and having a good email system (with appropriate queue priorities as per #1790) which only notifies users via email and can be configured.