Posted: September 26, 2014 at 6:19 pm
|
I just got an email from someone who registered for an event on our new site and she got the following (why is the attention… css… etc showing up?): > /* ————————————- Attention! This CSS file is used for generating the final messages that are sent to the attendees and admins. ————————————- */ /* ————————————- GLOBAL ————————————- */ * { margin:0; padding:0; } * { font-family: “Helvetica Neue”, “Helvetica”, Helvetica, Arial, sans-serif; } img { max-width: 100%; } .collapse { margin:0; padding:0; } body { -webkit-font-smoothing:antialiased; -webkit-text-size-adjust:none; width: 100%!important; height: 100%; } /* ————————————- ELEMENTS ————————————- */ a { color: #2BA6CB;} .btn { text-decoration:none; color: #FFF; background-color: #666; padding:10px 16px; font-weight:bold; margin-right:10px; text-align:center; cursor:pointer; display: inline-block; } p.callout { padding:15px; background-color:#ECF8FF; margin-bottom: 15px; } .callout a { font-weight:bold; color: #2BA6CB; } table.social { /* padding:15px; */ background-color: #ebebeb; } .social .soc-btn { padding: 3px 7px; font-size:12px; margin-bottom:10px; text-decoration:none; color: #FFF;font-weight:bold; display:block; text-align:center; } a.fb { background-color: #3B5998!important; } a.tw { background-color: #1daced!important; } a.gp { background-color: #DB4A39!important; } a.ms { background-color: #000!important; } .sidebar .soc-btn { display:block; width:100%; } /* ————————————- HEADER ————————————- */ table.head-wrap { width: 100%;} .header.container table td.logo { padding: 15px; } .header.container table td.label { padding: 15px; padding-left:0px;} /* ————————————- BODY ————————————- */ table.body-wrap { width: 100%;} /* ————————————- FOOTER ————————————- */ table.footer-wrap { width: 100%; clear:both!important; } .footer-wrap .container td.content p { border-top: 1px solid rgb(215,215,215); padding-top:15px;} .footer-wrap .container td.content p { font-size:10px; font-weight: bold; } /* ————————————- TYPOGRAPHY ————————————- */ h1,h2,h3,h4,h5,h6 { font-family: “HelveticaNeue-Light”, “Helvetica Neue Light”, “Helvetica Neue”, Helvetica, Arial, “Lucida Grande”, sans-serif; line-height: 1.1; margin-bottom:15px; padding-bottom:15px; padding-top:10px; color:#000; } h1 small, h2 small, h3 small, h4 small, h5 small, h6 small { font-size: 60%; color: #6f6f6f; line-height: 0; text-transform: none; } h1 { font-weight:200; font-size: 36px;} h2 { font-weight:200; font-size: 30px;} h3 { font-weight:500; font-size: 24px;} h4 { font-weight:500; font-size: 19px;} h5 { font-weight:900; font-size: 16px;} h6 { font-weight:900; font-size: 14px; text-transform: uppercase; color:#444;} h4.attendee-name { margin: 10px 0; } .collapse { margin:0!important;} p, ul { margin-bottom: 10px; font-weight: normal; font-size:14px; line-height:1.6; } p.lead { font-size:17px; } p.last { margin-bottom:0px;} ul li { margin-left:5px; padding-bottom: 5px; list-style-position: inside; list-style-type: none; } ul.question-list li, ol.datetime-list li { margin-left:10px; padding-bottom: 5px; list-style-position: inside; list-style-type: none; } li.ticket-name em, li.question-item em {padding-left: 15px;} hr { margin: 10px 0; } /* ————————————- SIDEBAR ————————————- */ ul.sidebar { background:#ebebeb; display:block; list-style-type: none; } #ee-message-preview-container ul.sidebar li { display: block; margin:0; padding:10px 16px;} #ee-message-preview-container ul.sidebar li h5 { text-decoration:none; color: #000; padding:10px 0 20px 0; display:block; margin:0; } ul.sidebar li a.last { border-bottom-width:0px;} ul.sidebar li a h1,ul.sidebar li a h2,ul.sidebar li a h3,ul.sidebar li a h4,ul.sidebar li a h5,ul.sidebar li a h6,ul.sidebar li a p { margin-bottom:0!important;} /* ————————————————— RESPONSIVENESS Nuke it from orbit. It’s the only way to be sure. —————————————————— */ /* Set a max-width, and make it display as block so it will automatically stretch to that width, but will also shrink down on a phone or something */ .container { display:block!important; max-width:600px!important; margin:0 auto!important; /* makes it centered */ clear:both!important; } /* This should also be a block element, so that it will fill 100% of the .container */ .content { padding:15px; max-width:600px; margin:0 auto; display:block; } /* Let’s make sure tables in the content area are 100% wide */ .content table { width: 100%; } /* Odds and ends */ .column { width: 300px; float:left; } .column tr td { padding: 15px; } .column-wrap { padding:0!important; margin:0 auto; max-width:600px!important; } .column table { width:100%;} .social .column { width: 280px; min-width: 279px; float:left; } .column-large { width: 550px; margin:0 auto; padding-left: 10px; } /* Be sure to place a .clear element after each set of columns, just to be safe */ .clear { display: block; clear: both; } /* ——————————————- PHONE For clients that support media queries. Nothing fancy. ——————————————– */ @media only screen and (max-width: 600px) { a[class=”btn”] { display:block!important; margin-bottom:10px!important; background-image:none!important; margin-right:0!important;} div[class=”column”] { width: auto!important; float:none!important;} table.social div[class=”column”] { width:auto!important; } } |
Hi, Are you running the latest version of Event Espresso at 4.4.3? — |
|
|
No 4.4.0 |
Hi Jeanie, We recommend running the current software. I’ve reset your support license key so you can update (if you haven’t already done so). We saw this issue back on 4.3 and it was corrected but haven’t seen it recently until this report. Does your organization name have special characters in it? Also, if you are using shared web hosting, please consider using Mandrill to ensure that your emails are delivered to the inbox instead of a spam / junk mail folder: https://eventespresso.com/wiki/postmark-app-mandrill-transactional-email-handling-services/ They have a generous free tier available. — |
|
|
I just updated EE4 and did a test registration and the same code showed up in the email sent. |
|
I created a simple custom message template without any css classes to see if that will help. But now I can’t figure out how to apply the custom message template (make it so it replaces the default “reg pending payment” message). |
Hi, Please give this change a try: http://cl.ly/image/3W2l1P2n2B2U [CO_EMAIL] — |
|
|
Thanks, but sadly that did not work. still have the code at the start of the email. |
|
September 28, 2014 at 10:57 pm In case this is helpful to know: When I do a test send from the admin it does not show up. When I actually register for an event, via the website front end, it shows up in the email auto response. |
|
September 28, 2014 at 11:20 pm Sorry to write more, but I should mention that I just tested actually paying (made a cheap event and paid for it w paypal) and the “payment details” email was fine! The message for “registration pending payment” is the one that had and still has all the code at the beginning. Also, I put the [CO_FORMATTED_EMAIL] back, because all that happened when I used [CO_EMAIL] was it said the message is from “WordPress” instead of the name. |
September 29, 2014 at 11:05 am Thanks for the additional testing. Could you reset the template for this message type? http://cl.ly/image/1H0L2v370v0p Next, please try changing the from field to [CO_EMAIL] http://cl.ly/image/3v091y2o2d3B Then let us know if the CSS still appears. — |
|
|
September 30, 2014 at 12:39 pm I did those things and the css still appears for that one. Can you please tell me how to replace the default email with a custom email? I can’t figure it out and can’t find any documentation. Maybe if I replace the “registration pending payment” email with my own custom one, it won’t have the css. |
September 30, 2014 at 12:43 pm Hi, That shouldn’t be happening unless something is interfering with the templates. Did you setup the Mandrill service? https://eventespresso.com/wiki/postmark-app-mandrill-transactional-email-handling-services/ — |
|
The support post ‘Message template contains weird data’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.