Skip to content
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

Coming Soon & Private on AT: Instagram Widget refused to work when site is on Coming Soon/Private mode #43982

Open
retnonindya opened this issue Jul 8, 2020 · 7 comments
Labels
Coming Soon [Platform] Atomic [Pri] Low Simple/Atomic Parity For issues related to feature parity between Simple and Atomic sites. [Size] XL Probably needs to be broken down into multiple smaller issues Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report

Comments

@retnonindya
Copy link

Steps to reproduce

  1. Ensure the website is set to Coming Soon or Private
  2. Open Customizer > Widgets > choose widget area
  3. Add a widget: Instagram
  4. Try to connect Instagram by clicking 'Connect Instagram Account'
  5. A pop-up, asked if we want to continue connecting Instagram with our WordPress.com website appeared
  6. Click 'Continue'
  7. Pop-up disappeared, then a 'Leave site?' prompt appeared

What I expected

Instagram widget able to connect and work properly even when the site is set to Private/Coming Soon...

... or a warning on the Customizer, informing folks that the site is set to Private/Coming Soon, and the widget would not work.

What happened instead

The widget looks okay, giving expectation that the widget should work. The widget didn't work/didn't connect without clear error message, caused frustration and confusion.

Context / Source

#manual-testing #user-report

@eduardozulian
Copy link
Member

Another report on 3183684-zen

@thesacredpath
Copy link

Another here: 3184869-zen

@rinazrina
Copy link

Another one: #3327365-zen

@katiebethbrown
Copy link

Another report: 3371670-zd-woothemes

@serabi
Copy link

serabi commented Nov 12, 2020

Another report: #25593826-hc

@kristenzuck kristenzuck added the User Report This issue was created following a WordPress customer report label Apr 29, 2021
@JoshuaGoode
Copy link

JoshuaGoode commented May 6, 2021

Adding my comment from the related issue specifically for the block instead of the widget: #43131

This will no longer occur with the site uses Coming Soon v2.

This is somewhat expected behavior on Private as it is very restrictive and blocks many Jetpack modules, external requests, and more.

The recommendation is to use Coming Soon v2 powered by the WordPress.com Editing Toolkit plugin.

This might could be closed as won't fix due to the current nature of Private mode on Atomic.

I'd say leave it open as a Simple/Atomic parity issue and to help decide the future of Private mode which can break many things.

@JoshuaGoode JoshuaGoode added Atomic Simple/Atomic Parity For issues related to feature parity between Simple and Atomic sites. Coming Soon labels May 6, 2021
@mmtr mmtr added [Pri] Low [Size] XL Probably needs to be broken down into multiple smaller issues Triaged To be used when issues have been triaged. labels May 21, 2021
@katiebethbrown
Copy link

Another report in 31425815-hc

The site was private. Had them switch to Coming Soon to resolve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Coming Soon [Platform] Atomic [Pri] Low Simple/Atomic Parity For issues related to feature parity between Simple and Atomic sites. [Size] XL Probably needs to be broken down into multiple smaller issues Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report
Projects
None yet
Development

No branches or pull requests

10 participants