Login multisite issue

So I updated s2member last Friday and am running into an issue with logins.

I’m running a multisite. I’ve been using a sidebar login widget. (though the same problem occurs on the login pages)

Before users could login to any of the sites on the network and it would log them in. Now the login doesn’t work unless a user has been added to that specific site. They get this message “Invalid username for this site”.

I’ve reverted back to the s2member I was using before – v.130221 – and now everything works fine again.

Is there anything that’s changed that would be causing this? Any way I can hack the newer version?

This is unfortunately a very important feature on my site.

Hello Christian,

So if I understood correctly. Before your users were shared amongst several websites and now they’re not?

– Eduan

The users are only on one site of the network and always have been.

The problem is that the login used to work on all the sites but now seems to be site specific.

Before users could login to any of the sites on the network and it would log them in. Now the login doesn’t work unless a user has been added to that specific site. They get this message “Invalid username for this site”.

This is the correct/normal behavior. Users belong to the site they register to, not the network. If it wasn’t behaving like that, then it was not the way WordPress would normally validate sessions in a network, as far as I understand it.

There was a fix related to logins in multisite networks in the v130406 release, maybe your experience is related to that? http://www.s2member.com/changelog/#s2-changes-v130406

This is the thread related to the change, in case it helps identify the relationship to your problem: http://www.s2member.com/forums/topic/deleted-users-can-log-in/#post-46738

I was afraid that might be the case…
Guess I’ll have to come up with a workaround.

Multisites are so much more trouble than they’re worth…

Yeah, I agree with you.

Well, if the previous non-standard behavior was what you actually wanted, you could find what the fix was in that release, and customize your installation to what it was before. If you put an older/customized copy of the related s2Member file in your must-use plugins directory (/wp-content/mu-plugins/), and it’d be used instead of the one in the s2member plugin directory.

I hope that helps!

Just been looking into how to implement this.
Do you know what files were changed for this update? Where should I be looking?

Any help much appreciated.

Christian

Do you know what files were changed for this update? Where should I be looking?

It sounds like you’re talking about the update here: s2Member® Unified Changelog » v130406

s2Member has the newest versions of s2Member’s changes documented on Github. You can find this version’s changes here:

https://github.com/WebSharks/s2Member/tree/130406

The file you’re looking for is /s2member/includes/classes/login-redirects.inc.php.