-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Customizer: Instagram Authentication does not work #14137
Comments
Same as #12292 but I think it needs to be solved here. |
Should be fixed by r156261-wpcom |
@sirbrillig Unfortunately still getting reports of the Instagram connection being broken in the Customizer's widget area. Three reports in this thread: https://premium-themes.forums.wordpress.com/topic/instagram-widget-not-working-3 Description of issue from a premium-theme seller on WordPress.com:
|
@kathrynwp are you sure the user has clicked "Save and Publish" before they clicked "Authorize"? Otherwise it will just reload the Customizer as they described. It's written in the instructions, but it's horrible UX and I get it wrong quite a lot myself. We have an issue for the customization team to improve it in the customization repo at issue 94. |
Oh wow. :) I bet not, I'll ask. I just tested myself moments ago, and didn't notice that you had to click the Save button before authorizing. When I just retested now and included that step, it worked, so I think you're right and it must be that missing step that's the problem. |
It's super easy to overlook the current instructions. Until we have a new flow, what about putting some of the text in bold and rewording it slightly, like:
|
Steps to reproduce
/customize
URL).What I expected
To be redirected to the Instagram login page. (This is the OAuth behavior that occurs if using the Customizer in wp-admin.)
What happened instead
A blank Calypso page is displayed. In the JavaScript console, the following error appears:
Browser / OS version
Mac OS 10.12.4
Chrome 57.0.2987.133
The text was updated successfully, but these errors were encountered: