Jetpack Safe Mode

1. Is it by design in a staging environment that’s under a different domain for Jetpack’s Safe Mode to not send out any publicize subscriptions or social media.

Yes. Staging environments should not come polluting your live data, or disturb the subscribers on your live site.

2. I noticed that when I look at my site stats under the Jetpack area in the testing environment that I see the same stats from my main site. Is that just because it’s a copy and I’m seeing the mirror of the live site?

Yes, exactly.

3. When I pushed my testing site changes up to my main site, I did have to do two things, which I’m guessing is also by design. I had to uncheck the discourage search engines box, as that was set in safe mode. And I also had to disconnect and reconnect Jetpack to make it function correctly. This is all correct right?

That mostly depends on how you push changes from one site to the other, but you may indeed have to disconnect / reconnect in some cases.

4. By making the mirror copy, are my jetpack subscribers also attached now to my mirror site?

No, they remain attached to your live site.

in general, will making any changes in my mirror site for testing purposes, mostly theme related really, affect my Jetpack standing on my live site?

Since you’ve enabled Safe Mode on your staging site, none of the things you do on that site will affect your Jetpack settings on the live site.

Hi Jeremy,

I didn’t want to create a new topic, but I have similar issue. I have a client that had Jetpack installed and connected for various uses (I am not super familiar myself). I used BackupBuddy to migrate a copy of the site to a dev environment (separate hosting) to create an additional separate site (supernus.swc-dev.com).

After creating this additional site, the main site (superiorbulklogistics.com) dashboard displays “Jetpack has been placed into Safe mode because we noticed this is an exact copy of supernus.swc-dev.com.” Which is backwards, it’s acting as if new site is the original, and the original is a copy. I was going through the step-by-step fix/safe mode options, and all the references to the site’s url’s are backwards. Which, I am worried to move forward with any of those options due to the fact that I don’t want to mess up settings/actions of jetpack on the live production site.

Any and all help would be greatly appreciated.

Thanks in advance,
James

@jimbo312 I updated the Jetpack settings on our end. You should be good to go, after one little addition to the dev site. Could you add the following to the site’s wp-config.php file?

define( 'JETPACK_DEV_DEBUG', true);

I hope this helps.

@jeherve Thank you for the quick help. I have added this to the dev site’s wp-config file. And still see the same messaging/error as before.

The “new” dev site (supernus.swc-dev.com) is entirely a separate new site, not just staging environment for site updates to live site (superiorbulklogistics.com). The backed up dev site actually is just a bridge site, so it doesn’t need Jetpack, but the live production site does.

I have attached a screenshot with both site’s Admin Dashboards to depict what I am referencing. Is there any solution for this?

Thanks,
James

It seems that the production site isn’t fully connected to WordPress.com right now. We built the notice so it appears on the right site, but it appears that the production site was disconnected from WordPress.com 2 days ago, and somehow that messed things up a bit.

Could you try to reconnect the production site to WordPress.com right now, and see if it helps? You can do so thanks to the Disconnect link appearing at the bottom of the Jetpack menu, and then reconnect by clicking on the Connect button that will appear on that page.

Once you’ve done that, you can also check that Development Mode is correctly enabled on the dev site by going to the Jetpack menu; you should see a banner mentioning that the site is in a jetpack Development mode at the top.

Let me know how it goes.

Thanks @jeherve! Figured it out and got all the old stats/subscribers back!

Thanks Again