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
Duplicate header and footer after Connect Twitter Account #9439
Comments
Thanks for the issue! We'll take your request into consideration and follow up if we decide to tackle this issue. To our amazing contributors: issues labeled To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss and we will follow up within 3 business days. For full info on how to contribute, please check out our contributors guide. |
Hi @nombrekeff, I tried to replicate but was unsuccesful, I see you're on the dashboard page in the screenshots, did you go there after connecting the account? |
It redirected me automatically, I've noticed it redirects me to Another thing I just notice is It still shows the connect twitter button after connecting. PD: I can replicate it every single time if you need more info, I can also share a video of the process if you want to |
that would be very helpful, thank you @nombrekeff ! |
Sure, here you go: https://ufile.io/9zo4b1ru If you need more info, I will be glad to help |
Thanks @nombrekeff - I took the liberty of downloading it and converting to a GIF so the issue is immediately clear to the contributors |
Oh thanks, I forgot about doing that, my bad! |
Hey, I just realized I'm already connected on DEV with my twitter on another account. Maybe that is causing the issue. |
Description:
I just connected my twitter account to my dev account, after twitter redirected back to dev the header and footer are duplicated, as seen in the screenshots. The dev console showed no errors.
To Reproduce
https://dev.to/settings
Screenshots
Desktop (please complete the following information):
Additional context
I tried disabling extensions, but the issue persisted.
The text was updated successfully, but these errors were encountered: