-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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(socialaccount): Allow account connections page to establish SITE_ID from request #3553
Conversation
Can you show me the full stacktrace of the
with:
|
That would be a simpler fix if it works (I will test)... Here is the backtrace:
|
Yes; there is a 1-line fix that is easier. I'll suggest that instead. |
Thanks. Assuming this also fixes the previous issue, can you include a revert of those changes as well? |
It does not fix the previous issue -- they are separate functions. |
Similar to the fix in #3548 , the subprovider refactoring in 0.55 created the necessity to identity SITE_ID based on the request in get_provider_account, which is used in the Django template for the Account Connections page.
This was the simplest way I could find to resolve the problem and get this page working again. I know next to nothing about Django, so I'm open to feedback. This and the previous PR may indicate a systemic challenge with the subprovider implementation that may require a different refactoring if related issues arise in the future.