-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: link to view profile #2280
Conversation
✅ Deploy Preview for regen-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -21,9 +21,9 @@ export const ViewProfileButton = ({ setIsWarningModalOpen }: Props) => { | |||
<OutlinedButton | |||
onClick={() => { | |||
if (isDirtyRef?.current) { | |||
setIsWarningModalOpen('/profile/portfolio'); | |||
setIsWarningModalOpen('/profile'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/profile/portfolio (ecocredits portfolio) is only available to web3 users which is why it was displaying a warning to connect a wallet address
updating to the generic /profile path
@erikalogie @clevinson see testing instructions above |
This is what is happening for me: https://monosnap.com/file/mVEXAqd1SUyNAX944OIfoVqW0zpRPc |
@erikalogie yes this is precisely fixing this issue, looking at your video, you're testing on dev.app.regen.network where the bug is still there, please use the deploy preview link instead: https://deploy-preview-2280--regen-marketplace.netlify.app/ |
Oh duh lol. Ok, yes this looks good! |
This deploy preview doesn't work for me (on Safari) when clicking on email log in:
Logging in with Google works as expected and fixes the bug. My guess is that the issue has something to do with api-staging.regen.network not allowing requests from domains other than dev.app.regen.network? So may be this is a non-issue. But I wanted to flag anyway incase it is indeed a problem that needs resolving. |
Yes doesn't seem related, api-staging.regen.network does allow such requests but I suspect Safari is not sending the CSRF cookie along the requests because the deploy preview is on a different domain, hence the 403 error. While chromium browsers do send it. |
For me I always get redirected to dev.app.regen.network when I try to test this. I don't seem to be able to login with that deploy preview to actually test. |
Could you login with email/passcode instead of google? For google login the redirect url is set on the server side, and on staging it's currently set to dev.app.regen.network but I can update it temporarily to use this deploy preview if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works in Brave
774ce72
to
ce8d73a
Compare
Description
ref: #2248 (comment)
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
How to test
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...