SOLVED

Re: Design Studio Images Not Appearing In Editor

Go to solution
Anonymous
Not applicable

Design Studio Images Not Appearing In Editor

When I attempt to add an image from our Design Studio library to a template, it does not actually appear in the email editor. Below is a screenshot, and the red box indicates where the photo should be appearing. Instead I get a broken image icon.

When a sample email is sent, the image loads just fine. If I call in the image from an outside URL it will appear in the editor just fine. Does anyone have any experience with this? Candidly, I am new to the email editor and may be missing a setting somewhere. The image name is all one word, and is a .jpg.

I am using the most recent version of Chrome, and I replicated the issue in IE, and on other computers.

marketo image not appearing.png

Tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Re: Design Studio Images Not Appearing In Editor

I was able to make Design Studio images appear in the editor by adding an 's' to the end of http.

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Re: Design Studio Images Not Appearing In Editor

I was able to make Design Studio images appear in the editor by adding an 's' to the end of http.

Anonymous
Not applicable

Re: Design Studio Images Not Appearing In Editor

In my case, I was able to fix this by REMOVING the "s" from http. Wow, what an embarrassing bug for Marketo.

Grégoire_Miche2
Level 10

Re: Design Studio Images Not Appearing In Editor

It is not necessarily a bug, it might simply be linked to information security in your browser. When you connect to Marketo and edit an email, you are in a secure (https) environment. Your bowser might refuse to display images coming from a non secure storage (such as Marketo itself, if you instance is not secured). You can change this in your browser settings.

-Greg

SanfordWhiteman
Level 10 - Community Moderator

Re: Design Studio Images Not Appearing In Editor

Actually what Caroline is relating is the opposite (you don't get a mixed content block if assets are secure, regardless of whether the page is secure; assets are only blocked if the page is secure and assets are insecure).

But it doesn't make any sense anyway -- either the image is accessible over HTTPS or not. More likely, the SSL configuration in the instance is broken, and the https: variant never worked. Have to be there at the moment to inspect.