Did you activate Jetpack network wide or per-site?
It has to be per-site and configured per-site.
It’s activated per site. As I said, it was working fine until I performed the actions described above.
I noticed that Jetpack was automatically connected for the new subdomain site
THAT implies that it was NETWORK activated, you see. It can’t auto-connect if the plugin is per-site activated, because it’s not turned on. So if it’s turned on automatically, then it was not per-site activated.
It is not automatically connected for any of the other subdomains. Also, I can, by simply looking at the plugins page in network admin, verify that it’s not network activated. Obviously this is some sort of bug. However, I’m not here to argue this point.
I simply want to find a solution for switching back to my old stats. If you can’t help me solve this problem please refrain from spamming this thread with useless pedantry.
How I Solved This Annoying Error
Okay, I managed to fix this problem. The solution is a bit of a hack and doesn’t address the underlying error.
First I renamed the new subdomain to something random. This is to prevent any potential clashes with my next steps.
I then manually changed the siteurl and home entries in the wp_options table, as well as the domain column in the wp_blogs table to the subdomain url to which the stats for my main site had erroneously become linked.
I also changed the line in wp-config.php that starts with define( ‘DOMAIN_CURRENT_SITE’…. I’m not sure if this was necessary but I did it in any case.
I then logged in to the site (The main site was now at subdomain.domain) and re-connected Jetpack.
I then reversed the above steps and changed all entries in the DB and wp-config.php back to what they were. Thankfully Jetpack remained synchronised after changing back, and my stats are showing again.
Unfortunately this is probably not the best solution. Hopefully this bug is taken care of soon.
It is not automatically connected for any of the other subdomains.
Important information. Would’ve helped to have known that.
I wasn’t being pedantic, I was attempting to understand the whole situation based on limited information. Please don’t assume the worst from the volunteers here, it doesn’t inspire anyone to want to help you.
My point, and I had one, was that if the plugin is activated automatically, THAT is what’s wrong. That’s broken WordPress behavior, and since I’ve never seen anyone else mention it with Jetpack (or any other plugin), it requires more information to understand.
I then manually changed the siteurl and home entries in the wp_options table, as well as the domain column in the wp_blogs table to the subdomain url to which the stats for my main site had erroneously become linked.
To what? And for which site? Your MAIN site? Do you mean that the main site had, somehow, picked up the subdomain URL settings in the options table?
I also changed the line in wp-config.php that starts with define( ‘DOMAIN_CURRENT_SITE’…. I’m not sure if this was necessary but I did it in any case.
Again, changed to what? That should point to domain.com and not a subdomain.
You asked:
To what?
The answer, clearly, is:
…to the subdomain url to which the stats for my main site had erroneously become linked.
You asked:
And for which site? Your MAIN site?
Yes, my main site.
You asked:
Do you mean that the main site had, somehow, picked up the subdomain URL settings in the options table?
No.
You asked:
Again, changed to what?
Again, the answer is right there:
…to the subdomain url to which the stats for my main site had erroneously become linked.
I was sure I miss-read that (which is why I asked). That’s … a really insane thing to have to have done. And the end problem was still that the plugin was on for your new subdomain (though logically it shouldn’t have done that at ALL since that’s not how plugins work) and then CHANGED Jetpack (again, shouldn’t be possible!).
This is way bizarre, and I would post here: http://en.support.wordpress.com/contact/?jetpack=needs-service
Did you ever hear back from the Jetpack support team dreamfoundry? I sent them a similar report myself, but I haven’t heard from them.
I never got a satisfactory answer from them. In the end I lost years worth of stats.
Luckily I was also using Google Analytics, which doesn’t just throw away my results without a care in the world.
