**Describe the bug**
When opening a project, I can't see any documents in the Contents view of the Dashboard.
**To Reproduce**
#### Scenario 1
1. Copy a frontmatter project to a local Git repo folder.
#### Scenario 2
1. Copy a frontmatter project to a local Git repo folder.
2. Start tracking all files.
3. Commit the repo
#### Scenario 3
1. Copy a frontmatter project to a local Git repo folder.
2. Start tracking all files.
3. Commit the repo
4. Push the repo to the remote origin
**Expected behavior**
The contents should be viewable in the Dashboard even if put in a local Git repo.
**Screenshots**



**Desktop (please complete the following information):**
- OS: Windows Server 2019 1809, build 17763,3352
- Browser MS Edge
- Version 107.0.1418.26 (Official build) (64-bit)
[frontmatter.zip](https://github.com/estruyf/vscode-front-matter/files/9939262/frontmatter.zip)
<!-- github-sync-id:1434976149 -->
Hi @DennisL68 thank you for opening this issue, I tried to reproduce this issue on my end, but haven't been able to.
What is the content of your markdown files?
Would you be able to share this sample project with me to see if I can find out what goes wrong?
Hi @DennisL68 thank you for opening this issue, I tried to reproduce this issue on my end, but haven't been able to.
What is the content of your markdown files?
Would you be able to share this sample project with me to see if I can find out what goes wrong?
<!-- github-comment-id:1303134626 -->
It is a clean Git repo that only contains the frontmatter project and an initial readme created by GitLab.
I'll upload it later today.
It is a clean Git repo that only contains the frontmatter project and an initial readme created by GitLab.
I'll upload it later today.
<!-- github-comment-id:1303249929 -->
Ok, it has to do with the project name and the folder name being the same frontmatter. Will check what we can do about this.
Ok, it has to do with the project name and the folder name being the same `frontmatter`. Will check what we can do about this.
<!-- github-comment-id:1303669244 -->
Ok, tested with v8.2.3401005 and that works but...
The parent of the parent can't be labeled Frontmatter either.
.../expand/Frontmatter/ - ok .../Frontmatter/expand/ - bad
Ok, tested with `v8.2.3401005` and that works but...
The parent of the parent can't be labeled `Frontmatter` either.
`.../expand/Frontmatter/` - ok
`.../Frontmatter/expand/` - bad
<!-- github-comment-id:1305301191 -->
Could you provide more details about the paths? What did you configure in the frontMatter.content.pageFolders setting?
Could you provide more details about the paths? What did you configure in the `frontMatter.content.pageFolders` setting?
<!-- github-comment-id:1305320443 -->
Then rename the "top" frontmatter to something else to make it work again...
You can use the same zip-file provided as example.
Just make sure to use `Extract to Frontmatter` to generate one extra level.
~~~
\---frontmatter
\---frontmatter
+---.frontmatter
| \---content
\---.vscode
~~~
Then rename the "top" `frontmatter` to something else to make it work again...
<!-- github-comment-id:1305337063 -->
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
When opening a project, I can't see any documents in the Contents view of the Dashboard.
To Reproduce
Scenario 1
Scenario 2
Scenario 3
Expected behavior
The contents should be viewable in the Dashboard even if put in a local Git repo.
Screenshots

Desktop (please complete the following information):
frontmatter.zip
Hi @DennisL68 thank you for opening this issue, I tried to reproduce this issue on my end, but haven't been able to.
What is the content of your markdown files?
Would you be able to share this sample project with me to see if I can find out what goes wrong?
It is a clean Git repo that only contains the frontmatter project and an initial readme created by GitLab.
I'll upload it later today.
I've updated the original entry with an attachment of the local repo of mine.
Ok, it has to do with the project name and the folder name being the same
frontmatter. Will check what we can do about this.Ok, that's for me trying to be structured ;)
But glad it's nothing to do with Git :)
A fix for this is available in the beta version, feel free to give it a try.
Ok, tested with
v8.2.3401005and that works but...The parent of the parent can't be labeled
Frontmattereither..../expand/Frontmatter/- ok.../Frontmatter/expand/- badCould you provide more details about the paths? What did you configure in the
frontMatter.content.pageFolderssetting?You can use the same zip-file provided as example.
Just make sure to use
Extract to Frontmatterto generate one extra level.Then rename the "top"
frontmatterto something else to make it work again...Update coming up