Make 404 page regex configurable #34171
Unanswered
lenzls
asked this question in
Ideas / Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are having the exact same issue as described in #25017.
Scenario
/nonsense
/IT/404
./nonsense
/it/404
, while we want it to stay at/nonsense
.Responsible for the navigation is
gatsby/packages/gatsby/cache-dir/production-app.js
Line 148 in 01eeffe
This clause only skips the navigation for
pagePath
s matching/404
, but not for e.g./IT/404
.Workaround
The suggested solution #25017 (comment) does not work for us. Because for some of our non-404-pages, the navigation is actually desired. Adding catch all rules like
/{language}/*
and/*
will show the 404 page instead of the actual content in these cases. Of course, this breaks our behaviour.Proposal
I'd like to propose (like #25017 (comment)) to make the 404-page regex configurable, so that we can adapt it to our own 404-page path schema.
Beta Was this translation helpful? Give feedback.
All reactions