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.
- This topic has 1 reply, 2 voices, and was last updated 10 years ago by
Steven Zahm.
-
AuthorPosts
-
05/27/2013 at 10:16 pm #261019
Grady Booch
ParticipantI’m integrating the Connections plugin with a site containing a custom taxonomy named, curiously enough “connections”. It’s present as a mechanism for connecting posts to connections from the plugin database
For the most part, the Connections plug in plays well with that custom taxonomy, save for one curious (and repeatable) fringe case. If you attempt to view a custom taxonomy category page using the usual URL that looks something like this:
mumble.com/?connections=moof
the site replies with a fatal error
Fatal error: Call to a member function get() on a non-object in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 226
specifically, it dies upon reaching this line of code
if ( ! $connections->settings->get( 'connections', 'connections_compatibility', 'jquery' ) ) return;
Apparently, $connections at this point in execution is not an object.
Similarly, if you go to the admin panel of the site then Posts -> Connections and then visit the posts associated with a particular custom taxonomy term, which is an URL that looks something like this
mumble.com/management/wp-admin/edit.php?connections=moof
the site replies in a more dramatic fashion
Warning: get_object_vars() expects parameter 1 to be object, null given in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 143
Warning: in_array() expects parameter 2 to be array, null given in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 143
Warning: get_object_vars() expects parameter 1 to be object, null given in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 248
Warning: in_array() expects parameter 2 to be array, null given in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 248
Fatal error: Call to a member function get() on a non-object in /home/content/59/8503459/html/gwizproductions/management/wp-content/plugins/connections/includes/class.scripts.php on line 226
I shut off all other plugins, I installed a fresh version of the core connections plugin, and the results are all the same.
Ergo, I’d conclude that the plugin is not playing nicely with the core WordPress category mechanisms when theres a custom category of the name ‘connections’. I noticed that connections.php declares a global variable named $connections – a common and unadorned name – and so my theory is that this global variable is clashing with something that WordPress is doing for the connections custom taxonomy.
BTW, if I rename my custom category to something benign like “eventconnections” then all is well with the world! (But this is a pain, for I have to unwind some existing code).
Anyway, you might note this a something to watch out for.
05/30/2013 at 12:05 pm #261285Steven Zahm
KeymasterThanks for the report … I’m going to have to dig deeper into this one. On the surface of it; it shouldn’t be possible to conflict with a taxonomy, especially with those URL/s.
-
AuthorPosts
You must be logged in to reply to this topic.