Replies: 8 comments
-
Hi! 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! 💜 |
Beta Was this translation helpful? Give feedback.
-
Done. |
Beta Was this translation helpful? Give feedback.
-
@jamelait You're using some very old versions of gatsby and the plugins. Can you upgrade and see if the issue still occurs? |
Beta Was this translation helpful? Give feedback.
-
@ascorbic I have tried but no success. The same problem occurs. I have upgraded the packages in the repo. |
Beta Was this translation helpful? Give feedback.
-
Can someone update the status and remove the "needs reproduction" label? |
Beta Was this translation helpful? Give feedback.
-
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Beta Was this translation helpful? Give feedback.
-
Any ideas? |
Beta Was this translation helpful? Give feedback.
-
This wasn't a bug with Gatsby but something in your code. Once I removed this line it works: https://github.com/jamelait/gatsby-bug-report-29065/blob/main/src/components/header.tsx#L35 If you want to include Snipcart, you can use something like this plugin: https://github.com/danielholdsworth/gatsby-plugin-snipcartv3 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I have a website. On that website I have links made with < Link to={href} >.
In development everything works fine.
In production when I get to the page that contains the links, directly, then click on a link, i quickly see the page I want but then I see a 404 page. What is also very strange is I can hit previous in my browser and see the correct page.
The issue doesn't happen when i go from home > podcast > episode 1.
The issue doesn't happen when i get to the page directly without clicking on an internal link.
Steps to reproduce
Clone https://github.com/jamelait/gatsby-bug-report-29065.git
Install packages with yarn
Run gatsby build
Run gatsby serve
Go to http://localhost:9000/podcast directly (don't go through homepage)
Click on on the first card titled "#0 · Intro · Jam"
Expected result
Show the page "podcast/0-intro-jam." without seeing a 404.
Actual result
The page "podcast/0-intro-jam" quickly shows up then a 404 page is shown.
Environment
System:
OS: Windows 10 10.0.19041
CPU: (8) x64 Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
Binaries:
Node: 10.20.0 - ~\AppData\Local\Temp\yarn--1611948646103-0.9764447001743484\node.CMD
Yarn: 1.22.4 - ~\AppData\Local\Temp\yarn--1611948646103-0.9764447001743484\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Languages:
Python: 3.6.5 - C:\Users\Jamel\AppData\Local\Programs\Python\Python36-32\python.EXE
Browsers:
Chrome: 87.0.4280.141
Edge: Spartan (44.19041.423.0), Chromium (88.0.705.53)
npmPackages:
gatsby: 2.31.0 => 2.31.0
gatsby-image: ^2.1.1 => 2.10.0
gatsby-plugin-mdx: 1.9.0 => 1.9.0
gatsby-plugin-sharp: ^2.1.1 => 2.13.4
gatsby-plugin-typescript: ^2.0.13 => 2.11.0
gatsby-remark-images: ^3.2.1 => 3.10.0
gatsby-source-filesystem: ^2.0.36 => 2.10.0
gatsby-transformer-remark: ^2.3.12 => 2.15.0
gatsby-transformer-sharp: ^2.1.19 => 2.11.0
Beta Was this translation helpful? Give feedback.
All reactions