-
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
createRedirect broke gatsby-plugin-netlify redirects on 2.32.7 #29779
Comments
I’ll push a fix to the netlify plugin to resolve this today. Thanks for reporting! |
We can confirm the same problem. Thanks for looking into it! |
Following up here, did this fix go out? We're running into the same issue and had to revert to restore our redirects functionality. Upgraded to the latest version of |
This is causing a lot of trouble for us SEO-wise... any updates? |
@ohsnapitscolin What version did you revert back to when you restored your redirects functionality? |
Hi @Corroshop I'm on the same team as @ohsnapitscolin, our issue came when we upgraded from |
Apologies for the delay in fixing this. A fix is now open in #30155 and should be merged and released soon. Cheers! |
Published in |
Any resolution for builds that are not using Gatsby 3.x? There may be a lot and my project is one of them. After adding 3.0.1 of the plugin... |
@fivetwelve This is also backported and published in |
Much appreciated @vladar 🙏 |
Hi,
newly merged PR and published as version 2.32.7 broke gatsby-plugin-netlify redirects implementation. The release (#29742) introduced a new prop
ignoreCase
which is passed to the build output of_redirects
file on gatsby-plugin-netlifygatsby/packages/gatsby-plugin-netlify/src/create-redirects.js
Line 46 in e79fc6b
I am not sure which way is right: introducing a new prop which with default value of false instead of undefined or the way gatsby-plugin-netlify including all the props to the output.
The result now:
_redirects
file outputs ignoreCase=false by default, which in turn is not recognized on Netlify and therefore the redirects are not working.The text was updated successfully, but these errors were encountered: