WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility?

  • dogfuriendly-john
    Participant
    1 month, 2 weeks ago #31316

    Hi.

    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.

    Regards,
    JP.

    • This topic was modified 1 month, 2 weeks ago by wpsolr.
    dogfuriendly-john
    Participant
    1 month, 2 weeks ago #31317

    Apologies, that should read…

    …or a potential configuration issue?

    JP.

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31318

    It looks like a plugin conflict indeed.

    I will do further testing of MyListing’s user registration while Yoast is active.

    • This reply was modified 1 month, 2 weeks ago by wpsolr.
    wpsolr
    Keymaster
    1 month, 2 weeks ago #31322

    I could signup as a user on MyListing with WPSOLR and Yoast activated. No visible errors in logs.

    dogfuriendly-john
    Participant
    1 month, 2 weeks 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.

    Regards,
    John Parker.

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31327

    MyListing (2.9.4), Yoast SEO Premium / Yoast SEO (19.8)

    Did you activate the WPSOLR’s Yoast extension also?

    dogfuriendly-john
    Participant
    1 month, 2 weeks 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
    Stack trace:
    #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: 176.25.142.233, 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”

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31329

    And without Yoast PRO?

    dogfuriendly-john
    Participant
    1 month, 2 weeks 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.

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31331

    Thanks. I’ll make some tests with Yoast Pro.

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31332

    I can see some error in logs now, when Yoast Premium is active. I will investigate.

    It does not prevent me from working though. Can you confirm that?

    dogfuriendly-john
    Participant
    1 month, 2 weeks 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 6.0.2.

    dogfuriendly-john
    Participant
    1 month, 2 weeks 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.

    wpsolr
    Keymaster
    1 month, 2 weeks ago #31339

    I’ve identified the potential problem.
    I’ll send you a fix ASAP to test on your environment.

    dogfuriendly-john
    Participant
    1 month, 2 weeks ago #31340

    That’s great.

    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.
    Regards,
    John Parker.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic.