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

Send recompletion message from an email different than the primary site admin #190

Open
abias opened this issue Aug 8, 2024 · 1 comment

Comments

@abias
Copy link
Contributor

abias commented Aug 8, 2024

This issue might overlap with #23, but it goes beyond it:

One of our customers was wondering why the local_recompletion messages are coming from the primary admin - and I was wondering as well.

Looking at

, I see that the messages are really sent by the primary admin which does not really make sense in our hosted environments where the primary admin is always a special support user.
But in other scenarios, it might not make sense as well as a student won't necessarily know the name of the Moodle admins.

Talking to Dan privately, we found two feasible improvement approaches:

The larger one:
The teacher configuring the course recompletion would be able to select the sender from the list of course contacts (as defined by $CFG->coursecontact). If the selected sender is unenrolled or if the teacher does not select anyone at all, the fallback will be support email. And if this is not set, it will default back to the admin email.

The smaller one:
A global plugin setting which would allow the admin to set the sender for all activity instances and courses.
This setting would offer these options:
• Primary admin (default and current behaviour)
• Moodle Support user
• Moodle Noreply user

Unfortunately, we did not receive funding for this implementation up to now, but I document the discussion result here anyway to allow other community members to step forward and craft a PR.

Cheers,
Alex

@danmarsden
Copy link
Owner

Thanks for adding it here Alex!

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

No branches or pull requests

2 participants