Hi! By default we are only displaying the buttons in places, where the wp_login_form action was used to create the login form. But you can see here: nextendweb.com/nextend-social-login-docs/documentation/#publish other publishing options, for example you could use a shortcode to display your social login buttons.
@@NEXTEND היי ניסיתי להוסיף את זה אבל זה מראה לי את זה רק ככיתוב (את הקוד הקצר) - האם יכול להיות שזה בגלל שעוד לא חיברתי אף רשת חברתית? התוסף מופעל כמובן :)
Yes, your buttons will only appear once their providers are set up. So you should go trough the steps of at least one of the providers: nextendweb.com/nextend-social-login-docs/documentation/#free-providers and then that should show up!
Anyone could create an application, so we tried to write down the steps as clear as possible. For Google you won't need any special access, but for Facebook you need to register for their developer site: developers.facebook.com/ But this registration is allowed for anyone too.
Hi Dhruv! I assume you actually meant you receive this error when your try to verify the settings on the Settings tab of our Google provider, right? If you do, then this problem is probably caused by probably a firewall ( usually ModSecurity ) that block that requests containing the ".profile" string in the query strings. And since Google returns that in one of the scopes like we mention here: nextendweb.com/nextend-social-login-docs/google-403-and-404-errors/ the firewall would automatically block their requests. To find out if this is the case or not, please get in touch with us over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/ and in the ticket send us a link of the site where you experience the problem.
Hi Vale! As for the 404 error: This problem can occur because of 2 reasons: A.) Either your WordPress default login page (/wp-login.php) page is not available. By default we are trying to handle the OAuth flow over that page, so when we redirect there it will cause a 404 error. If this is the case, you should use our OAuth redirect uri proxy page and Page for register flow settings on the General tab: nextendweb.com/nextend-social-login-docs/global-settings/ B.) Or you have a firewall that blocks the requests of Google, more specifically the ".profile" string in one of its scopes. If this is the case, then you should get in touch with your host and ask them to take at this problem. They probably need to adjust the firewall blocking rules, as we mention here: nextendweb.com/nextend-social-login-docs/google-403-and-404-errors/ If you are not sure which one causes the problem, then please get in touch with us over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/ and we will check this problem on your site. As for the question about the domain name: You need to use the domain name and the URLs of your own site. If you inspect the Getting Started section of the providers in the plugin, we will display that information there.
Hi! If you experience a problem, you can get in touch with us over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/ In your ticket please describe the problem itself and the name of the plugin that was necessary for the problem to occur. Then we will take a look and hopefully we can find a solution for the problem.
Hi Ana! At our Global settings -> General: nextendweb.com/nextend-social-login-docs/global-settings/#pro-settings the "Registration notification sent to" setting defines, whether or not a registration email will be sent to new users. So if you are using the Free version of Nextend Social login (or you haven't modified this in the Pro version), then we use "WordPress default" value. WordPress by default will send a registration email. If in your case that doesn't happens, you will have a plugin or theme modifying this behavior. You could try to switch to a default WordPress theme, then deactivate your other plugins, to see which one creates your issue. There are plugins, like Better Notifications for WP: wordpress.org/plugins/bnfw/ which as far as I know is capable of customizing registration emails. I'm not sure if 2 plugins would define on your website about what should happen with these emails, which one would win, but maybe this plugin would worth a try too.
Hi @jonnathanedberthalim2115 Such problem usually occurs when the page where we try to handle the OAuth flow ( by default it is the /wp-login.php page ) is not accessible, or it redirects to somewhere else. So what I would suggest first is forcing Nextend Social Login to handle its OAuth flow and Register flow over other pages. For this you need to use our "OAuth redirect uri proxy page" and "Page for register flow" settings. Both of these can be found in our Global settings > General tab: nextendweb.com/nextend-social-login-docs/global-settings/ Make sure the selected pages are public that you won't use for anything else, and excluded from all kind of caching. If you still have questions or problems, please get in touch with us directly over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/ and we will check this problem for you.
Hi Samra! Each of our providers have a REST API endpoint where you can post the access token that your requested from the users. If we can find a WordPress user in your site (that is connected to the social media account that you got the access token from) then we will return its user ID. Then you could log the person in to his/her WordPress account, otherwise you should register a new account, log the person in to the registered account and link the social media account to it. Please note that, these needs to be implemented with custom coding. In our documentation you can find more information about our REST API and the format of the access tokens: nextendweb.com/nextend-social-login-docs/nextend-social-login-rest-api/
Hi! In the Free version we don't have an integration for WooCommerce, but if your goal is to display the social buttons in the WooCommerce forms, then with some work you can achieve your goals, since we have multiple options to display the social buttons e.g. shortcode, PHP code or HTML: nextendweb.com/nextend-social-login-docs/usage/ If you would like to have an out of the box support for WooCommerce, then in Nextend Social Login Pro Addon we have an integration for the WooCommerce forms, so the social buttons can automatically appear there, also you could manage them over our backend: nextendweb.com/nextend-social-login-docs/global-settings-woocommerce/ In addition, the Pro Addon gives you an option to send the WooCommerce registration notifications to people who register with Nextend Social Login. ( By default WordPress would send them the WordPress default registration notifications. ) If you still have a question or problem, feel free to get in touch with us over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/
Do you mean you don't want to show the buttons on the /wp-login.php page, or that you don't wan the /wp-login.php page to be used for the login flow (and appearing in the URL on the login buttons)? 1) If you don't want the buttons on the /wp-login.php page You could disable the login buttons from the /wp-login.php by disabing the buttons on the Login Form and Registration Form options at Global settings > Login form: nextendweb.com/nextend-social-login-docs/global-settings-login-form/ Then you could create a new custom page and publish the login buttons there using shortcode: nextendweb.com/nextend-social-login-docs/usage/ and whenever you mention your login page, link to this page instead of the /wp-login.php page. 2) If you don't want the /wp-login.php for the login flow First create an empty page what you will not use for anything else, then at Global Settings -> General tab: nextendweb.com/nextend-social-login-docs/global-settings/ you should use the "OAuth redirect uri proxy page" setting. At your API settings you made, for example at Facebook: nextendweb.com/nextend-social-login-docs/provider-facebook/#configuration you have to change the step 12. setting, to change the URL for the API. This also changes the URL on the social login button. Then create another new page again, and also at the Global settings: nextendweb.com/nextend-social-login-docs/global-settings/ you will find a "Page for register flow" setting. To the new page's description you should add the given shortcode, [nextend_social_login_register_flow]. Then select that page with our settings. If you meant something else, or something don't seem to want to work out please open a support ticket: nextendweb.com/contact-us/nextend-social-login-support/
Great Video.!! When someone logs in with either facebook or gmail, will I be able to see the information of the user that logged in?? Is there a LOG info page? Thanks !
Hi Jaime! We are using the user management and registration/login codes of WordPress, so the social users are handled the same way regular WordPress users are. This means, that you will be able to find their datas in the WordPress left admin menu's "Users" menupoint. We don't have a separate menupoint, like a log about these users, so every available data can be found in this Users menupoint.
Hi, do you get any kind of error message when you try to register? The most common problem is that the registration is disabled at WordPress, and Nextend Social Login by default inherits that. If you don't want to enable the registration with WordPress but only with Nextend Social Login go to Global settings > General: nextendweb.com/nextend-social-login-docs/global-settings/ and at the "Membership" choose Enabled. If this wouldn't make any difference, please open a support ticket: nextendweb.com/contact-us/nextend-social-login-support/
You can see the publishing options here: nextendweb.com/nextend-social-login-docs/documentation/#publish so for example you can use the shortcode to display the login buttons anywhere: nextendweb.com/nextend-social-login-docs/usage/ like this: [nextend_social_login]
Im getting this error when I click "Verify Settings" "Authorization Error Error 401: invalid_client The OAuth client was not found" Despite doing all the above to a T.
Hi, your problem is that the client ID you entered is not correct: nextendweb.com/nextend-social-login-docs/provider-google/#appid Make sure you copy-paste the correct client ID of an existing app.
Hi @aimperialdesign6519! Do you mean, that you would like to display our login buttons on your registration page? You could use our shortcodes to display the buttons anywhere: nextendweb.com/nextend-social-login-docs/usage/
Hi @myselfmyself-en2yu! We do not have a video tutorial for TikTok, only a written one, that you can find here: nextendweb.com/nextend-social-login-docs/provider-tiktok/
Hi Antonio, I think the problem will be caused by a third party code which interferes during the verification. Please open a support ticket here: nextendweb.com/contact-us/nextend-social-login-support/ and we will find out what causes the problem!
Hai , Once I fill secret I'd and key of Google ,then i click verify settings the page is not directing to my website it is directing to the domain page and says "It seems we can’t find what you’re looking for. Perhaps searching can help."plzz help to login with Google issue
Hi Harish, These kind of problems can usually occur, if the page where we try to handle the OAuth flow is not available for some reason, or when your server has a firewall ( e.g. ModSecurity ) that black lists one of the strings that Google uses in the request as a scope. Please get in touch with us over the ticket system: nextendweb.com/contact-us/nextend-social-login-support/ and we will check this problem on your site.
Hello, I want to know how I can redirect the user to a specific page of my website once they have logged in? On google or facebook. I know I must add a few lines of code in wp-content\themes\xxxxxxxxx\include\ ?
Hello Oscar! You don't need to do custom coding for that. If you go to our Global Settings > General tab: nextendweb.com/nextend-social-login-docs/global-settings/ you will find the "Fixed redirect url" setting, which is the strongest redirect in Nextend Social Login. So you could simply enter the URL of the page into that field.
@@scottkauer6642 Hi Scott! No, this setting is about the redirection after logging in, so Google won't have a connection to this part. You only need to change your Google API settings, if you are changing the "OAuth redirect uri proxy page": nextendweb.com/nextend-social-login-docs/global-settings/ so the page, where our login codes are happening. By default we are using the wp-login.php page of your website to run our login codes, but if for example you want to hide the url of this page, you can use a different page. Google only sends it's datas to the specified page, that is why changing it would require changing the url in the API too. So the process is: login button pressed -> first time user uses the popup login / second time user doesn't see anything -> Google sends it's datas and we are running our login codes on the wp-login.php page or on the OAuth redirect uri proxy page -> we are redirecting to the Fixed redirect url.
@@NEXTEND I don't need anyone to log in to the back end. Just want them to go from the main page, click the Google login (for members of our specific GSuite domain only), then be directed to a specific start page.
Hi Mushtaq, Sorry for the delayed reply! Actually users can use the social buttons for both registration and login. So this is why they are appearing in both. Anyways at our Global Settings > Login form tab: you can find options to hide the social buttons from a certain form: nextendweb.com/nextend-social-login-docs/global-settings-login-form/
Hi! Did you manage to go through all the steps?: nextendweb.com/nextend-social-login-docs/provider-google/#configuration The Google (and other) buttons are only appearing once the configuration is completely ready. After that, we are displaying the buttons in places, where the wp_login_form action was used to create the login form, like the /wp-login.php page of your website. If you want to have the button elsewhere, you could use the shortcode: nextendweb.com/nextend-social-login-docs/usage/
