Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.5.13, plugin conflict
- This topic has 2 replies, 2 voices, and was last updated 4 years, 11 months ago by
Steven Zahm.
-
AuthorPosts
-
03/23/2016 at 7:10 pm #370270
Jeromy
GuestI know it’s a lame ecommerce plugin but an old site is using it successfully and after upgrading their site to the latest WP, eShop and Connections version, the shop breaks, UNLESS I deactivate Connections. Can you help? I get this error:
Call to a member function get() on null in /root/wp-includes/query.php on line 28
03/24/2016 at 3:47 pm #370420Steven Zahm
Keymaster@ Jeromy
If you have narrowed this down to eShop… it is not Connections with the bug, it is eShop. Nothing I can fix from my end. When this error occurs it is normally being caused by an old or poorly coded theme. Here’s a link to a FAQ that discusses this issue as it relates to theme’s. My guess is eShop is using simimilar code which is breaking a core WordPress global variable.
The only solution I can offer, which is not a great one because it involves editing a core WordPress file. Here it is.
Open the
query.php
file found here:../wp-includes/
.Look for this:
function get_query_var( $var, $default = '' ) { global $wp_query; return $wp_query->get( $var, $default ); }
Change it to this:
function get_query_var( $var, $default = '' ) { if ( isset( $GLOBALS['wp_query']->query_vars[ $var ] ) ) { return $GLOBALS['wp_query']->query_vars[ $var ]; } return $default; }
You’ll have to make this change on every WP update as this change will be overwritten by the WP update.
This is the best solution I can give you as Connections requires the
get_query_var()
WordPress function. It is in fact used over 300 times in Connections.Hope that helps!
03/25/2016 at 11:18 am #370521Steven Zahm
Keymaster@ Jeromy
Would you be interested in testing a beta version of Connections which works around this?
Basically what I decided to do was write a wrapper function for the WordPress
get_query_var()
function. What this wrapper function does is check to make sure the is works and if it does, it uses it. If it does not, then it falls back using a method similar to the one I mention in my previous reply. I then updated every instance in Connections whereget_query_var()
is used to use my new wrapper function.This work around solution should “just work”.
-
AuthorPosts
You must be logged in to reply to this topic.