WordPress.com connection lists as Staging Site

Hello @kingbrown75,

With Jetpack, your stats information is connected to a unique blog ID. Sometimes, if a site owner was using a development site or a different address when they set up Jetpack, disconnecting may create a new blog ID. When this happens, it may appear that your stats were lost.

That’s what happened on your site; it previously used a different site URL, ngf.079.myftpupload.com.

I have fixed the issue, and you should be able to get your Plan, Stats and Subscribers back by going to the Jetpack menu in your dashboard, and disconnecting/reconnecting to WordPress.com. You can disconnect from WordPress.com thanks to the link at the bottom of the page.

For future references, you may want to check our Safe Mode and Staging Sites modules, as they will help to avoid such issues the next time you might be encountering it ??

Please let me know if the actions I took have fixed the issue, otherwise we’ll take another look at it. Thanks!

Thanks for the release, Is it safe to include a staging site with production in WP.com? This happened in a previous instance and need to update WP plugins in staging since it’s supposed to be common practice. Another issue with staging is plugin updates not working without JetPack connected, I should mention since it a related issue. Or will this cross-contamine WP.com or wp-admin? Looking forword to your reply.

If I am understanding your question properly, you should be able to do this as long as you turn on Staging Mode in Jetpack as outlined here:

https://jetpack.com/support/staging-sites/

Does this work with GoDaddy staging sites? This appears like it may work for the first question but doesn’t address the other which is as important.

Common practices says any updates should be done in staging environments to prevent errors on production. Your plugin updates require JetPack to transfer data so with that said. Staging sites should have WordPress access to update plugins, right? Mentioned earlier, I had an past instace with both staging and production in WP.com (see link). This configuration happened itself and I can’t replicate it after deleting that staging. Is it possible to have production and staging in WP.com to only update plugins. My staging doesn’t allow plugin updates having to update in production before before merging and work on other tasks.

Both questions are related as one is about cross contamination and the other not having a way to connect both to WP.com to prevent cross contamination, if possible.

https://prntscr.com/26kzyv5

• This reply was modified 3 years, 1 month ago by kingbrown75.

Hi @kingbrown75

The staging mode should work with any host; as long as the wp-config.php file isn’t altered or edited whenever you push from production to staging or vice-versa; otherwise, you would have to make any required changes manually.

I’ve seen you’ve mentioned that the staging site doesn’t allow for updates; is that through the WP Admin, or specifically through the WordPress.com dashboard?

Since you’ve deleted that past staging instance, have you gone ahead and installed Jetpack on the new one?

We’d be happy to help if you could clarify more.

Best,