Describe the bug
Even though there are images in /static/img, and "frontMatter.content.publicFolder": "static" is specified in frontmatter.json, nothing is showing up in the Media Dashboard.
When I manually specify /static/img/mypic.jpeg for the preview field in the front matter for my blog post the image is shown as I would expect in the Content Preview.
In fact, nothing I do has any impact on the Media Dashboard whatsoever; when I create a new media folder, nothing happens. As far as I can tell, the Media Dashboard is completely broken and non-functional
To Reproduce
Steps to reproduce the behavior:
Install FrontMatter extension
Follow instructions to initialize project
Create a new blog post with some content
Attempt to use the Media Dashboard (I'm sorry, I don't know how to describe it other than that - absolutely nothing in the Media Dashboard works as far as I can tell)
Expected behavior
Dragging & dropping an image in the Media Dashboard window results in anything other than the "No Media to display" message.
Specifying a new/different media folder has any impact on where the Media Dashboard gets media from (no matter what I do, it only ever shows /static/img as the only path for media)
Device:
OS: macOS 15.5
Front Matter CMS Version: 10.8.0
Browser: Safari
Additional context
My project is using Docusaurus 3.8.1. It is a fresh project - no overrides for Docusaurus configs. And, as far as I'm aware, I have no VSCode settings that would conflict with FrontMatter (nothing FrontMatter-related in my VSCode settings).
**Describe the bug**
Even though there are images in `/static/img`, and `"frontMatter.content.publicFolder": "static"` is specified in `frontmatter.json`, nothing is showing up in the Media Dashboard.
When I manually specify `/static/img/mypic.jpeg` for the `preview` field in the front matter for my blog post the image is shown as I would expect in the Content Preview.
In fact, nothing I do has any impact on the Media Dashboard whatsoever; when I create a new media folder, nothing happens. As far as I can tell, the Media Dashboard is completely broken and non-functional
**To Reproduce**
Steps to reproduce the behavior:
1. Install FrontMatter extension
2. Follow instructions to initialize project
3. Create a new blog post with some content
4. Attempt to use the Media Dashboard (I'm sorry, I don't know how to describe it other than that - absolutely nothing in the Media Dashboard works as far as I can tell)
**Expected behavior**
1. Dragging & dropping an image in the Media Dashboard window results in anything other than the "No Media to display" message.
2. Specifying a new/different media folder has any impact on where the Media Dashboard gets media from (no matter what I do, it only ever shows `/static/img` as the only path for media)
**Device:**
- OS: macOS 15.5
- Front Matter CMS Version: 10.8.0
- Browser: Safari
**Additional context**
My project is using [Docusaurus](http://docusaurus.io/) 3.8.1. It is a fresh project - no overrides for Docusaurus configs. And, as far as I'm aware, I have no VSCode settings that would conflict with FrontMatter (nothing FrontMatter-related in my VSCode settings).
<!-- github-sync-id:3186663330 -->
It seems to be fixed in the beta version 🤘🏻
<img width="1624" alt="Image" src="https://github.com/user-attachments/assets/696081f5-c4d6-45d9-8eb9-e7e42e9326ad" />
<!-- github-comment-id:3020300934 -->
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
Even though there are images in
/static/img, and"frontMatter.content.publicFolder": "static"is specified infrontmatter.json, nothing is showing up in the Media Dashboard.When I manually specify
/static/img/mypic.jpegfor thepreviewfield in the front matter for my blog post the image is shown as I would expect in the Content Preview.In fact, nothing I do has any impact on the Media Dashboard whatsoever; when I create a new media folder, nothing happens. As far as I can tell, the Media Dashboard is completely broken and non-functional
To Reproduce
Steps to reproduce the behavior:
Expected behavior
/static/imgas the only path for media)Device:
Additional context
My project is using Docusaurus 3.8.1. It is a fresh project - no overrides for Docusaurus configs. And, as far as I'm aware, I have no VSCode settings that would conflict with FrontMatter (nothing FrontMatter-related in my VSCode settings).
Thanks, something internally changed and got fixed in the latest beta. Can you test that out?
It seems to be fixed in the beta version 🤘🏻
Should I mark this closed now, or when the beta is released?
Version 10.9.0 just got released with this fix included.