Multisite Registration Error

[Diomenas]

Hi,

I have purchased and installed S2Member Pro in my website. I am using WordPress Multi User along with S2Member to setup a multi-user network where my paid members have access to a blog with their membership. I'm not necessarily selling the blog, just giving it along with the other perks to any paid member of the website. I am using Jainrain Engage (RPX) for logging in with various social networks. I had this setup working UNTIL i enabled MultiUser in the site (i did not enable it from the beginning).

Now when a user tries to register, whether it be through the Jainrain connection or manually through the wp-register.php page, they are presented with the page 'wp-login.php?registration=disabled' and the message "User registration is currently not allowed." right above the login box.

I have gone into the database and the user_can-register option under wp_options was set to 0. I changed this to 1 and also added the line 'add_site_settings('user_can_register',1);' to wp-register.php. Even with both of these set, I am still being presented the "User registration is currently not allowed."

I have followed all directions exactly as included with the plugin in order to activate multi-site and S2Member together, I do not understand why it will not allow my users to register. Can anyone offer some assistance with this?

[Cristián Lávaque]

And open registrations are enabled? WP Admin -> s2Member -> General Options -> Open Registration

Could you create a test installation of a multisite network with JainRain without s2Member? Do you have the problem?

[Diomenas]

Yes. Open Registration is enabled in s2Member and s2Member has it forced enabled in the WordPress options. I have not set up a test network but I will. Once I have done this I will respond to let you know the status.

[Cristián Lávaque]

Got it.

[DominicWasserzug]

Did you find a solution Billy?

[craigjb12]

I'm having this problem as well

[craigjb12]

update,

This might not be optimal for everyone, but turning on "Allow sign in based on verifiedEmail match:" in Engage Setup worked for me