-
Notifications
You must be signed in to change notification settings - Fork 156
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
VIP Go setup #500
Comments
@jonny-bull welcome to Distributor and great question! Unfortunately I don't have an immediate answer for you, though you might try the WPCOM OAuth2 connections to see if that works while I dig a bit to get you a better answer. Note that 10up is closed for the holidays starting tomorrow through Wednesday, January 1st so it'll likely be early January at best before I'm able to get back to you with an answer. Apologies for the delay, but hopefully you'll have a safe and happy holiday in the meantime... cheers! |
@jonny-bull were you able to try using the WPCOM OAuth2 connections to see if that resolved things for you? |
@jonny-bull were you able to try using the WPCOM OAuth2 connections to see if that resolved things for you? |
Hey @jeffpaul, I believe this is what might have been tripping them up: Lines 110 to 112 in 2e8e077
Distributor\Utils\is_vip_com() is still true for VIP Go sites, but seems only necessary for WPcom VIP Sites.
Could perhaps also check if the Alternatively, I think we've got everybody migrated to VIP Go that is using this plugin, so I could double check on that and this logic could potentially just be removed entirely? |
@WPprodigy thanks for the notes, much appreciated! I'd rather play it cautious and avoid any mistake in a VIP site getting caught here, so the VIP_GO_ENV check you noted make be the best route. |
@WPprodigy any chance you've been able to check to see if everybody using Distributor has been migrated to VIP Go? |
Confirmed! All on VIP Go. |
In discussing the best approach here, the decision was to remove the logic noted in the #500 (comment). |
Describe your question
I've got a WP multisite set up locally with Distributor that works as expected.
When deploying to a VIP Go environment, the sites in my network aren't detected.
Is there any extra setup required to get networked sites to appear as options for pulling and pushing on VIP Go?
The text was updated successfully, but these errors were encountered: