Followers disappeared after recent update

Hi Edee,

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 (I won’t put it here, but it was definitely a development server). It had blog ID 52618076 whereas your site now has ID 63782918.

I have fixed the issue, and you should be able to get your Stats and Subscribers back by going to the Jetpack menu in your dashboard, and disconnecting / reconnecting to WordPress.com.

Ah, okay. That makes sense. I recently got rid of a couple of development sites and, though I’m careful about who is signed in when it all gets connected, it looks like I had an “oops.”

I just checked and it all seems to be working just fine. Thank you so very much for handling/fixing this for me. Truly appreciated.

Please feel free to close this thread.

Uh oh – the stats were there a few days ago, but they’ve disappeared again. Looking in your instructions it says to disconnect then reconnect. Does my client need to do that again? Is it connecting now with her own WordPress.com or with the one on the dev site?

Hi! It looks like your development site once again connected to WordPress.com and carried over the blog_id to the live site. How do you handle your development site and live site? Do you you simply copy over the db from production to live? With Jetpack, you need to be careful when you do that: make sure to disconnect Jetpack on both sites before copying over the db; once the db is copied, then you can reconnect Jetpack.

I also noticed an artifact from your dev site in the live site’s source:

<link rel="icon" href="https://www.forestavenuepress.com.php53-2.dfw1-2.websitetestlink.com/wp-content/uploads/2013/05/forest-favicon.png" type="image/x-icon" />

So, to fix this, disconnect and reconnect again on both sites, and let me know once that’s done. I’ll make sure that stats are correct for the live site then.

Thanks – and no, I don’t copy the entire database over. I’m probably a weirdo but because I don’t want/need everything I only upload theme template files. In fact, in this case, she only hired me to set up a theme template the way it shows in the demo, so I didn’t actually do a dev site for it. I think when you first mentioned it I wasn’t tripped up by that because I typically do use them. At any rate, I never actually connected anything for her, I had her do it with her own logins/pwds. This particular site started out at forestavenuepress.wordpress.com (which might still be live), but it was owned by the client, not me. So when she made the transition from the wp.com to a self-hosted, she contacted support and had them move the subscribers over. I’m wondering how you can send me the info privately so I can see what the dev site is you’re referring to? Ohhhh, wait a second! She had the domain and she had the .com redirecting to that, she actually had a subdomain of sorts set up with that same main domain. I’ll see if that’s still active/available for me to go in and disconnect it (crossing fingers!) but I’m thinking it must be still live if you’re able to see it?

Thanks! I’ll let you know asap!

I tried to log into the production site URL but it is redirecting to the main login. When I just go to the production URL it shows that URL in the address bar but shows the live site. I didn’t set the domain stuff up, someone else did. So I don’t know exactly what he did, but I’m wondering if this is now an issue for their hosting company first, then when that’s straightened out I come back here and let you know it’s been disconnected/reconnected?

Again, thanks so very much. If there were a way to buy you a giant coffee, I’d do it!!

Hi Edee!

To start with, https://forestavenuepress.wordpress.com/ is still live but I don’t see any link to the self-hosted site; there’s no redirection there or anything, so nothing there should be affecting things.

So quick question before we go further: is https://www.forestavenuepress.com.php53-2.dfw1-2.websitetestlink.com the dev site?

Yes, it was. The way it happened was she had forestavenuepress.com and was using that for her wordpress.com (masking). Since it’s her business, she didn’t want it to be down while it was being set up, so she had that longer one set up so the new WordPress template could be configured, then once it was ready, they had their host get rid of the long string and make it forestavenuepress.com straight up. Right now if I try to log into that other one it redirects me straight to the “normal” log in. Regardless, if you just go to that longer one, it is showing the current site as it is now. So they’re the same, only not, if that makes any sense.

Hi Edee,

Thanks for the info. I think the issue is that on the dev site, the Site URL on Settings -> General was set to https://forestavenuepress.com/ . In any case, since the dev URL is still live, is it possible for the host to just kill it? That’d be the easiest way to clarify this and make sure that the problem doesn’t crop up again.