sffandom

Okay, let me rephrase that.

Is there any way to turn this off without hacking the core code, themes, plugins, or otherwise engaging in a resource-wasteful experience?

The best, most satisfying answer would have been equivalent to: “In the Admin dashboard, under such-and-such section, click the CHECK BOX marked ‘disable update notifications’.”

An acceptable alternative would have been equivalent to, “Sorry, no, nothing in the core system. You’ll either have to try a plugin or change some code. Here are a couple of links.”

Marking this as resolved.

Per my original request:

“Is there any way to turn this off without hacking the core code?”

The recommendation you refer to leads to a plugin with THIS warning:

“This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.”

So, all we need is a simple checkbox somewhere in the Admin panel. It would take all of 1 IF statement to control whether the emails are sent out.

Instead, we’re advised to install an out-of-date plugin.

I found another that has been updated more recently. I’m testing it.

Short answer: No way to do it, WordPress core team doesn’t want to give us a way to do it, but they’re saying someone should write a plugin so we can slow our sites down even more.

*SIGH*

And I’m testing a new plugin right now. Not holding out much hope this will work.

WordPress just seems hellbent on ruining itself as a user-friendly system, at least for those of us who don’t have time to dink around with clunky Weebly-style interfaces.

Very informative discussion. Thank you.

Okay. Fair enough.

Thank you for the explanation.

It’s the flaky way Google is working with the REST API.

I’ve installed Site Kit on 2 sites so far. On both sites I got that error message. Waiting about 12 hours allowed the verification process to proceed. [ADDED ON EDIT: You should try again after 15 minutes and 1 hour before going 12 hours.]

Meanwhile, if you decide to RESET the plugin for any reason, it appears you’re stuck back in waiting mode.

This has been one of the most unsatisfying analytics plugin experiences I’ve ever had. Google, of course, blames your server for their problems.

I would not disable anything for at least 12 hours to see if you can get it to work by just waiting it out.

• This reply was modified 4 years, 12 months ago by sffandom.

I just checked a few sites, including a couple that sent errors with the previous version. I have received no warning emails. All the sites I looked at have the current version of Jetpack.

All of our sites are running on PHP 7.2. I know 7.3 has been released but 7.2 is still considered “current”.

So here is an update. I looked in the WP error log file. There was nothing there that hasn’t already been reported here. Jetpack says it’s missing a class.

I activated the DEBUG, LOG, and DISPLAY attributes via “wp-config.php”. I learned that 3 older plugins need to change their code or I will have to replace them but the original error was not triggered. After deactivating the plugins the WordPress Site Health report gave me a bizarre set of contradictory warnings (e.g. “You have X plugins and all are up to date” and “you have Z plugins and Y inactive plugins”). So the Site Health report isn’t reliable.

All the sites use a plugin to automatically install plugin updates. This error has so far only been reported by a small number of them but the error messages are trickling in. I looked at a couple of sites that haven’t reported the error and they look fine. Everything is up-to-date. These sites use the same plugins as the site where I activated the DEBUG warnings above. These plugins don’t use “wp-cron.php” to schedule tasks.

It looks to me like the Jetpack update process encounters an error. Something in the WP-Cron process triggers it. Everything seems to be functioning normally after the installation is completed. I manage too many sites to file support tickets for all of them when I have no other information to share. So I see no reason to file a support ticket for an issue I cannot replicate and which doesn’t seem to be happening with the consistency I feared.

It could be there is a very obscure bug in Jetpack. It could also be that the servers are coming under intermittent heavy loads (rogue crawlers, DNS attacks, high volume traffic – lots of possible causes) and that whatever Jetpack is trying to do misfires because the servers cannot keep up.

In my situation none of these are test blogs. They are all live sites and most of them haven’t had any recent changes made to them other than to automatically install the latest plugin and theme updates. This is a problem with the Jetpack plugin and not with our sites.

Each site only sends the message once. I’ll submit a support ticket on one of the sites.

Here is one (from an email). It’s the same message over and over again. Just a different domain/account each time. Are you suggesting there is additional information to be gained from activating Debug mode? The sites appear to be operating normally. They just send out these bizarre messages.

Error Details
=============
An error of type E_ERROR was caused in line 38 of the file /home/[DOMAIN ACCOUNT]/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php. Error message: Uncaught Error: Class ‘Automattic\Jetpack\Connection\Client’ not found in /home/[DOMAIN ACCOUNT]/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:38
Stack trace:
#0 /home/[DOMAIN ACCOUNT]/public_html/wp-content/plugins/jetpack/sync/class.jetpack-sync-actions.php(191): Jetpack_IXR_Client->query(‘jetpack.syncAct…’, Array)
#1 /home/[DOMAIN ACCOUNT]/public_html/wp-includes/class-wp-hook.php(286): Jetpack_Sync_Actions::send_data(Array, ‘deflate-json-ar…’, 1562121616.5943, ‘sync’, 0.00073790550231934, 0.001906156539917)
#2 /home/[DOMAIN ACCOUNT]/public_html/wp-includes/plugin.php(208): WP_Hook->apply_filters(Array, Array)
#3 /home/[DOMAIN ACCOUNT]/public_html/wp-content/plugins/jetpack/sync/class.jetpack-sync-sender.php(244): apply_filters(‘jetpack_sync_se…’, Array, ‘deflate-json-ar…’, 1562121616.5943, ‘sync’, 0.00073790550231934, 0.001906156539917)
#4 /home/[DOMAIN ACCOUNT]/public_html/wp-content/plugins/jetpack/sync/class.jetpack-sync-sender.php(124): Jetpack_Sync_Sender->do_sync_for_queue(Object(Jetpack

I’m getting these notifications from site after site. Reinstalling isn’t a feasible option. And when I log into the sites there are no reported errors. Just emails coming to me as the technical admin for a lot of sites. This has been going on for over 5 hours as I write this.

• This reply was modified 5 years, 4 months ago by sffandom.

That’s the obvious part. You should try managing 100+ Websites like this. Every extra action whether it be to hover the pointer over the admin menu bar or scroll down to click on a sub-menu item or to wait for AJAX to finish loading a page that could be populated via text-based HTML in half the time, it all adds up to time wasted throughout the day.

THAT is why it’s such an annoying change. Most people won’t care. The people who care are the ones who work on a lot of sites throughout the day.

Pushing everyone to WordPress.Com devalues the tool in subtler ways, but I’m less likely to recommend Jetpack to people who just want to see the data in their dashboards.