-
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
Layout graphql query data not being passed down to 404 page #3504
Comments
Yeah, looks like we're not passing props into the 404 page here
Could you try adding Check out the contribution instructions for setting up a local dev environment https://www.gatsbyjs.org/docs/how-to-contribute/#contributing |
I ran in to the same issue and adding |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub issues, we have to clean some of the old issues as many of them have already been resolved with the latest updates. Please make sure to update to the latest Gatsby version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
This issue is being closed because there hasn't been any activity for at least 30 days. Feel free to open a new one if you still experience this problem 👍 |
Description
I have a graphql query in my layout, which is passing down data to all pages. The 404 page receives this data in development, but not in production.
Environment
Gatsby version: 1.9.52
Node.js version: 8.9.1
Operating System: Mac OS 10.11.6
Actual result
404 page not receiving layout graphql query data
Expected behavior
404 page should receive layout graphql query data as per other pages
Steps to reproduce
1. Add graphql query to
src/layouts/index.js
2. Add
src/pages/404.js
component using data from this query3. Run
gatsby build
followed bygatsby serve
and navigate to non-existent pageThe text was updated successfully, but these errors were encountered: