Describe the bug
I have several assets in the /static folder, including sub-folders. When going to the media view, nothing is listed. When I "Create a new folder" that points to the /static folder, the images in that folder show up, but not the ones in the sub-folders. However, when I click the refresh button, they all disappear. Dragging and dropping the folder from the file view only opens up a new editor with that folder as the workspace.
To Reproduce
Steps to reproduce the behavior:
Init frontmatter in an existing project.
Open the frontmatter dashboard
click on the media tab
Screencast
Expected behavior
All media in the project is shown. Media dragged onto the media view should be created in the folder specified by frontMatter.content.publicFolder.
Desktop (please complete the following information):
OS: Fedora Linux 36
Browser Brave
Version 1.40.91 Chromium: 102.0.5005.78 (Official Build) beta (64-bit)
**Describe the bug**
I have several assets in the `/static` folder, including sub-folders. When going to the media view, nothing is listed. When I "Create a new folder" that points to the `/static` folder, the images in that folder show up, but not the ones in the sub-folders. However, when I click the refresh button, they all disappear. Dragging and dropping the folder from the file view only opens up a new editor with that folder as the workspace.
**To Reproduce**
Steps to reproduce the behavior:
1. Init frontmatter in an existing project.
2. Open the frontmatter dashboard
3. click on the media tab
**Screencast**

**Expected behavior**
All media in the project is shown. Media dragged onto the media view should be created in the folder specified by `frontMatter.content.publicFolder`.
**Desktop (please complete the following information):**
- OS: Fedora Linux 36
- Browser Brave
- Version 1.40.91 Chromium: 102.0.5005.78 (Official Build) beta (64-bit)
**Additional context**
The project I am using is at https://github.com/skamansam/skamansam.github.io/tree/svelte (make sure it's the `svelte` branch). All the frontmatter config and data should be there as well.
<!-- github-sync-id:1270183198 -->
I finally found the issue - it was because some config was in frontmatter.json and soem was in the VSCode settings file. Moving all of them to the frontammter.json file fixed the issue. Maybe this can be kept here in case someone else runs into this problem?
I finally found the issue - it was because some config was in frontmatter.json and soem was in the VSCode settings file. Moving all of them to the frontammter.json file fixed the issue. Maybe this can be kept here in case someone else runs into this problem?
<!-- github-comment-id:1154665954 -->
@estruyf Thank you! I've been using Front Matter for about a year and a half and it has been amazing. Thank you for such an awesome product!
@estruyf Thank you! I've been using Front Matter for about a year and a half and it has been amazing. Thank you for such an awesome product!
<!-- github-comment-id:1155304743 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
I have several assets in the
/staticfolder, including sub-folders. When going to the media view, nothing is listed. When I "Create a new folder" that points to the/staticfolder, the images in that folder show up, but not the ones in the sub-folders. However, when I click the refresh button, they all disappear. Dragging and dropping the folder from the file view only opens up a new editor with that folder as the workspace.To Reproduce
Steps to reproduce the behavior:
Screencast

Expected behavior
All media in the project is shown. Media dragged onto the media view should be created in the folder specified by
frontMatter.content.publicFolder.Desktop (please complete the following information):
Additional context
The project I am using is at https://github.com/skamansam/skamansam.github.io/tree/svelte (make sure it's the
sveltebranch). All the frontmatter config and data should be there as well.I finally found the issue - it was because some config was in frontmatter.json and soem was in the VSCode settings file. Moving all of them to the frontammter.json file fixed the issue. Maybe this can be kept here in case someone else runs into this problem?
Thanks @skamansam I spotted another issue when I checked your configuration so thank you for that 👍
@estruyf Thank you! I've been using Front Matter for about a year and a half and it has been amazing. Thank you for such an awesome product!
Thank you @skamansam these kinds of messages make me happy.