MartinCap

Hi @mazedulislamkhan Thanks for the updates.

Could you please let us know when this issue is solved in a future update, as we will not updated the plugin until then.

Many thanks.

@mazedulislamkhan

This one is the closest to our issue.

https://github.com/Yoast/wordpress-seo/issues/9170

Thanks for your reply @mazedulislamkhan. Here are the answers to your questions:

Does this issue occur while using the WordPress v4.9.4 (latest)?
Yes.

Does the issue occur while all the non-Yoast plugins are disabled?
Yes.

Does the issue occur while the default 2017 theme is active?
Untested.

Is there any specific posts or pages where the issue occurs? Or does it occur on all over the site (backend, frontend)?
All over the site. Slow page generations times were shown in our cache performance log. They were typically 50-70% higher than normal.

If you create a staging site on your localhost by copying the production site, does this resolve the slowness issue?
I do not have the capabilities to do this.

It seems many other people are experiencing similar problems.

For me, downgrading to 6.3.1 stopped the issues completely.

@noahkuhn @gooma2

Thanks for confirming it’s not just an issue for us.

We’ve got a state-of-the-art server set-up, so anything that slows things down is a pretty big issue.

Moving back to 6.3.1 has rectified the issue completely.

It seems there are some major flaws in the 7.x updates. It’s disappointing. We’ll definitely be holding off and waiting before updating Yoast plugins in the future.

• This reply was modified 6 years, 8 months ago by MartinCap.

Hi Lamday,

Thanks very much for your reply.

I’ve tried disabling JITM by adding the following code to our functions.php file:

add_filter( 'jetpack_just_in_time_msgs', '__return_false', 99 );

However, the issue persists. On every single page load in WP Admin, we something like the following on our server:

/wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=paged%253D6&_wpnonce=97ab0770dc

Each query of this type takes about a second to execute.

To be clear, this problem only started when we installed Jetpack 5.0, so I think it may be a problem with the plugin?

Many thanks,
Martin

Hi,

We’re still seeing this in our logs every time we load a page in WP-Admin

/wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=&_wpnonce=1dc587fb6e

To be clear, there is no notice showing at all.

Martin

I am getting this same error original PHP error posted by @jaradsecco.

To add to this however, although the mixed content issue is fixed, we are seeing the following request in our logs every single time we load a page in the admin page:

wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=&_wpnonce=cdf8d1cc12

There are no notices showing in the admin area from Jetpack or any other plugins.

Hi, I was using WordPress 4.7.5 at the time of the mixed content problem.

There were no notices in the admin page from Jetpack at that time.

However, we’ve just upgraded to WordPress 4.8 and the Jetpack Admin notice about enabling Vaultpress backups came up after the update.

We closed it and now the mixed content problem is gone.

Thanks for your reply.

Hi Maria, thanks very much for your reply.

How can I remove the SQL_CALC_FOUND_ROWS function from the code above?

Thanks,
Martin

Just to follow up on this for anyone who may be reading and facing similar issues, we seem to have fixed the problem.

The issue (which had been ongoing for some time but for some reason only caused problems sporadically) appears to have been caused by the SQL_CALC_FOUND_ROWS query causing a server-resource bottleneck.

Hundreds of the same SQL_CALC_FOUND_ROWS query would run and cause a big strain on server resources, often rendering WordPress completely unusable. Some times it would last a few minutes, other times it would last hours.

After going through our custom theme’s code, we realised that all of the post pages were using the (inefficient) code below to load recent posts:

<?php $recent = new WP_Query(array('cat' => 11, 'showposts' => 14 )); while($recent->have_posts()) : $recent->the_post();?>

As we did not require pagination in this instance, we simply changed this to include the ‘no_found_rows’ => true part (to prevent the pesky SQL_CALC_FOUND_ROWS query altogether) and it seems to have solved our woes.

So the same code now looks like this:

<?php $recent = new WP_Query(array('no_found_rows' => true, 'cat' => 11, 'showposts' => 14 )); while($recent->have_posts()) : $recent->the_post();?>

I’m by no means an expert when it comes to this stuff but I hope it will be useful to someone if they face similar issues.

Here is where we found the fix: https://thomasgriffin.io/optimize-wordpress-queries/

Hi everyone.

We had exactly the same problem after the Jetpack ‘update’ to 4.2.

It took a while to figure out what was happening but it’s possible that it was a conflict with the W3 Total Cache plugin, because after deactivating W3TC and leaving Jetpack as version 4.2, the login page worked as normal again.

Anyway, I have since reinstalled version 4.1.1 – and won’t update until sure this issue is fixed.

Thanks.

Just want to say thanks to Samuel for posting this.

Our site – https://www.thesportreview.com – was super slow after the 4.3 update – and this fixed it in an instant. Much appreciated.

Martin

Thanks so much for your help with this, Héctor.

I’m going to try and implement this tonight and will let you know how I get on!

Thanks again
Martin

Hi Héctor,

That would be amazing!

The code we currently have in our theme is below.

The additional custom field I want to include is called ‘standfirst’ (which is applied to every post), and I want to put it immediately before the first <span> element.

<?php if (function_exists('wpp_get_mostpopular')) wpp_get_mostpopular("range=daily&cat=11&stats_comments=0&wpp_start=\"\"&wpp_end=\"\"&limit=1&thumbnail_width=140&thumbnail_height=80&stats_views=0&post_html='<li><div class=\"news-feed-image\">{thumb}</div><div class=\"news-feed-item-wrap\" ><a href=\"{url}\" style=\"margin-bottom:15px;\">{text_title}</a><span class=\"homepage-trending-icon\"></span><span class=\"homepage-time\">Trending story</span></div></li>'"); ?>

Thanks so much for your help!