You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lamyseba opened this issue
Jan 24, 2025
· 3 comments
Labels
bugSomething isn't workingIn BETAThe current task is available for testing in the BETA version.ReleasedThe task has been releasedv10.8.0Project: v10.8.0
Note: The normal "insert image" button in media view (+"button on the image) works as expected, giving relative path.

This bug would not be very annoying if the absolute path vscode-frontmatter compute wasn't erroneous. This computation is based on filepath in my filesystem, and not based on the previewPath properties. Hugo translate filepath into an url-friendly version when generating site, and the absolute path calculation that does vs-code-frontmatter is not the same. Using a path based on previewPath (wich is supposed to work) would be less erroneous.
But what I expect and prefer, is to get a relative path as specified in the docs. Output is nicer, and I can pay attention for subdirectories of my post, so that they have url-friendly names that will not be transformed neither by Hugo, nor by vscode-frontmatter.
Device:
OS: Linux
Front Matter CMS Version : 10.7.0
Browser : firefox
Additional context
My content type is in "pageBundle" mode.
The text was updated successfully, but these errors were encountered:
Thanks @lamyseba for opening the issue. It was related to the page bundle. I have added support for this, and you are able to try it out in the latest beta version.
bugSomething isn't workingIn BETAThe current task is available for testing in the BETA version.ReleasedThe task has been releasedv10.8.0Project: v10.8.0
Describe the bug
In media Snippets, the [[&mediaUrl]] placeHolder does not give relative path but an erroneous absolute path).
To Reproduce
This is in my frontmatter.json
When I am editing my post, click on the media button, and then choose the snippets on the desired image, vs-code frontmatter inputs in my post:
I expected it to input
Note: The normal "insert image" button in media view (
+"
button on the image) works as expected, giving relative path.This bug would not be very annoying if the absolute path vscode-frontmatter compute wasn't erroneous. This computation is based on filepath in my filesystem, and not based on the previewPath properties. Hugo translate filepath into an url-friendly version when generating site, and the absolute path calculation that does vs-code-frontmatter is not the same. Using a path based on previewPath (wich is supposed to work) would be less erroneous.
But what I expect and prefer, is to get a relative path as specified in the docs. Output is nicer, and I can pay attention for subdirectories of my post, so that they have url-friendly names that will not be transformed neither by Hugo, nor by vscode-frontmatter.
Device:
Additional context
My content type is in "pageBundle" mode.
The text was updated successfully, but these errors were encountered: