Mike Fitzpatrick

In case people need the translation, and because the Jetpack team didn’t reply…

“A very heavy plugin that still offered statistics for free. Now the statistics are also paid, so it has become a useless plugin.”

Seems people everywhere agree on this point.

Hi Ajay, thanks for replying, though unfortunately, it doesn’t address my concerns. My site has always been a small business blog, and I’ve always rightly had free access to my statistical data until now. 15 years. My data.

I’m not prepared to now pay $300 every year to access my data, and it’s clear that most others aren’t either. Do you think that I’ll get $300 per year’s value out of seeing how many views I get each day/month/year..? Seriously? It’s great to have stats and I loved that Jetpack provided them, but this new extortionate move to withhold them from us behind a ridiculously large paywall is disgraceful, no other way to describe it.

Please don’t “enhance” anything, just let us access our data as we’ve been doing for decades. As I mentioned, someone at Automattic has gotten ahead of themselves with this egregious pricing structure, but you guys already know that. I just hope that management comes to their senses on this, because this is easily one of the worst software developer/business decisions I’ve encountered and highly unethical in my humble opinion.

Agreed, it’s absolutely outrageous and not aligned with the foundations of WordPress or, I thought, Jetpack. I don’t know what’s happened at Automattic, but it ain’t good.

That’s great, but the problem is you’ve just made this change and it affects millions of users who’ve had free access to their stats for years and expect something as simple as stats to be available for free. I certainly do and I don’t think it’s an unreasonable expectation. I’m a small business, why would I pay $200 A YEAR to see my data? Seriously, who thought this was a good idea? I’m not a Jetpack hater BTW, I’ve been using it for 15 years and like several of the modules a lot, but this is too much guys.

Agreed, I am especially annoyed about this, and it’s our data being withheld from us when we’ve had access to it in my case for the last 15 years!

Thank you, I’ll give that a try and see how it works for me. Appreciate the assistance!

Hi Stef, thanks for getting back to me. I was able to resolve a few hours after posting by synchronising gravatar details everywhere (except here it seems where my old pick still appears), disconnecting and reconnecting Jetpack and stats resynchronised across both platforms. I’m sure this is because I’ve been using Jetpack/Wordpress for so long and changed login details many times across WordPress.com, www.ads-software.com, WP admin, Jetpack app, etc. I’d love to reduce this all down to one login, not sure how to do that. Also don’t want to risk losing WP-admin access!

Hi Dan

Thanks very much for replying here, I didn’t realise I’d posted in the wrong place, my apologies for that. Thanks also for the explanation, this makes sense and I retrospectively corrected all the posts/faqs where I had the issue. I was hoping for a lazy solution but sometimes there isn’t one!

All working correctly, thanks again.

Regards

Mike

Thanks, Amrit, I use Litespeed and Cloudflare, I’ve marked the contact page as uncacheable now, which is fine as it’s a very light page. Does it seem fixed from your end now?

Regards

Mike

Problem solved with 4.0.1,

Thanks guys!

• This reply was modified 1 year, 10 months ago by Mike Fitzpatrick.

Hi, exactly the same thing has happened to my website, lost the logo and site title details in mobile and tablet renders. Likewise, I’ve moved my menu and search buttons and they appear, but not the title/logo!

Any help appreciated!

• This reply was modified 1 year, 10 months ago by Mike Fitzpatrick.

Thanks, qtwrk, will do and thanks for your help so far!

Just to clarify, the rows were deleted, they did not reappear. I meant to say that the REST cache behaviour is the same.

Right, uninstalled the LiteSpeed plugin, and deleted (really deleted) all LiteSpeed. rows in WP_options, reinstalled the plugin, behaviour is the same. Any other ideas?!

My only concern – will I need to re-compress all my thousands of images if I delete all Litespeed data from WP_options..?