 |
Maybe not in core, but : MUST be extendable by plugins. |
 |
Why not in core? What's the difference with the other emails that we can change? (note that I'm speaking from an end-user perspective, no clue about the underlying technical mechanisms etc) |
|
|
I say : maybe not in core. And why not in core : because if we have a global system to extend any email : if you want to update the email sent when user regitering or whith another email etc ... then you have what you want. If a dev put it in core : i don't help him. If a dev work on a plugin i help him. It's my choice. |
|
|
Thanks for the explanation. Seems you interpreted my question as an attack; let me say it absolutely wasn't intended as one. If you say 'maybe', apparently there's some argument(s), and I was just curious what those arguments are. I just didn't understand why it shouldn't be in core, s I ask a clarification question. Not saying you should help any dev or not or whatever. Your choice indeed ;) As you might have guessed by now, I'm a noob - and still don't really get it. You're saying that while the Invitation, Reminder, Confirmation and Registration emails can & are set on a per-survey base, this is cannot be the case for 'Saved answer' email because these 'Saved answer' emails might also be affected by a global system that changes the email content? "if you want to update the email sent when user regitering or whith another email etc ... then you have what you want" Yup, I figured that's already possible, and I would imagine that same functionality for the 'Saved response' |
|
|
Hi, Sorry my english is bad .... don't want to 'attack' just explain more :) Actually i really think plugin is better : more easily manageable for a specific purpose. Each time we make an update on LS core : some user have specific error : they don't need this update but this update affect us. Sometimes : they don't need the functionality (for example : some user never send mail via limesurvey), but fix/improve mail system can - Make a bug for them too - Add some page and page again for them too (LimeSurvey have a lot of option : and sometimes it's hard to find the good option) Then : make a event + a little plugin : - You have what you want - LimeSurvey is more simple to manage for us - LimeSurvey is more simple to understand for other users Denis PS : you're right too : we can have a "global" save email (transaltion in each language available) + email text for survey specific usage. PS2: i think too a lot opf "default" string must be updatable by plugins, for specific purpose. |
|
|
> Actually i really think plugin is better : more easily manageable for a specific purpose. > Each time we make an update on LS core : some user have specific error : they don't need this update but this update affect us. > - LimeSurvey is more simple to understand for other users Right, I understand that it's easier to maintain in a plugin (& less chance on a bug). However, many of the other emails can already be adjusted; that functionality already is in core. Because it's already available, I think it's not making things extra difficult for users. So indeed the option to change emails is in core already (see screenshot, I added 'Saved answer' as a bad mock-up). Are you suggesting they should be removed from core and instead be placed in a plugin? |
|
|
Screenshot from 2016-05-15 23:46:15.png (59,108 bytes) |
|
|
Did any decision was reached about this? I also think this should be a core feature. Imo, survey owners should be able to modify this email template the same way they can change the others through the "Edit email templates" in the admin interface. Thanks! |
|
|
Can be done in plugin in 4.0 : https://github.com/LimeSurvey/LimeSurvey/commit/de63762472630ab797db4ae65899a53c165eef70 (I fact : any email text not only this one …) |
 |
This is a feature missing for a lomng time. Woul be great to see this in a future Limesurvey 4.x version (added at core, not as plugin). |
|
|
Plugin included in core … Else : more and more issue and more issue and less maintainable system … |
|
|
Plugin included at the core would be fine, if it is enabled by default and the user has no limitations using it. |
- Anonymous
