[Steven Zahm]

Thanks for the suggestion!

[Steven Zahm]

@ dominic

I just pushed out the update which includes this fix. You can download it from your purchase history. Apologies for the trouble!

[Steven Zahm]

@ dominic

Hmmm… I just tried it and I was unable to replicate the error. Can you check to see what the Collation is set to in the wpdbprefix_connnections table for the bio and notes columns? It should be utf8mb4_unicode_ci.

Let me know what you find out.

[Steven Zahm]

@ 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 where get_query_var() is used to use my new wrapper function.

This work around solution should “just work”.

[Steven Zahm]

@ Invescontrol

Good to hear my guess was right and resolved the issue.

[Steven Zahm]

@ Cecile

Sound like you had the CSV Import extension installed on the other site. You’ll need to install it on your sandbox site too.

[Steven Zahm]

@ connie

Great to hear!

[Steven Zahm]

@ 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!

[Steven Zahm]

@ Invescontrol

Impossible to say without a link to the page having the issue. If you can share, I’ll take a look.

My best guess, that you might have index.php as part of your permalink structure. If you do, remove it on the WordPress Permalinks Settings admin page. Doing so will also improve the SEO of your site.

[Steven Zahm]

@ Robert

I just visited again. This time in Chrome, Edge, Firefox and IE11. In all browsers the map worked fine.

Perhaps you have an adblocker installed breaking the page or have javascript disabled in your browser???

[Author]

Posts