-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Contact form not working #45
Comments
Did you found the solution for this?? |
403 means you are not allowed to mutate. You need to check the authorization part of the app on the backend where visitors do not have access to send requests. Check and make sure you token is in editor mode. |
Thanks for the advice, I'm gonna try to fix asap and let you know if it works! Edit: Token is already on editor mode but the error is still there |
So this is an issue with the .env file. Basically, during the development process, the .env file for some reason returns undefined. You can take your token and project id, and production and just put it all in the client.js file without the process.env.React_App_.. When it's time to build and deploy that's when you should put those env variables back into the client for production. Since this is a problem with the .env files a few solutions if this is happening during development are. 1) Make sure the .env file is in your root directory and not in your src directory. 2) make sure within your .env file there is only the token or id without the quotations, commas, etc. just the keys alone. 3)Restart the npm server and if that doesnt work then close vscode and restart again. |
@acej0k3r I was facing the same issue and issue got resolved when i put the token inside client.js file instead of .env. Thanks! |
Messages are not posted to sanity and two errors are shown:
The text was updated successfully, but these errors were encountered: