WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility?
7 months, 1 week ago #31316
We’re currently evaluating WPSOLR Pro for use with a MyListing based system on a 7-day trial.
However, we’re seeing quite a few errors cropping up in various plugins that all resolve down to…
PHP Fatal error: Uncaught Error: mysqli_result object is already closed in /srv/www/xxx/httpdocs/wp-includes/wp-db.php:1685
For example, when we attempt to register a new user when WPSOLR Pro is enabled this error is thrown by Yoast, although other plugins are also generating this error in other circumstances.
Is this a known issue with the 22.3 release, or a potential confirmation issue?
Thanks in advance.
7 months, 1 week ago #31317
- This topic was modified 7 months, 1 week ago by wpsolr.
Apologies, that should read…
…or a potential configuration issue?
JP.7 months, 1 week ago #31326
Are you using the current versions of MyListing (2.8), Yoast SEO Premium (18.1) / Yoast SEO (19.8) ?
The error doesn’t occur when WPSOLR Pro is deactivated and I can’t see how any of the configuration we’re using could be causing it, as it’s a very “vanilla” set up.
John Parker.7 months, 1 week ago #31328
Just tried that and it’s not made any difference.
Extensions already configured: Geolocation, Yoast SEO, MyListing Theme
2022/10/19 09:28:55 [error] 715#715: *11274 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: mysqli_result object is already closed in /srv/www/staging.abc123.com/httpdocs/wp-includes/wp-db.php:1685
#0 /srv/www/staging.abc123.com/httpdocs/wp-includes/wp-db.php(1685): mysqli_free_result()
#1 /srv/www/staging.abc123.com/httpdocs/wp-includes/wp-db.php(2030): wpdb->flush()
#2 /srv/www/staging.abc123.com/httpdocs/wp-includes/wp-db.php(2756): wpdb->query()
#3 /srv/www/staging.abc123.com/httpdocs/wp-content/plugins/wordpress-seo/src/builders/indexable-author-builder.php(191): wpdb->get_row()
#4 /srv/www/staging.abc123.com/httpdocs/wp-content/plugins/wordpress-seo/src/builders/indexable-author-builder.php(97): Yoast\WP\SEO\Builders\Indexable_Author_Builder->get_object_timestamps()
#5 /srv/www/staging.abc123.com/httpdocs/wp-content/plugins/wordpress-seo/src/builders/indexable-builder.php(349): Yoast\WP\SEO\Builders\Indexable_Author_Builder->build()
#6 /srv/www/staging.abc123.com/httpdocs/wp-” while reading response header from upstream, client: 126.96.36.199, server: staging.dogfuriendly.com, request: “POST /dashboard/ HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php/php8.1-fpm.sock:”, host: “staging.abc123.com”, referrer: “https://staging.abc123.com/dashboard/?register”7 months, 1 week ago #31330
Registration works correctly if the Yoast SEO Premium is disabled. (i.e.: If it’s just running vanilla Yoast SEO.)
If it helps, I can also trigger the “mysqli_result object is already closed” error if I enable Shield Pro and attempt to use the quick search area (in the left hand of the nav bar), although I’ve been running all of our testing with Shield Pro deactivated.
As such, it seems like the problem relates to something WPSOLR Pro is doing to the database connection.
JP.7 months, 1 week ago #31333
We’re getting a fatal error, hence the “There has been a critical error on this website.” white screen in WordPress…
“PHP message: PHP Fatal error: Uncaught Error: mysqli_result object is already closed in /srv/www/staging.abc123.com/httpdocs/wp-includes/wp-db.php:1685
FYI – This is using PHP 8.1, WordPress core 188.8.131.52 months, 1 week ago #31336
FYI – We’re going to cancel our trial before the end of the free 7-day period.
If you can advise on the fatal error issue above, we’ll can start a new trial and take it from there. As it stands there’s clearly some compatibility issues, but if we can address those then the speed improvements we’ve seen with WPSOLR Pro make it a very compelling option.
JP.7 months, 1 week ago #31340
Unfortunately I’m about to leave the office until the 31st, but if you could email it to the email address I registered with here on the forum, I’ll start a new trial and check your fix as soon as I’m back in the office.
Thanks in advance.
You must be logged in to reply to this topic.