Not a major issue, but is it possible to have html in the outgoing emails? I have set the Default Sending Format to MIME. Following is what I've tried and the results I received -
Also if I add {LINKDESCRIPTION} to the email and there happens to be html in the description it turns the html tags to wsncodes. If this is done by design then just let me know so I don't try to fix something that ain't broke! :-)
Fixed in the 5.0 series where the email functions are simplier. Will see what I can do with 4.1 soon (made one change, but that's unlikely to fix it alone).
Only HTML is supposed to be supported, not WSN codes.
Comments on html in email
Forum Regular
Usergroup: Customer
Joined: Apr 03, 2007
Location: NY & PA
Total Topics: 94
Total Comments: 339
Not a major issue, but is it possible to have html in the outgoing emails? I have set the Default Sending Format to MIME. Following is what I've tried and the results I received -
resulted in & # 60;a href=""& # 62;Link Title& # 60; /a & # 62;
resulted in
Also if I add {LINKDESCRIPTION} to the email and there happens to be html in the description it turns the html tags to wsncodes. If this is done by design then just let me know so I don't try to fix something that ain't broke! :-)
**Note - spaces added to show actual text
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Fixed in the 5.0 series where the email functions are simplier. Will see what I can do with 4.1 soon (made one change, but that's unlikely to fix it alone).
Only HTML is supposed to be supported, not WSN codes.
Forum Regular
Usergroup: Customer
Joined: Apr 03, 2007
Location: NY & PA
Total Topics: 94
Total Comments: 339
Great! Thanks for the clarification re: HTML vs WSN codes in email and for letting me know that at least I can look forward to it in the 5.0 series.
In the meantime I know what I need to do to work around it until I can upgrade or you figure out a way to get it to work in 4.1. Thanks again.