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.
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.
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.
12/01/2014 at 4:10 pm #31130812/02/2014 at 9:38 am #311438
My first guess is that you’re using an older version of Link. Can you first try updating Link to the latest version?
If that doesn’t fix it and since “it started recently” that hints to the possibility of a new plugin that was installed or a plugin update that is breaking the hook in WordPress Link hooks into to properly function. Which plugins have you installed or updated recently, try deactivating them to see if the error goes away.12/02/2014 at 12:19 pm #311444
I have been updating the plugins as often as possible. It doesn’t look like link has been updated since July…correct?12/03/2014 at 10:39 am #311607
re: I have been updating the plugins as often as possible. It doesn’t look like link has been updated since July…correct?
Right, the latest version is 2.0.2. Do you have version 2.0.2 installed?
What about my second comment? “since “it started recently” that hints to the possibility of a new plugin that was installed or a plugin update that is breaking the hook in WordPress Link hooks into to properly function. Which plugins have you installed or updated recently, try deactivating them to see if the error goes away.”
Have you temporarily deactivate other plugins to see if the error goes away? My guess is another plugin or maybe even the theme is improperly hooking into the WordPress
wp_loginaction hook.12/03/2014 at 10:53 am #311610
I do have 2.0.2 installed.
I have a feeling it is “Pie Register” that is causing the issue. But, I need to charge people to access the site and Pie Register does a great job.
I had “User Switching” enabled and that caused a few errors too. But deactivating that worked for a few of the errors.12/03/2014 at 11:36 am #311619
Well, I know “User Switching” works perfectly fine with Connections and Link … I use it, a lot, myself.
My vote is “Pie Register” … I’m checking out its code right now …12/03/2014 at 11:50 am #311627
Yep, it’s “Pie Register”. They quite possible broke any plugin that relies on the
Here’s the lines of code that has the bug:
They should either not call the
wp_loginaction hook at all or they should pass the $user object as a second variable like so:
do_action( 'wp_login', $user->user_login, $user );
The only fix right now … You’d have to edit that file, all three instances, to either remove the call or add the second variable. The safest solution is the latter because it might be possible that “Pie Register” may run in a way the core WordPress action
wp_loginis never run and it needs to run for Link and any other plugin that may rely on it.
Hope that helps!12/03/2014 at 11:58 am #311628
Thanks for the troubleshooting. I will reach out to their team and see if they can provide a fix.12/03/2014 at 12:02 pm #311629
If you have a moment, I would truly appreciate a review as they really do make a difference. Many thanks in advance!
You cannot reply to this support topic. Please open your own support topic.