Hi All,
I have a radEditor that is being used as email template creator for email blasting. User can select image they want to put on their template.
Now the issue is email received does not display any images added to the template.
I have already added <telerik:RadEditor ContentFilters="MakeUrlsAbsolute,FixEnclosingP" ...
but to no avail. Still cant show images.
Thanks in advance,
Ryan
5 Answers, 1 is accepted
Hello Ryan,
I hope you are doing well.
What mail client do you use and what is the exported img src value from the editor that is loaded in it? If the path points to a not HTTP/HTTPS resource the mail client will be unable to read it.
Can you please provide the generated markup from RadEditor to examine it on my side?
Please also check the content form unsupported by Outlook HTML elements/attributes at https://www.outlook-apps.com/html-ignored-by-outlook/.
You may also want to turn on the ConvertInlineStylesToAttributes filter which converts XHTML compliant inline style attributes to Email compliant element attributes. For more information check here https://demos.telerik.com/aspnet-ajax/editor/examples/builtincontentfilters/defaultcs.aspx.
Regards,
Rumen
Progress Telerik
Hi Rumen,
Can you tell me how to generate markup so that will be able to provide you.
Thanks for your help,
Ryan
Hi Ryan,
There are three ways to obtain the generated markup from RadEditor:
- Press the Html button and you will find the HTML content that will be sent to the server/database OR
- Obtain the content through the RadEditor1.Content property on the server-side OR
- If the content is saved to database or some file, get it from there.
You should also see what content is supplied to the email client and what content does the email client support for img src source. For example if the image is provided as base64 stream, the email client might now support it. Another reason could be the src to point to unexisting or unaccessible location for example to point to a local hard drive but not an Internet server.
Regards,
Rumen
Progress Telerik
Hi Rumen,
I have been busy for a while. This is test sample saved from DB.
<
p
><
img
alt
=
""
src
=
"https://portaltpa.com/Portal/images/adminLogo.gif"
></
p
><
p
> </
p
><
p
>Test with Image</
p
>
Inspecting Email from Gmail -> it becomes:
<
p
><
img
alt
=
""
src
=
"https://ci6.googleusercontent.com/proxy/p-W00BONOzvS6OyChEN-NzwYfPTk-gBeaL4lBt8nHOWAgBejJta1wQlQHyDmsIlzjg1AULEV0FtfLfJmYK14l_E-=s0-d-e1-ft#https://portaltpa.com/Portal/images/adminLogo.gif"
class
=
"CToWUd"
></
p
>
It will show the image. Seems like Gmail is adding something.
Any suggestion on how to fix the issue?
Thanks!
Ryan
Hi Ryan,
I hope you are well!
Since the problem is not directly related to RadEditor, I looked at Google for the reported behavior and found the following discussion on the topic:
https://support.google.com/mail/forum/AAAAK7un8RU8LIu1ORmO0Y/?hl=ca
Ok, a final update with this. It turns out, for me anyway, that the problem is with Virgin Media's version of gmail rather than gmail as a whole. So not as big a problem as I'd imagined for clients, but still pretty poor service by them.
.......
I had a similar issue for our customers. I knocked together a quick script(https://gist.github.com/ritwikSOP/5d1be5e2a09f0c65fa6b) to pull the same url 100 times and check the performance, and I get a mix of 404s and 500s from the Google image proxy for Gmail. In fact, I only had about 78% of those requests returning 200s which is pretty appalling for something they've rolled out to everyone. Surely 100 sequential request for the same image should have a better success rate?
A blog pos on the issue: https://blog.filippo.io/how-the-new-gmail-image-proxy-works-and-what-this-means-for-you/.
A SO discussion on it: Gmail's new image caching is breaking image links in newsletter:
THE SOLUTION
Following is the only way to force GoogleImageProxy to fetch your images
- Rename your images to something else with png, jpg or gif extensions only.
- Don't use any kind of query string in your image url like
?t=34343
- your image must include png, jpg or gif as an extension.
- your image url must be mapped onto your image directly.
- If you need to use some proxy url for your protected images then your response must include the proper header like
Content-Type: image/jpeg
- File extension and content-type header must match
- Status-code must be 200 instead of 403, 500 etc
I hope the above information will help you resolve the problem. Please share your experience here at the forum when you solved it out.
Stay Safe!
Regards,
Rumen
Progress Telerik
Our thoughts here at Progress are with those affected by the outbreak.