-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
gatsbyjs 404page problem #12279
Comments
Hi @hesamkaveh! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it. If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look. Thanks for using Gatsby! 💜 |
Hi @hesamkaveh , I see that you are using an older version of Gatsby. Can you update all your packages to see if the problem is fixed? If not, please share a reproducible example. Ahh @DSchau beat me to it 😀 |
Hi @DSchau and @krismorf and thank you for reply,
You can see my category.js on github .It works before update, My right 404 error page: http://hesamkaveh.com/404 |
@hesamkaveh would you be able to cross-post that to #12272 Generally, by latest, we mean non-alpha latest (e.g. latest stable). You can use that with |
@hesamkaveh it seems like your most recent error was caused by using a too-recent version of Gatsby. Is there still an error here? |
Yes It is not resolved and errors still here in too-recent version. |
I think You need to adjust your queries that use categories filter to something like
check graphiql for exact syntax - above might not work |
Oh i searched for syntax and i find a syntax that work correctly with new gatsby! My Previous syntax: And my new syntax: thanks:) |
I added src/pages/404.js
It is loading correctly on developing mode, but on build version, css not loading ( see my 404 page )
The text was updated successfully, but these errors were encountered: