-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add referenced links to e-mail notifications #177
Comments
@Artmir I agree. I will happily accept patches with new default text! |
Unfortunately haven't had time to play with github that much to be able to apply patches. I hope it is ok if I send the text and links to you when I come up with some. |
Sure! Let's use this thread for that. |
E-mail notification for new comment. Tested working as of 3.0.8. Will update on the other message templates later.
What's funny is why don't the url's automatically translate without having to hyperlink them manually. |
Here is the full list of message templates I managed to create. Worth to note is that when idea moves back to 'needs work' there is no notification event fired in the announcement nor in the e-mail. I feel that at least the author should be notified. Also when new content is created (new node, challenge, idea etc) users will not get notified by e-mail.
Challenge status:Third placeholder:
Created challenge:First placeholder:
Third placeholder:
Created like on comment:First placeholder:
Third placeholder:
Created reply to comment:Third placeholder:
Create like on node:Third placeholder:
Idea life-cycle change:Third placeholder:
New comment created:Third placeholder:
New discussion:First placeholder:
Second placeholder:
Third placeholder:
User mention:first placeholder:
Third placeholder:
|
I suggest adding the above updated message templates to the ver. 3.0.9 |
There is a need for links to be added to the referenced content when sending out e-mail notifications for: New comment, liked comment and possibly others.
Currently only plain text is sent.
The text was updated successfully, but these errors were encountered: