> The reason is primarily that link URLs
> would be lost

I currently use html2text by Jon Abernathy, which retains links as
footnotes.

> it's possible to
> send an HTML-only email. That's really bad form

100% agree - which is why Cake should default to best practice by
automatically creating a text version (if text template is undefined).
If you're creating a plain text email, you probably don't want/need an
html version.

On May 19, 8:13 pm, brian <[email protected]> wrote:
> On Tue, May 19, 2009 at 12:21 PM, GreyCells <[email protected]> 
> wrote:
>
> > 4. Having to provide text and html bodies for email. (Should be able
> > to create html mail and have Cake write the text version
> > automatically).
>
> I disagree with this. I prefer to create 2 versions of the content and
> echo each variable in its view. The reason is primarily that link URLs
> would be lost if the content is simply run through strip_tags() for
> the plaintext version. What I do is run it through a RegExp to append
> the URL in brackets after the word(s) that would have had the link. I
> also like to add in newlines where certain headers are so everything
> isn't jumbled together. And then there's the question of layouts,
> which will generally be very different.
>
> One big annoyance I see in Email, though, is that it's possible to
> send an HTML-only email. That's really bad form, IMHO. Obviously, this
> isn't a frustration I'm *subjected to* but I don't think the Cake devs
> should be encouraging HTML-only email. My SwiftMailer component (much
> modified from a very old one found at Bakery) defaults to text and
> creates an HTML version in addition to the plaintext if requested.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to