Stream: IG creation
Topic: image related errors
Craig Newman (May 26 2020 at 17:25):
When I add images to MD files in my IG, I get an "image source cannot be resolved" error even though the images are incorporated just fine into the appropriate pages. Even thought the error does say ".JPG", I've tried with both upper and lower case file types and get the same error. My file looks like this:


If it makes a difference, I am using FHIR Shorthand. Any idea what the issue is? Thanks
Jose Costa Teixeira (May 26 2020 at 17:32):
Is this available somewhere?
Craig Newman (May 26 2020 at 19:19):
A slightly older version of the error (but still fundamentally the same) is available on the QA Report page for https://build.fhir.org/ig/HL7/fhir-birthdefectsreporting-ig/index.html. Is that what you want to see?
Jose Costa Teixeira (May 26 2020 at 19:52):
i see nothing in this qa report about images
Jose Costa Teixeira (May 26 2020 at 19:53):
what I wanted to see is the source repo - is the thing you are working on available in a repo somewhere?
Jose Costa Teixeira (May 26 2020 at 20:05):
I just tested the markdown with images and it works fine. Even with spaces in the filename
Jose Costa Teixeira (May 26 2020 at 20:05):
the only way that I can get this error is if I put the image not in the images folder but in the same folder as the .md
Jose Costa Teixeira (May 26 2020 at 20:08):
@Craig Newman I do not know if this is the only way to get it working, but if you put images in the ..\images folder this should work.
Jose Costa Teixeira (May 26 2020 at 20:08):
Not sure if that is how sushi handles it or if I am missing something @Chris Moesel ?
Chris Moesel (May 26 2020 at 21:21):
Based on a past conversation with @Lloyd McKenzie, images must go in the images
folder. That is the only folder that the publisher will blindly copy files from. Files in pages
and pagecontent
must be processed by Jekyll to get copied over to the final IG, and binary files are not processed by Jekyll. See this sub-thread for the original conversation where I learned this: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Template.20changes/near/186949666
Jose Costa Teixeira (May 26 2020 at 21:34):
that checks. so @Craig Newman you must ensure your image files are in the images folder, not in the same folder as the .md
Frank Oemig (May 27 2020 at 07:07):
Some ideas:
Spaces in filenames?
Filename is case sensitive!
Leading './'?
All files from images and subdirs are copied
Craig Newman (May 27 2020 at 12:23):
The files are in the image folder in the github repo
https://github.com/HL7/fhir-birthdefectsreporting-ig/tree/master/fsh/ig-data/input/images
This is a version that's older than the earlier screen shot I provided, but the file mentioned in the error for the CI build version is in the images folder
error The image source './expanded core content organization.jpg' cannot be resolved
Grahame Grieve (May 27 2020 at 12:26):
what's with the spaces?
Craig Newman (May 27 2020 at 12:34):
I tried it without spaces and still see the same errors
Grahame Grieve (May 27 2020 at 12:46):
well, use it without spaces, and I'll look at it tomorrow
Grahame Grieve (May 29 2020 at 05:30):
it's the ./ - what's with that?
Grahame Grieve (May 29 2020 at 05:34):
anyway, fixed next release. if you want to waste 2 characters, the ig publisher will let you do that.
Grahame Grieve (May 29 2020 at 05:34):
btw: The link 'craig.newman@altarum.org' for "HL7 Public Health Work Group" cannot be resolved
- needs a mailto:
Craig Newman (May 29 2020 at 11:43):
I think I copied the format from the FSH Tutorial. Not sure why it worked there but not here. Thanks.
Chris Moesel (May 29 2020 at 13:01):
btw: The link 'craig.newman@altarum.org' for "HL7 Public Health Work Group" cannot be resolved - needs a mailto:
I think that's a long-time problem w/ the templates. They try to convert the email from the IG contact into a link, but they do it wrong.
Chris Moesel (May 29 2020 at 13:02):
@Lloyd McKenzie -- I think the email link issue has been reported before. Any updates?
Lloyd McKenzie (May 29 2020 at 13:02):
no :(
Last updated: Apr 12 2022 at 19:14 UTC