AJO Content fragment editable fields for image and url adds an extra space before and after

[NitinSh1]

Hi,

I am working on to create content fragments with editable fields in our emails and observed that when we use any image url and url field in a fragment, AJO add an extra space character before and after the provided value.

This extra space breaks the images and links in some of the email clients.

Does someone know any workaround this issue?

[SatheeskannaK]

@NitinSh1 Do you see this issue happening when you setup emails without using fragments? and Which email clients are you seeing this issue?

[NitinSh1]

Hi @SatheeskannaK ,

Thank you for the reply.

I don't see that issue when we create an email from HTML. And it's the old outlook which is the issue.

[SatheeskannaK]

@NitinSh1 Got it. I've noticed that MSO clients often encounter these types of problems. A possible solution is to attempt adding specific MSO tags to see if that resolves the issue.

https://www.goodemailcode.com/email-enhancements/mso-styles.html

https://www.emailonacid.com/blog/article/email-development/how-to-code-emails-for-outlook-2016/

[NitinSh1]

@SatheeskannaK : Correct. It's specific to MSO where we see this issue.  I am not sure how we can manage the SRC attribute using MSO specific style tags.

[Mayank_Gandhi]

@NitinSh1 we are trying to test this on product side, can you share the detail steps to reproduce I cant see it on my sandbox.

[NitinSh1]

Hi @Mayank_Gandhi ,

I have tried it with few sandboxes and steps to reproduce are

1. Create a visual fragment with editable fields as image, url and text.
2. Add the created fragment in an email delivery or content template
3. Provide the image url
4. Simulate/send the proof and inspect the img tag.

Regards,

Nitin

[NitinSh1]

Hi @Mayank_Gandhi ,

Were you able to reproduce it?

Regards,

Nitin

[Mayank_Gandhi]

@NitinSh1 no, but I talked internally you can log a support case and we will check it further.

[NitinSh1 · Accepted solution]

Hi @Mayank_Gandhi ,

I have already created a support ticket #E-001789600 for the same. Seems like a product bug to me.

Regards,

Nitin

[Mayank_Gandhi]

@NitinSh1 i will have a look into this one

[Sukrity_Wadhwa]

Hi @NitinSh1,

Since there hasn’t been any recent activity on this thread and it is already being addressed with the help of Adobe Support, so, we’ll be closing this question for now.
If you have any related questions or updates to share, please don’t hesitate to request to reopen this thread. We’d be happy to take another look.
Thanks!