-
Notifications
You must be signed in to change notification settings - Fork 172
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
Log In trows error "Password was correct, but there was an error logging in." #56
Comments
Hi @j-salins. Can you send me your front-end URL and I'll have a look to see what's going on? It sounds like it could be a cors issue. Check and make sure the WPGraphQL CORS plugin is set up correctly |
Are you still seeing this concern or can the issue be closed? |
I've come across this but if I set
in useAuth.ts It allows the login, to me it seems like the const updateViewer doesn't get called to update I'm not too sure if any of this helps?? |
adding |
seems I can't disable cors for use in localhost :/ 'WP GraphQL CORS extension' comes with loginWithCookies |
Hey guys. If ye PM me the WPGraphQL endpoint that ye are having issue's with I can take a look. Sound's like the backend might me missing a few settings. |
I have also problems logging in, sometimes it works, most of the time it doesn't. |
Hello! @scottyzen . It looks like the nuxt app, the client somehow doesn't attach cookies that are asked to set by server. You can try it here https://graceful-gaufre-d45d6e.netlify.app/ |
Got it working after:
Now cookies were sent well and logged in successfully and viever is not empty in the response from the wp |
Is there a way to test it locally without changing the 'SameSite cookie mode' to LAX? |
refreshCart() method returns results from graphql query GqlGetCart where customer object fields are empty and viewer object is null.
Could this be because of incorrect graphql plugin configuration or something else?
When registering new user from nuxt app, it saves data on backend, but throws same error in nuxt.
The text was updated successfully, but these errors were encountered: