One click registration & login plugin for Facebook, Google, X (formerly Twitter) and more. Quick setup and easy configuration.
Nextend Social Login is a professional, easy to use and free WordPress plugin. It lets your visitors register and login to your site using their social profiles (Facebook, Google, X (formerly Twitter), etc.) instead of forcing them to spend valuable time to fill out the default registration form. Besides that, they don’t need to wait for validation emails or keep track of their username and password anymore.
Nextend Social Login seamlessly integrates with your existing WordPress login and registration form. Existing users can add or remove their social accounts at their WordPress profile page. A single user can attach as many social account as they want allowing them to log in with Facebook, Google or X (formerly Twitter).
Three popular providers: Facebook, Google and X (formerly Twitter)
Providers are the services which the visitors can use to register and log in to your site. Nextend Social Login allows your visitors to log in with their account from the most popular social networks: Facebook, Google and X (formerly Twitter).
Free version features
One click registration and login via Facebook, Google and X (formerly Twitter)
Your current users can easily connect their Facebook, Google or X (formerly Twitter) profiles with their account
Social accounts are tied to a WordPress user account so every account can be accessed with and without social account
You can define custom redirect URL after the registration (upon first login) using any of the social accounts.
You can define custom redirect URL after each login with any of the enabled social accounts.
Display Facebook, Google, X (formerly Twitter) profile picture as avatar
Login widget and shortcodes
Customizable designs to match your site
Editable and translatable texts on the login buttons
Upload Nextend Social Login through ‘Plugins > Add New > Upload’ interface or upload nextend-facebook-connect folder to the /wp-content/plugins/ directory.
Activate the Nextend Social Login plugin through the ‘Plugins’ menu in WordPress.
Go to the ‘Settings > Nextend Social Login’ to see the available providers.
Configure the provider you would like to use. (You’ll find detailed instructions for each provider.)
Test the configuration then enable the provider.
Screenshots
Nextend Social Login and Register on the main WP login page
Nextend Social Login and Register in the profile page for account linking
The Providers page with the available providers and their states.
The Settings page of the Facebook provider.
FAQ
Can I make my site GDPR compliant with Nextend Social Login installed?
1. Where does Nextend Social Login display the social login buttons?
The free version of Nextend Social Login displays the social login buttons automatically on the /wp-login.php’s login form and all forms made using the wp_login_form action. You can use Nextend Social Login’s widget and shortcodes if you need to display the buttons anywhere. If you need to publish the login buttons in your theme, you can use the PHP code.
2. How can I get the email address from the X (formerly Twitter) users?
After you set up your APP go to the Settings tab and enter the URL of your Terms of Service and Privacy Policy page. Then hit the Update your settings button. Then go to the Permissions tab and check the “Request email addresses from users” under “Additional Permissions”. There’s a documentation that explains the process with screenshots.
3. Why are random usernames generated?
When a user tries to register with a social account, Nextend Social Login will try to generate a username from the name that comes from the provider. If this name contains special characters, then we won’t be able to generate a username that is valid for WordPress, as WordPress doesn’t allow special characters in usernames either. For this reason we will need to generate a unique and random username for the registered account.
In the Pro Addon it’s possible to ask an username if we can not generate a valid username, so you can avoid random usernames.
4. What should I do when I experience any problems?
Contact us via email and explain the issue you have.
5. How can I translate the plugin?
Find the .pot file at the /languages folder. From that you can start the translation process. Drop us the final .po and .mo files and we’ll put them to the next releases.
6. I have a feature request…
That’s awesome! Contact us and let’s discuss the details.
7. Does Nextend Social Login work with BuddyPress?
Nextend Social Login Free version does not have BuddyPress specific settings and the login buttons will not appear there. However your users will still be able login and register at the normal WordPress login page. Then when logged in they can use every BuddyPress feature their current user role have access to.
Using the Pro Addon you can set where the login buttons should appear on the Register form and how they should look like.
Changelog
3.1.13
Security fix: Error message sanitization.
3.1.12
Fix: We will now delete the user avatar if the social media account which was used to set the avatar for the user gets unlinked.
Fix: Fixed an issue where an error was thrown whenever the download_url() function would return a WP_Error object during the unlinking process.
Fix: Fixed an issue where a plugin/theme force update check could cause a fatal error.
Feature: Global Settings Added new “Unsupported WebView behaviour” option which determines what should happen to the social login buttons in WebView environments.
Improvement: Removed custom download_url() method, instead we will use the standard WordPress version, as it now works as expected.
Improvement: Facebook API call version updated from v13.0 to v19.0.
PRO: Fix: Updated our code to comply with the fact that func_get_args() no longer reports the original value passed to a parameter, and instead returns the current value.
PRO: Improvement: Removed no longer needed “Checkout for WooCommerce” integration, and instead added the following actions at the billing form: woocommerce_before_checkout_shipping_form, woocommerce_after_checkout_shipping_form
Improvement: Shortcode – customlabel shortcode parameter added, which can be used for specifying a custom label for the connect state of the social buttons rendered by the currently used shortcode. Also you can use the {{providerName}} placeholder to display the name of the given provider in your custom text.
PRO: Improvement: Register form – Password template HTML has been updated according to the latest WordPress default Forget Password form structure.
PRO: Improvement: Custom Actions – Full Site Editing compatibility: the Custom Actions feature now attempts to render the buttons on any actions which are fired after the “init” action. ( Earlier, we tried only on the actions fired after the “login_head” and “wp_head” actions, so the buttons weren’t rendered on the actions that were called within the Block Theme widgets. )
Improvement: The HTML of the “Register” submit button in our Register flow can now be overridden over template files.
Improvement: Registration – if the provider has account select screen, then the user will be able to select another account if an error prevented the registration.
Improvement: Auto-linking security improvements.
Improvement: Google provider – new OAuth2 authorization and token endpoints.
Improvement: Developers can now use the “nsl_required_capability” filter to override the default capability ( manage_options ) that is required to be able to access the backend of Nextend Social Login.
Improvement: Japanese translation added.
Improvement: Hebrew translation added.
Feature: Twitter – option to choose whether we should use v1.1 or the v2.0 OAuth flow and credentials. ( The different versions have different App creation guides depending on the selected value. )
PRO: Fix: Yahoo provider – The redirect URL suggestion will now contain the complete Yahoo endpoint URL, as new Apps now require an exact match ( earlier the URLs with query strings weren’t accepted ).
PRO: Improvement: Developers can now add extra validation logics for the “Ask E-mail/Password/Username on registration” features by using the “nsl_validate_extra_input_password_errors”, “nsl_validate_extra_input_username_errors” and “nsl_validate_extra_input_username_errors” filters.
PRO: Improvement: The HTML of the “Ask E-mail/Password/Username on registration” features can now be overridden over template files.
PRO: Feature: Line provider – added an option to allow the auto login.
PRO: Feature: BuddyPress registration integration – so BuddyPress can send its registration notifications upon registration with social login, too.
Improvement: Support login restrictions – BuddyPress activation integration – in this case the actual registration is done by BuddyPress, not Nextend Social Login.
Improvement: Developers can now define the NSL_DISABLE_IN_AMP_REQUESTS constant, to disable the social buttons and its assets in the AMP requests.
Improvement: Developers can now use the “nsl_disabled_register_redirect_url” and “nsl_disabled_login_redirect_url” filters to override the redirects in most cases when the registration or login with social login fails for some reason
Improvement: Introduced some public PHP functions that developers can use to get some user data outside of our normal flow
Improvement: Avatar storing improvements
Feature: Option to allow the profile syncing separately for the registration, login and link actions
PRO: Fix: Apple provider – There was an encoding problem with the scope parameter of the Apple authorization URL.
PRO: Improvement: Developers can now override the GitHub and Disqus client credentials over the “nsl_disqus_api_key” / “nsl_disqus_api_secret” and “nsl_github_client_id” / “nsl_github_client_secret” filters. ( Can be useful for multi sites and multi language sites, as the App of these providers support only a single redirect URL. )
Fix: Google provider – Google OAuth no longer supports any kind of WebViews, so the Google button will be hidden in all WebView environments.
Fix: User selected language in the backend didn’t load our translations in certain cases.
Improvement: We will trigger the “wp_login_failed” action when the login with social login fails, so the login history plugins could track the failed login attempts happened with social login, too.
Improvement: The unlinked social media identifier will be now available from the “nsl_unlink_user” action parameters.
PRO: Fix: Microsoft provider – ErrorInsufficientPermissionsInAccessToken error when using the Personal Audience option.
PRO: Fix: Steam provider – Error when pressing the “Got it” button on the “Fix OAuth Redirect URIs” page while the Steam provider was enabled.
Fix: The Jetpack Boost plugin stopped our authentication flow
Fix: The “WP 2FA” plugin could prevent the login with social login even if our “Support login restrictions” feature was disabled
Fix: PHP error when other plugins tried to force WordPress to update the plugin update transients ( update_plugins ) with null parameter
Fix: The “Page Transitions” feature of Elementor Pro opened our links in the opener window, causing a redirect in both the popup and the popup opener window
Improvement: Introducing the “nsl_connect_button_custom_attributes”, “nsl_unlink_button_custom_attributes”, “nsl_link_button_custom_attributes” filters to add extra attributes on our button links
Improvement: Avatar storing – We won’t try to copy the avatar into our avatar folder if the same file is already there
Improvement: Avatar storing – If the earlier stored avatar file doesn’t exist, we will delete the associated attachment data the next time the user logs in
Improvement: Facebook provider – Graph API version of the used endpoints have been updated from v7.0 to v13.0
PRO: Fix: There was a JavaScript error on the WordPress default Lost Password page when separator layouts were used
PRO: Fix: We didn’t display the intended warning when the Free version was not compatible with the Pro Addon.
PRO: Fix: Apple provider – PHP warning when verifying the provider settings for the first time
PRO: Fix: WebView – we will no longer display the separator either, if we can not display any social buttons because of the embedded browser environment.
PRO: Fix: TikTok provider – the registration and login didn’t work as TikTok modified their endpoints, the request method and the response of their API.
PRO: Improvement: Yahoo provider – Getting Started Update
PRO: Improvement: PayPal provider – Getting Started Update
Improvement: Facebook provider – Facebook popup height has been increased, so everything will be visible during Authorization
Improvement: Facebook provider – The Facebook button will no longer be visible in Android WebView, as Facebook has deprecated the support for Facebook Login Authentication on Android WebView. In the WebView of the Facebook and Instagram Android Apps the buttons will still be visible, as Facebook currently allows the authentication over these Android WebViews.
Feature: Option to control the appearance of the Redirect Overlay
Improvement: If there is a slow server or a poor internet connection, the redirect after the authentication with social login might take some time. During this time we will display a loading spinner, so the visitor will know that something is about to happen.
PRO: Feature: Integration for Easy Digital Downloads Checkout form.
PRO: Feature: Display social buttons with layouts on Custom Actions
3.1.1
Improvement: string paths from the language files have been removed.
PRO: Improvement: VKontakte provider – we will use the API version 5.131 for the endpoints, as API version 5.74 is deprecated.
PRO: Feature: Easy Digital Downloads login and register form support.
3.1.0
Fix: Display error message for logged out users, when they try to login with a social media account that’s email address matches with a WordPress account email address, that has a linked provider from the same kind.
Fix: WooRewards will be able to generate points on registration with Nextend Social Login
Improvement: nsl_already_linked_error_message filter added to modify the error message when a WordPress account with the same email address has another social media account already linked
Improvement: Separate autologin from registerComplete function
Improvement: nsl_autologin_priority filter added to control the priority of the autologin after the registration with Nextend Social Login
PRO: Improvement: New Facebook Sync data field: Quote ( requires user_likes permission )
PRO: Feature: BuddyPress Layout options added for registration form
3.0.29
Fix: We added clear: both; on .nsl-container to make floated elements before the buttons not to mess up the layout.
Fix: Jetpack removed the “Register” button in our register flow when the registration was handled over the WordPress default login page.
Improvement: The social buttons with the Default style will try to go as wide as the longest button, if there is enough space in the social button container element.
Feature: Fullwidth style for the social buttons.
Summer Sale offer
3.0.28
Fix: We didn’t display the disabled registration notification when the “OAuth redirect uri proxy page” feature was used.
Fix: Google provider – Social button didn’t appear in Opera Mini and iOS Opera Touch.
Fix: WordPress couldn’t download the avatars coming from the social media when the avatar URL was too long.
Fix: Our styles were missing from pages with AMP mode of “AMP for WP”.
Fix: There was an AMP validation error as earlier we didn’t load our styles into the unique style tag with the “amp-custom” attribute.
Fix: Database – There was a database error on MySQL 8.0.17 and above, as the display width attribute has been deprecated for integer data types.
Fix: Database – Default values of register_date, login_date and link_date have been changed from “0000-00-00 00:00:00” to NULL, since the old value could cause a database error when we tried to make database structure modifications in databases when NO_ZERO_DATE, NO_ZERO_IN_DATE values are set in sql_mode.
Improvement: Developers can now pass false value for the nsl_disabled_register_error_message filter for turning off our registration disabled notification.
Improvement: Google provider – The Google button will no longer be hidden in Line App WebView, as Google allows the authentication over the WebView of this App.
Improvement: Developers can now use the nsl_unlink_user action to run custom function when a user unlinks the social media account from the WordPress account.
Improvement: The context “Register form submit button label” has been added to the Register button appearing in our register flow. So it can now be translated with language files separately.
Improvement: On the frontend we will use native JavaScript instead of jQuery.
PRO: Fix: Linkedin provider didn’t store the first name and last name, if the account didn’t have profile with English as either primary language or secondary language.
PRO: Fix: Our integration for “Checkout for WooCommerce” didn’t work with their most recent versions.
Improvement: Google provider – using OAuth2 v2 endpoint
Improvement: 2 new filters for customizing the redirect url and error message when login is disabled.
Improvement: Database – new column “social_users_id” for Primary Key
Improvement: PHP 8.0 compatibility
Improvement: We will override the WordPress default avatar using the “pre_get_avatar_data” filter instead of “get_avatar” filter.
PRO: Fix: Apple provider – Logo overlaps the box shadow of the light button skin
PRO: Improvement: New Google Sync data fields: Genders and Locations ( requires People API )
PRO: Removed: Google Sync data fields: Gender, Profile link, Taglines and Residences
3.0.26
Fix: PHP notice by AMP plugin
Fix: The orphan thumbnail sizes generated from the avatars will be deleted when the earlier stored avatar has been overridden by the provider.
Improvement: Hashed filenames for avatars to avoid tracking back the user avatars over the URL by User ID.
Improvement: Avatars are now stored in the dedicated folder called nsl_avatars. The name of the folder can be modified with the NSL_AVATARS_FOLDER constant.
Improvement: Ultimate Member – the registration date will appear in the info popup for users registered by social login.
PRO: Improvement: WooCommerce – Email template for registration setting defines the email template that the registration notification will use when the registration happens with social login. Earlier this was a hidden and built in feature of the Registration notification sent to setting.
3.0.25
Fix: WishList Member plugin prevented the strong redirects of Nextend Social Login.
Fix: Connect button – URL encoding in the redirect parameter to keep the URL parameters after login.
Fix: JavaScript errors on JavaScript minification with WP Hide & Security Enhancer
Fix: Delayed login caused by image optimization plugins, like EWWW Image Optimizer.
Fix: Social button styles will be loaded in AMP Reader template pages, too.
Improvement: Reactivate renamed to Analyze & Repair
Improvement: Notification at the backend, when there is at least one configured provider however it is not enabled.
Improvement: Facebook provider – updated steps and new video guide in the Getting Started section.
Improvement: Facebook provider – new default button color.
Improvement: Facebook provider – we will use Graph API v7.0 for the endpoints.
Improvement: Google provider – updated steps and new video guide in the Getting Started section.
Improvement: Allow redirect and error message overrides when registration is disabled.
Improvement: The Google button will no longer be hidden for Instagram, Twitter and Facebook App WebViews, as Google allows the authentication over the WebView of these Apps.
PRO: Fix: Plugin could not be activated because it triggered a fatal error. – Fix for the problem: Deactivate and delete “Nextend Social Login Pro Addon” plugin with version 3.0.21, then activate the version 3.0.22.
3.0.21
Compatibility: PHP 7 or greater is required for the new version!.
Fix: Icon style – Icons will be wrapped into multiple lines when there is no more room for them.
Fix: Social buttons will no longer be distorted when the page is translated with Google translator.
Fix: WPLMS theme – social button style and duplicated social buttons.
Fix: WP Rocket – compatibility with combine JavaScript feature.
Fix: Popup target window when the social buttons appear in certain modals.
Fix: Ultimate Member avatars with social registration.
Fix: Avatar will be synchronized again, if the attachment was already set, but the file doesn’t exist.
Improvement: Database – Register, Link and Login date will be stored in database.
Improvement: Improvement: Google – Light skin will be the default button skin.
PRO: Fix: Social button layouts in Theme My Login forms.
PRO: Fix: Ultimate Member and Support login restrictions – Users will be redirected to the Ultimate Member login page after the registration.
PRO: Improvement: Yahoo new endpoint and app creation guide. New and deprecated Sync data fields.
PRO: Improvement: WooCommerce automatically generated password feature support when Registration notification sent to is set to User or User and Admin.
3.0.20
Fix: Ultimate Member Auto Approve + Support Login Restriction – Avatars will be synchronized.
Fix: Error message didn’t show up when an “OAuth redirect uri proxy page” was selected.
PRO: Note: We had plans to implement the Instagram provider. Unfortunately we need to change our mind, since the Instagram API will become deprecated soon!
3.0.17
Fix: Activation fix on certain sub-domains.
3.0.16
Fix: NSL Avatars used to override the specified BuddyPress avatars.
Fix: 500 error when the Extended Profiles setting is disabled in BuddyPress.
Fix: By default, users won’t be redirected to the homepage after unlinking their accounts, instead will be redirected back to the page, where the unlink action has happened.
Fix: Nextend Social Login will now wait for jQuery before positioning the social buttons.
Fix: Getting Started section of some providers are updated with the new App creation steps.