Images are imported in the selected folder (img by default) but only the link shows in the journal page
PhilippeKr opened this issue · 10 comments
But maybe I'm doing sopmething wrong in Obsidian, or my parameters are incorrect in the journal, but the end result is that the images are not present, only links (and the link shows for example the image size), but they don't point towards the image uploaded in Foundry.
Hi! Can you provide an example of the markdown you are importing? That will help me reproduce the issue and troubleshoot. Thanks!
I think the Forge uses an abstraction layer in front of S3 to store images. I wonder if that is causing the issue. There are other modules that upload images, so I might be able to do a little research to see if they have to implement anything special for The Forge.
I'm also seeing this problem with just links not the images being displayed. And I'm serving my game locally, not from the cloud/forge/etc.
I'm on v11 of foundry.
I'm seeing the same issue. I'm also on v11 of Foundry, self hosting. The import of my images works fine, but the link to them breaks. I can see in the source of the journal entry the link in Obsidian. For example:
![[Risur.webp]]
This file is in my vault at /Images. In Foundry, I've set my upload path to worlds/zeitgeist-modded/images/gm.
After the import, I see a !null in the journal entry as text. The journal entry source shows ![[Risur.webp]] in plain text. In the interim, I've added this tag to my Obsidian notes:
<img src="worlds/zeitgeist-modded/images/gm/Risur.webp">
I still see the !null, but the image also shows up.
First, this is an excellent module. Thank you so much!
Second, I am hosting on Forge I just tried it and thought maybe I had this issue. However, what was really happening was that my images were not inside the folder that I was importing from my vault. I just moved the images into a subfolder of the folder I was importing and everything worked great. Images were present and imported into my Forge assets library.
I'm looking forward to planning my next session!
Great to hear!
Yes for all reporting this issue, please update to the latest version and make sure your images are within the folder or subfolders you are importing.
This is because browsers don't actually import directories. It sends a list of file paths. So if your image isn't in this list, it can't be imported.
This is expected behavior because it means your browser isn't snooping around your file system grabbing files you haven't told it to grab.
If there's anyone still having this issue after trying these steps to resolve, please let me know so I can troubleshoot further.
@PhilippeKr let me know if you are still having this issue after trying the following:
- Updating to the latest module version.
- Make sure your images are within the folder or subfolders you are importing.