I’m seeing the following in the production admin after upgrading Jetpack:
Your home option is set up as http://examplesite.org.uk, but your WordPress.com connection lists it as http://examplesite.dev!
The data listed above is not for my current site. Please disconnect, and then form a new connection to WordPress.com for this site using my current settings.
Ignore the difference. This is just a staging site for the real site referenced above.
That used to be my URL for this site before I changed it. Update the WordPress.com Cloud's data to match my current settings.
Jetpack is clearly confused. Anybody else seen this while using Jetpack on Bedrock managed sites?
Yeah, I’ve been seeing that a lot lately. It’s not a Sage issue, I think it’s something new with Jetpack. I just launched a site yesterday and resetting the connection (to the production URL) sorted it out.
Yes, I know it’s not Sage. it’s Jetpack getting confused by having more than one address for a site. Annoying though as previously it worked fine.
A couple of weeks ago, around the time that they launched the Protect plugin into Jetpack, I started having an issue where Jetpack was locking me out of all my localhost installs.
Anytime I would pull (with DB Migrate Pro) a database down from a staging site, if I didn’t have Jetpack development mode set in wp_config, Jetpack would lock me out of the site.
I wonder if this new behavior is a fix for that?
Yes, so I added:
define( 'JETPACK_DEV_DEBUG', true);
To the environments config for development and stage and it looks like the problem has gone away, thanks!
The few times I’ve installed Jetpack to test something, I would always set that, just so I didn’t have to register/log in.
Yeah I totally missed that one.
All working fine again now.