the error is actually in the wp db library functions…  what version of wp?

and what  versions of php and mysql?

seems an issue (lots of similar reports in wp forums) with mysqli library?

Thanks for your help.

Version 4.3.1
PHP version 5.3.26
MySQL version 5.5.31-30.3-log

wow, really old version (5.3.26) of php for a new server…  released 2 1/2 years ago…  just for record, WordPress recommends php version 5.6 or newer…  and php 5.3 reached end of life support in 2014 and is no longer supported…   that said, WordPress still supports it…  but I would highly recommend upgrading to a current supported version…

can you verify if the php was compiled with  mysqli support?

I upgraded to php 5.5.29. Cleared all cookies etc but no change.

Regards

Paul

I am getting the exact same problem.

PHP Fatal error: Call to a member function check_connection() on a non-object in /home/XXXXX/public_html/wp-content/plugins/simple-press/sp-api/sp-api-wpdb.php on line 439

WordPress 4.3.1
PHP Version: 5.5.28
MySQL Database Server Version: 5.6.23-log
MySQL Client Version: mysqlnd 5.0.11-dev

I’ve been getting it since upgrading to 4.3 and then the auto update to 4.3.1

same question again – to both 😉

can you verify that your php library is compile with mysqli included?

Mr Papa said
same question again – to both 😉

can you verify that your php library is compile with mysqli included?

MySQL Extension: Installed|Enabled
MySQLi Extension: Installed|Enabled

Yep.

Thanks for the help but I’m not a programmer and I’m guessing most people on here aren’t so if you can tell me how to find that out it would help heaps. I’m just a Joe Average trying to run my WordPress site.

Regards

Paul

No, this would be an advanced topic… sorry, thought  I  mentioned it, easiest way would be to inquire with your host… if you have access to a phpinfo() display, that could give it to you as well…

still researching this as well since not convinced that is the issue…  but the error is actually occurring in a wp function (their db connection code)…  and its not obvious how its triggered..  only these two reports and I cannot duplicate it… and wp support forum have fair number of similar reports but no common thread…

would it be possible to temp disable all other plugins and see if it still occurs?

Mr Papa said
No, this would be an advanced topic… sorry, thought  I  mentioned it, easiest way would be to inquire with your host… if you have access to a phpinfo() display, that could give it to you as well…

still researching this as well since not convinced that is the issue…  but the error is actually occurring in a wp function (their db connection code)…  and its not obvious how its triggered..  only these two reports and I cannot duplicate it… and wp support forum have fair number of similar reports but no common thread…

would it be possible to temp disable all other plugins and see if it still occurs?

Already tried that and it still happens.

well, tomorrow is weekend and plan to research further… but bit stymied what would be causing this on two sites… and in a wp function no less…

It would be tricky because it’s a live membership site with 35 IT courses running 24/7.

It’s all working but I see the error every time I post and on the bottom of every page. I can only see it in Google Chrome though, not Firefox!

Regards

Paul

can you guys give me a link to where this is happening so I can see where the error is occurring in relation to the rest of the page display? @howtonetwork yours is behind paywall…

It appears the only way this can happen is when the WP global $wpdb does not exist – or correctly is not yet set up…  wouldnt have expected that in the footer, but perhaps something else is doing some sort of ajax response…

can you both verify on forum – integration – page and permalink that you have ‘limit forum display to within wp loop’ set true and ‘allow multiple loading of forum content’ set false?

If so, then try checking ‘force strict use of the WP API’ and see if any difference…

The error for me only appears in my error logs, I guess he has debug set to true in wp-config.php so that might be when he actually sees the error.

Limit forum to display to within WP loop was not checked (is now)
Force the strict use of WP API was not checked (is now)
Allow multiple loading of forum was not checked and is still not checked