How to remove extra tags from email stationary

Options
I'm working on creating a set of responsive emails, but they haven't been sending correctly. The stationary I've been using had nothing but the message placeholder (no HTML and no styles).



When I put the entire HTML (from <html> to </html>) into the message (not the stationary), what gets sent is an email with 2 sets of <html> <head><body> and closing pairs, which is screwing things up.



And when I try to put my own HTML into the stationary, LO strips them out.



I need a way to turn this off so I can have greater control over what gets sent, especialy needing to have elements/styles in the head to make the responsive emails work.
Tagged:

Comments

  • If it helps I'm using the Zurb Ink responsive email framework for creating these emails.



    Also, here's a screenshot of what actually gets sent.



    image

     
  • Ian,



    If you have your responsive email created outside of LO, the simplest way to set it up would be like this:



    Take all of the styles from your style block and add them to the "styles" section of the stationary. Even though Luminate  adds these rIght below the opening <body> tag (when they shouldn't belong in the <head>)  i've never had trouble with this and it always still renders as it should, even though it's technically invalid markup.



    Keep the rest of your stationery just the way you have it – with nothing but the message placeholder. Then, in the body of your email, copy everything between the opening and closing <body> tags.  Don't add your own <html> or <body> tags as these get added automatically.  Make sure your editing in plain text mode, so that Luminate won't mess with any of your code.



     I agree that it's silly and makes it a pain  that you can't add anything to the head of a stationary (specifically styles and meta tags), but I've yet to run into rendering issues when I put these in the body instead. The other pain is that you aren't able to edit the opening <body> tag (to add styles or classes) but I've always been able to find work around for this as well.



     
  • Derek Martin
    Derek Martin Blackbaud Employee
    Ancient Membership 10 Comments Photogenic Name Dropper
    Try setting SDP EMAIL_INCLUDE_LINKED_STYLESHEETS to FALSE.  If you can't see that SDP, you may need to contact Support.
  • Adding a DocType is also an SDP. You have to have a DocType for some media queries to work on iOS.



    The DocType one and the linked styles as false should really be the standard settings. The stock set up is just plain wrong.

     
  • Derek Martin:

    Try setting SDP EMAIL_INCLUDE_LINKED_STYLESHEETS to FALSE.  If you can't see that SDP, you may need to contact Support.

    Hey Derek, where do I find that setting? Is that Setup > Site Options?
  • Derek Martin
    Derek Martin Blackbaud Employee
    Ancient Membership 10 Comments Photogenic Name Dropper
    Yes. Site Data Parameters (or SDPs for short) are located under Setup -> Site Options.



    There's a drop-down selector that allows you to filter your view of the SDPs (there are hundreds) by group or function.  Both EMAIL_INCLUDE_LINKED_STYLESHEETS and EMAIL_DELIVERY_DOC_TYPE (that Brian mentioned) are under Email. 



    It's almost certain that you won't be able to see these SDPs; some SDPs can be viewed and changed by anyone with Site Admin rights, and some are Support-only. 
  • Derek Martin:

    Yes. Site Data Parameters (or SDPs for short) are located under Setup -> Site Options.



    There's a drop-down selector that allows you to filter your view of the SDPs (there are hundreds) by group or function.  Both EMAIL_INCLUDE_LINKED_STYLESHEETS and EMAIL_DELIVERY_DOC_TYPE (that Brian mentioned) are under Email. 



    It's almost certain that you won't be able to see these SDPs; some SDPs can be viewed and changed by anyone with Site Admin rights, and some are Support-only. 

    Sweet thanks Derek, I'll contact support since I don't have that option. Really looking forward to getting these emails working!
  • Hi, Daniel. Thanks for the clear explanation. What workarounds have you developed for body styles being ignored?

    The other pain is that you aren't able to edit the opening <body> tag (to add styles or classes) but I've always been able to find work around for this as well.



     

    Matt

Categories