New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ContentDoc with path does not find content #1142
Comments
I think what you want to do is to use to show the posts in the |
I see the same behavior with |
So what is the actual fix for this, still not getting it |
Use |
The error could also appear if you accidentally place the 'content' under another directory :) - not the root directory. If you have done it and the fixed it you should clear your cache in order to have it working :) |
Still getting this error |
Hello @Foddie2 |
I'm seeing this issue when I place the dynamic slug within a nested directory. I.e. Here's a reproduction. |
@CodyBontecou Stackblitz does fail to find EDIT: I played around a bit... |
Hey @nobkd that seems to fix my immediate issue, thank you. |
For me. It's worked in development mode. but not working in production mode |
I am getting the same thing. Turning |
Is this problem being resolved? I have the same problem here |
same here, it works in development mode, but not working in production mode. And I don't want to set |
Oh. I am using "@nuxt/content": "^2.12.1" and still encountering a similar error. |
Environment
Nuxt CLI v3.0.0-rc.3-27550969.a4a3cff 12:03:02
RootDir: /sandbox 12:03:05
Nuxt project info: 12:03:05
Linux
v14.18.1
3.0.0-rc.3-27550969.a4a3cff
yarn@1.22.17
vite
modules
@nuxt/content@2.0.0
,@nuxt/ui@0.1.1-27555426.2ead323
-
Reproduction
https://codesandbox.io/s/nuxt3-contentv2-blog-demo-zokde1
Describe the bug
I want to use ContentDoc to query blog posts under
content/blog
by specifyingpath="/blog"
inContentDoc
component.If I enter
<BASE_URL>/blog/my-article
I always see the fallback code inside the#not-found
slot instead of theindex.md
located at that path.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: