Support Forum

Fatal error: Call to a member function check_connection()

TS TSZ
TSZ
Member
Member since Sep 2013
2 posts
Sep 10, 2015 · 2:56 pm · Edited

I’m not sure why but I keep getting this error on a specific page of WordPress:

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

In the error logs, that error seems to be paired with this one as well:

PHP Warning:  Unknown: Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively in Unknown on line 0

I am running the latest version of WordPress (4.3) and SimplePress (5.5.11).

Not really sure what either of those mean. Any ideas?

3 Answers

New Answer
YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Sep 10, 2015 · 3:17 pm

Both of these are somewhat strange.

The first – check_connection() – is a core method of the WordPress database connection class. So  the ‘page’ you are seeing this error on (1) seems to NOT be connected to the WP code base bit (2) IS connected to the forum error checking code. You will need to explain 1 to me. My only explanation to 2 would be if there is something like a forum widget or template tag also being displayed on the page in question. If not then there no way SP should loading this code. So what is special/different about the page?

The second issue is a real puzzle, Doing a search for help suggests that perhaps you have something that is using the $_SESSION capability of php that is using the same variable name as a global variable used by  a different component. The only session variable ever used in SP is within our captcha plugin. if you are using that you could perhaps try deactivating it to see if that stops the error entry. If not then it might mean another plugin or your WP theme is using a session variable with a conflicting name bit that would mean we would need to know what it is exactly….?

TS TSZ
TSZ
Member
Member since Sep 2013
2 posts
Sep 14, 2015 · 12:53 pm

Thanks for responding! Still not sure exactly what is causing the problem but it’s most likely conflicting with this complicated enterprise software plugin that we’re using and/or the theme we’ve been using.

We decided to work around this by creating a separate WordPress installation and it looks like it’s working fine now.

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Sep 14, 2015 · 2:42 pm

Wouldn’t it be nice to know though… ? 🙂