Thumbnail location frontmatter

[LexLorijn]

Currently the image property is generated as "[[]]" inside the property. Using only [[]] makes it easier to use the generate thumbnails in the markdown file.

So this would mean changing:
return e.image="[[${l}]]"
to:
return e.image=[[${l}]]
in the main.js Thank you.

[ltctceplrm]

Using quotes around the wikilinks for images is actually the correct way in obsidian, it allows it to see it as an actual link to that image and not just text.

If you want to embed the image in the note then you can use this dataview code:
="![[" + meta(this.image).path + "|350]]"

Or this if you don't need the resizing:
="!"+this.image

The backtick needs to be included and you need the dataview plugin enabled.

[LexLorijn]

You're right! I was just checking when creating a property by pasting for example:

---

title: A New Hope
link: "[[Episode IV]]"
url: https://www.example.com

The property is created and the link works. However, using Media-DB currently the "" stay after the creation of the property file.

checking the MD-file shows this: cover_url: '"[[Resources/Attachments/movie_The Roses (2025).jpg]]"'

I actually don't use dataview for personal reasons. I only use templater the generate HTML which I keep in the .MD files. Before I was using the following to fix the problem:

let localImagePath = getProp(['cover_url', 'image_url', 'Poster', 'poster']);

if (localImagePath) {
localImagePath = localImagePath.replace(/[[/g, '').replace(/]]/g, ''); // Haakjes weg
localImagePath = localImagePath.replace(/["']/g, ''); // Quotes weg
localImagePath = localImagePath.split('|')[0]; // Alias weg
localImagePath = localImagePath.trim(); // Spaties weg
localImagePath = encodeURI(localImagePath); // URL veilig maken
}

Then I found return e.image="[[${l}]]" in the main.js and modified this, which made it obsolete. Could this be some problem on my end?

[ltctceplrm]

It seems like an extra single quote is being added to the double quotes, which means obsidian only sees it as pure text. Could you try with this beta version of the plugin and let me know if it still happens?

main.js

[LexLorijn]

It seems to have been resolved. Everything is working perfectly now. Thank you for your quick response and your effort to maintain a very useful plugin. It is the easiest way for me to make nice looking pages for my media in addition with use of templater. So I will be using it very regularly!