[dogfuriendly-john]

1 year, 5 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #31403

Many thanks for the workaround – we’ll start another trial and see if this fixes the issues we’re having. 👍

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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.

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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.

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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.

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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”

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #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.

[dogfuriendly-john]

1 year, 6 months ago in reply to: WPSOLR Pro “mysqli_result object is already closed” / Yoast incompatibility? #31317

Apologies, that should read…

…or a potential configuration issue?

JP.

[dogfuriendly-john]

1 year, 6 months ago in reply to: MyListing extension on staging server and Shield Pro compatibility issues? #31290

Hi.

Thanks for the speedy response – do you have a sense of when the 22.4 release is likely to be? (Are there any beta versions available for test?)

In terms of the error, we’ve heard back from the Shield Pro devs…

It appears to be Shield generating the error, but as you’ve discovered, it’s both plugins together causing the problem. We each have a different, incompatible, version of the PHP monolog library distributed with our plugin. Our plugin throws the error just by the timing of the included library.

We suspect that unfortunately they have chosen a version of the library that is only compatible with PHP 7.2+.

There’s nothing we can do to mitigate this error – except perhaps upgrade our library version. Unfortunately this isn’t practical because the newest version of Monolog is only compatible with PHP > 8.1. We support PHP 7.0+ so we can’t make that switch.

You may want to reach out WPSOLR author and let them know about this error and ask them if they’d consider using an older version of the library.

Is such a downgrade feasible from your perspective, or are the security or functionality issues that would prohibit this?

THanks again.

Regards,
John Parker.

[dogfuriendly-john]

1 year, 7 months ago in reply to: PHP 8.x support #30853

Ahh… cool. That makes more sense.

I’m guessing the person in that other thread had some other issue.

Thanks for the clarification.

Regards,
John Parker.

[dogfuriendly-john]

1 year, 7 months ago in reply to: PHP 8.x support #30848

So, you’re only testing with a version of PHP that’s no longer supported after the 22nd of September?

The fact that PHP 8 has been out for over two years and you’re not testing with it it a little concerning if I’m honest.

Regards,
John Parker.