Except, as I think Mr Papa has said a few times, we just can not replicate this issue. In his case on either a local, test site OR several production sites.
I really need him to chime in on this one but perhaps the next thing to probably check is the stats option settings if there are any. Maybe the issue lies buried in there.
Have either of you guys raised this question with JetPack support by the way?
as I mentioned, jetpack locally runs in development mode so stats is not active… another pain of jetpack…
but on the live sites, stats is running… and there are no options, per se… just not sure how to proceed… we could try loading jetpack on another or our live test sites, but not expecting much difference…
did anyone ever check for anything in the php error log?
Yellow Swordfish said
Have either of you guys raised this question with JetPack support by the way?
Mr. Papa said
did anyone ever check for anything in the php error log?
I have not even considered trying to reach Automattic about this. And nothing in my server error logs shed any light on the subject. I was only offering what I thought was a confirmed conflict.
Sorry, I just have more pressing issues to address right now and can get my my stats—with much more detail—via Google Analytics, or at wordpress.com.
I tried another theme yesterday that didn’t matter. Also went through my stats settings and disabled the smiley, disabled the graph in the admin bar, no change.
As for contacting automattic thats a joke. If they answer it will be a canned response that has nothing to do with the subject question asked.
I know you guys want sp to totally free of glitches. But disabling the stats module before doing any sp admin functions is ok with me.
Thanks for all your help. 
Ed
And only today we had another user with (different) forum admin issues who also uses JetPack and the stats module. Solved the problem (another plugin and jQuery) and all is well. The admin works fine AND the stats module works fine…
I fixed my sites – it was easy. Goodbye Jetpack! 
Google Analytics gives better stats anyway. Using CloudFlare i just add my tracking id to the config and it’s done. Tracks every page on the site including 403 and 404 pages. Added a couple url filters to remove /wp-admin/ and /wp-login.php so theres no tracking of admin login and edited pages etc.
The sites load much faster than before without all that bloat loading.
Regards, Ed
jetpack does have some nice features, but is quite bloated – many times larger than wp itself… glad you were able to get around it…
still stumped why its affecting a few users, but not others….
Mr Papa said
jetpack …is quite bloated
Exactly why I prefer to run JetPack Lite, since it only provides the wp.me shortlinksm and stats. I can live without the stats, but we’re pretty much a slave the the Jetpack after having shared so many of its shortlink which I doubt would work if deactivate.
Hey Jim, I tested the JP shortlinks that i previously shared and they still work after giving JP the boot.
I’m assuming JP must create the shortlink when a post or page is published and is not dependent on JP to keep it alive.
If i need a shortlink to share a post somewhere it’s easy to use tinyurl.com to whip one up quick.
Regards, Ed
FidoSysop said
tested the JP shortlinks that i previously shared and they still work after giving JP the boot…
Sure enough… thanks for helping me confirm that Ed!
good news… still trying to see what could be up with jetpack for a few installs… 🙁
When looking for a shortlinks alternative I found the official bit.ly WordPress plugin. But it changes all your sites canocal links to shortlinks. Don’t think that’s good for seo as Google sees the link and crawls it only to discover it’s a redirect back to itself.
Quickly deactivated before it loused up my seo.
Off topic but thought it was worth mentioning since shortlinks were discussed.
Regards, Ed
Quick heads-up that this is now fixed, following a Jetpack update:
3.4.2
Release Date: April 19th, 2015
- Bug Fix: Javascript errors on wp-admin due to stats display code
https://wordpress.org/plugins/jetpack/changelog/
Oooh! Excellent news. Thanks for letting us know. Hopefully those affected will be subscribed here but they will be offered the JetPack update anyway!