I was thinking of the idea to create a default set of confirmation emails and only allow the admins to change the text for this. This way users that can create events can't send out emails that damage the site owners.
The users on my site wouldn't necessarily be "staff" just "privileged". And I don't see a reason for allowing these users to have control over email that will get sent out in the company's name.
Maybe a specification option:
Allow event author/event coordinators to have personalized emails?
[x] yes
[ ] no
Help: Selecting 'yes' will allow the creators of the event/content type to customize the emails being sent out. Selecting 'no' will only allow admins to customize the email confirmations/cancellations/etc...
Just an idea?
Thanks
Comments
Comment #1
dwwSeems closely related to #118794: Using Event author for "send signups to" address. Please read that. Not marking this duplicate, since you're talking about customizing the text of these messages, whereas the other issue is about locking down where they get sent.
Comment #2
dwwI think the basic concept articulated in this feature request is a good one.
However, I believe the whole email functionality of this module is weird and needs rethinking.
Therefore, this is hereby postponed in favor of #290305: Split out email functionality into separate submodule(s).
Comment #3
bsherwood commented@dww:
I agree! While email notification isn't actually required, it does help in informing users of their signups and progress.
Since you have professed your desire to remove the email functionality into sub-modules, maybe hooking it into another notification framework would be easier to maintain, flexible and more robust. The Notifications and Subscriptions modules come to mind.
Comment #4
dww@specmav: wrong thread. ;) Please post your ideas about the reorganization in the reorganization issue...
Comment #5
duaelfrThis version of Signup is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.
Comment #6
simon georges commentedReverting recent closing.