Will it work with WooCommerce Memberships?

Hi @taco100

Will it work good with WooCommerce Memberships add on?
I couldn’t really try out this plugin called WooCommerce Memberships, since it is a paid one, but we don’t have an integration for memberships.

Nextend Social Login registers the users the same way as WordPress does, so I assume there will be no memberships associated with the accounts that register with the providers of Nextend Social Login.
But if it works similarly like other membership plugins, then logged in users can usually subscribe to the memberships. So in theory once the user registers with Nextend Social Login, the person should subscribe to your memberships manually.
Anyway feel free to give it a try.

Will it work well at a Hebrew RTL website?
The text direction doesn’t have any affect on the social login functionality so it will work fine on both RTL and LTR sites.

But if you mean the language of the labels of the social buttons then, we have options to change the Label of the social buttons in each provider: https://nextendweb.com/nextend-social-login-docs/buttons/

Best regards,
Laszlo.

Thanks Laszlo for your awesome reply.
Regarding Q1 –
The way it’s working in my website is that the user can’t just register himself, but he has to buy a product (we have only one product = it’s the paid membership), and after a successfull payment the plugin:
1. Create a WP user for the client.
2. Attached this user with an active membership.

So – Do you think it can work somehow together with the suggested flow above?
If the system already opened a WP user to this client, will he be able to log in to his user with FB/Google account without using his active WP password?

Regards
Tal

Hi @taco100

In this case the only workaround I can think of is disabling the registration with Nextend Social Login.
In this case the users could connect with social login in 2 ways:
1.) A user logs in to his/her WordPress account and links his social accounts to his existing WordPress account. After the social account is linked, logging in with that social account will automatically log the user in to his associated WordPress account.
2.) If the users tries to connect with a social account, and there is an account already registered on your WordPress site, with that email address then the social account will be automatically linked to the WordPress account.

What you need to know about social registrations is that, by default Nextend Social Login inherits the WordPress default Membership settings. So if WooCommerce Memberships disables that, then it will also disable the registration with Nextend Social Login.

If it doesn’t disable the default registration, then you could go to Nextend Social Login > Global Settings > General tab – https://nextendweb.com/nextend-social-login-docs/global-settings/ – find our Membership setting and set it to disabled. In this way new account registration with social login won’t be enabled, but as I mentioned above they will be able to link social accounts to existing WordPress accounts. So users will be able to login with those social accounts later on.

It sounds very good.

1. I can recommend the user, right after registration, to go and connect his social account in order to log in easier next time.

2. I’ll go ahead and try this out!

I appreciate your kind help so far
Tal

Hi again ??
I’ve created a staging site to implement and test the above.
but – Nextend is stopping me cause the staging site is not HTTPS…
Is there any solution for this issue? (we cannot add SSL to this staging site)
If not – we’ll have to build a temporary sub-domain or something similar, will that be ok?

Hi @taco100

Yes, some of the providers – for example Facebook – only allow the communication with secure sites (SSL). This is why we also give the following notification for users with HTTP:
Facebook allows HTTPS OAuth Redirects only. You must move your site to HTTPS in order to allow login with Facebook.

Just for testing purposes you or your host could try setting up a self-signed certificate for your dev domain as you see here: https://www.viralpatel.net/secure-wordpress-admin-https-self-signed-certificate/

But, yes I would rather suggest developing on a sub-domain with SSL, since self signed certificates may not work in certain cases.

Best regards,
Laszlo.