One other think I can think that might be useful, is to be able to define an HTML version template, as well as a plain text version for each email-type contact. That’s probably a bigger update, but would be nice for 0.0.6.
ok. I will add it to my ToDo list. The version for EE2 realy near so I will updates docs when release it.
btw you can download version 0.0.6 (EE1) from attachmen. Now you can used tag {password} in email templates for CP, User, Member register w/o validation.
Actually as I wanted to test this out with sending a HTML mail I just added in :
$email->mailtype = 'html';to the mail sending part in the extension file.
Upon doing that it sent the template as html which was fantastic!
One thing I was trying to do though was to have a weblog entries tag in the template and have that spit out some default data for new users but all I got was the weblog entries tag showing up as the tag and it didn’t render the entry unfortunately.
Would be great if that could be added in. I reckon you could probably just hard-code in the HTML bit couldn’t you and not need an option for it and all people would have to do is place in line-breaks in the template in order to get what they want if they just want a text version?
Alternatively if the weblog entries tag could work and they are using a WYSIWYG editor then that would do the same thing also wouldn’t it?
Best wishes,
Mark
Hey Max,
Great extension, it was exactly what I was looking for! I just ran across the same issue with Mark though, when I try to use weblog entries in the template they weren’t parsed. I would want to use this because all of the content on the site is updated through entries, and I don’t want to allow my client to have access to the templates for when they need to make a change to the email that’s sent.
But fantastic job! Let me know how I can buy a couple of coffees for you!
Would be great if that could be added in. I reckon you could probably just hard-code in the HTML bit couldn’t you and not need an option for it and all people would have to do is place in line-breaks in the template in order to get what they want if they just want a text version?
You could, but I’d guess that it’s bad practice, and that EE uses a different Content-Type when sending out email (text/plain vs text/html) - so anyone who uses a non-html reader (or turns it off) wouldn’t see anything. Ideally you’d want to define both, so you can format them nicely for each type of recipient.
Would be great if that could be added in. I reckon you could probably just hard-code in the HTML bit couldn’t you and not need an option for it and all people would have to do is place in line-breaks in the template in order to get what they want if they just want a text version?You could, but I’d guess that it’s bad practice, and that EE uses a different Content-Type when sending out email (text/plain vs text/html) - so anyone who uses a non-html reader (or turns it off) wouldn’t see anything. Ideally you’d want to define both, so you can format them nicely for each type of recipient.
Yep you’re absolutely right on that. Typed all that too quickly before I actually thought about what I was saying 😉
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.