SOLVED

validation error: <img> escaping malformed URI reference

Go to solution
Highlighted
Anonymous
Not applicable

validation error: <img> escaping malformed URI reference

I'm trying to set up a fully tokenized email template. But I've gotten several validation errors that won't let me save - metatags, some proprietary attributes, etc.

I've sacrificed these to complete my task, but one remains: Validation refuses to accept a tokenized image url. I've tried different html type attribute tags, hoping that would solve it, but no luck. I always get the error: Warning: <img> escaping malformed URI reference

I've tried my urls three different ways:

entire url:

<img src="{{my.Content - EM_Header image}}" alt="xxxx" Title="xxxx" border="0"/>

including http:

<img src="http://go.idt911.com/rs/000-XXX-000/images/{{my.Content - EM_Header image}}" alt="xxxx" Title="xxxx" border="0"/>

replacing characters with unicode:

<img src="http://go.idt911.com/rs/746-PTV-801/images/{{my.Content - EM_Header image}}" alt="IDT911" Title="IDT911" border="0"/>

Any thoughts?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Community Moderator

Re: validation error: <img> escaping malformed URI reference

It's the space in the token name, not the token itself.

replacing characters with unicode:

<img src="http://go.idt911.com/rs/746-PTV-801/images/{{my.Content - EM_Header image}}" alt="IDT911" Title="IDT911" border="0"/>

You definitely wouldn't want to do this!  The token won't be recognized if it doesn't have real curly braces.

View solution in original post

1 REPLY 1
Highlighted
Level 10 - Community Moderator

Re: validation error: <img> escaping malformed URI reference

It's the space in the token name, not the token itself.

replacing characters with unicode:

<img src="http://go.idt911.com/rs/746-PTV-801/images/{{my.Content - EM_Header image}}" alt="IDT911" Title="IDT911" border="0"/>

You definitely wouldn't want to do this!  The token won't be recognized if it doesn't have real curly braces.

View solution in original post