nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Acknowlegdement Email Styles

Christine Goodwin

In our acknowledgement email from the Advanced Donation Form, any designation with an apostrophe is showing the code instead of the apostrophe. For example instead of Women's Soccer the email displays it as Women's Soccer. Support has shared with us that someone else also had this issue and fixed it by changing a style in the email message. If you are that client, could you share how you were able to get the designation to show correctly in the ack email? Support cannot share the name of the client.

Thank you,

Christine

Find more posts tagged with

Comments

David Wanless

Dear Christine,

I would hope that Support could pass on a message from you to the other organisation.

Best of luck.

Kind regards,

David.

Chris Kastner

Hi Christine,

Changing the style alone won't impact things like the HTML encoding of special characters. I have however seen some BBIS/CRM emails use a HTML attribute on the mergefield tag: htmlencode="true"

Whilst I haven't tested this, you could try adding that to your designation mergefield tag's HTML (or perhaps try it with htmlencode="false" if that doesn't work).

Cheers,

Chris

Christine Goodwin

Hi Chris,

I tried what you suggested with no luck. While working with BBPS, we discovered that our acknowledgement emails from the ADF form and from the event registration forms is stripping out this code from the source code after save:

<!DOCTYPE html>
<html>
<head>
</head>
<body>

In the “regular emails” from BBIS, it's sticking.

Rick Root

Christine Goodwin:
In our acknowledgement email from the Advanced Donation Form, any designation with an apostrophe is showing the code instead of the apostrophe. For example instead of Women's Soccer the email displays it as Women's Soccer. Support has shared with us that someone else also had this issue and fixed it by changing a style in the email message. If you are that client, could you share how you were able to get the designation to show correctly in the ack email? Support cannot share the name of the client.

Thank you,
Christine

So I just made a gift in our system using the ADF, and the acknowledgement email came through just fine with an apostrophe.

Are you certain that the entity code isn't stored in the DESIGNATION table like that, and it just gets properly shown everywhere else?

The merge tag we're using is

Christine Goodwin

We are using the OOB merge field called “Receipt Grid”. Designation is not a merge field option for us.

47182eb70e0504aa51ca3d772bea4d43-origina