[{"name":"Nextend Social Login and Register","slug":"nextend-facebook-connect","version":"3.1.14","author":"Nextendweb","author_profile":"https://profiles.wordpress.org/nextendweb/","requires":"4.9","tested":"6.6.2","requires_php":"7.0","requires_plugins":[],"rating":98,"ratings":{"1":8,"2":2,"3":2,"4":8,"5":404},"num_ratings":424,"support_threads":13,"support_threads_resolved":10,"downloaded":5968202,"last_updated":"2024-08-01 5:37am GMT","added":"2012-09-25","homepage":"https://nextendweb.com/","sections":{"description":"

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.

\n
Demo | Tutorial videos | Docs | Support | Pro Addon
\n

\n\n

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
Very simple to setup and use
Clean, user friendly UI
Fast and helpful support

Additional features in the Pro addon

WooCommerce compatibility
BuddyPress compatibility
UserPro compatibility
Ultimate Member compatibility
Easy Digital Downloads compatibility
Pro providers: LinkedIn, Amazon, VKontakte, WordPress.com, Yahoo, PayPal, Disqus, Apple, GitHub, Microsoft, Line, Discord, Slack, TikTok, Steam, Twitch, Kakao, Reddit, Spotify and more coming soon
Configure whether email address should be asked on registration at each provider
Configure whether username should be asked on registration at each provider
Choose from icons or wide buttons
Several login layouts
Restrict specific user roles from using the social logins. (You can restrict different roles for each provider.)
Assign specific user roles to the newly registered users who use any social login provider. (You can set different roles for each provider.)
Show the name of the linked providers in the Users table

Usage

After you activated the plugin configure and enable the provider you want to use, then the plugin will automatically

add the login buttons to the WordPress login page. See screenshot #1
add the account linking buttons to the WordPress profile page. See screenshot #2

\n","installation":"

Automatic installation

Search for Nextend Social Login through ‘Plugins > Add New’ interface.
Find the plugin box of Nextend Social Login and click on the ‘Install Now’ button.
Then activate the Nextend Social Login plugin.
Go to the ‘Settings > Nextend’ Social Connect 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.

Manual installation

Download Nextend Social Login
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.

\n","faq":"\n

\nCan I make my site GDPR compliant with Nextend Social Login installed?\n\n

Sure, Nextend Social Login provides you the tools to make your site GDPR compliant. Check out the Nextend Social Login GDPR documentation to learn more about the topic.

\n1. Where does Nextend Social Login display the social login buttons?\n\n

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.
\nYou 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.

\n2. How can I get the email address from the X (formerly Twitter) users?\n\n

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.

\n3. Why are random usernames generated?\n\n

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.
\nFor 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.

\n4. What should I do when I experience any problems?\n\n

\n5. How can I translate the plugin?\n\n

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.

\n6. I have a feature request…\n\n

That’s awesome! Contact us and let’s discuss the details.

\n7. Does Nextend Social Login work with BuddyPress?\n\n

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.

\n\n","changelog":"

3.1.14

Fix: Updated compatibility with Jetpack (Jetpack_SSO class has been changed to Automattic\\Jetpack\\Connection\\SSO).
Fix: Fixed an issue where the old avatar would still show up due to browser cache even after the avatar has been changed and synced.
Fix: Fixed an issue where we had forcefully overriden default avatars as well over the “pre_get_avatar_data” filter. Now the “force_default” argument is respected.
Fix: Fixed an issue where the target window setting couldn’t work properly for buttons that were loaded dynamically after page load.
Fix: Fixed an issue where the “Fallback username prefix on register” and “Ask Username on registration – When username is empty or invalid” options wouldn’t work if the “Username prefix on register” was set.
Fix: Fixed an issue where it was possible to have too long of a username, thus not being able to register with the social login.
Fix: Fixed an issue where consecutive social icons of the same provider could not appear on the same page, when at least one instance was hidden by a CSS visibility property.
Improvement: Developers from now on can use the “nsl_register_roles” filter to override the default roles of the user registered by social login.
Improvement: Solid Security 2FA compatibility – Their 2FA solution will only show the 2FA modal if our “Support login restrictions” option is enabled.
\n
Improvement: Facebook Getting Started updated.
\n
\n
PRO: Fix: Fixed an issue where it was possible to login with the social login through BuddyPress for the first time even if the account was still awaiting activation.
\n
PRO: Improvement: New TikTok Sync data field: Username ( requires user.info.profile scope ).
PRO: Improvement: New LinkedIn Sync data fields: Headline, Vanity name ( requires Advertising API ).
PRO: Improvement: PayPal Getting Started Update.
PRO: New provider: Patreon

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: Google Getting Started updated.
\n
Improvement: Facebook API call version updated from v13.0 to v19.0.
\n
\n
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.
\n
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
PRO: New provider: Spotify

3.1.11

Fix: The default “Terms and conditions” text can now be translated with our language files.
Improvement: Facebook Getting Started Update
\n
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.
\n
\n
PRO: Improvement: Register form – Password template HTML has been updated according to the latest WordPress default Forget Password form structure.
\n
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. )
PRO: Improvement: PayPal Getting Started Update
PRO: Improvement: PayPal integration updated according to the new PayPal endpoint and API changes.
PRO: New provider: Reddit

3.1.10

Fix: Fixed a crash during login when “Support login restrictions” is enabled while WP 2FA plugin is installed.
Fix: Fixed a PHP Warning issue related to Ultimate Member when “Support login restrictions” is enabled.
Fix: Indeed Ultimate Affiliate Pro compatibility – registration with social login didn’t award rewards to the affiliates
Fix: Terms and conditions text could not be translated
Improvement: Twitter provider has been rebranded as X
\n
Improvement: Facebook Getting Started Update
\n
\n
PRO: Fix: Added the now needed Content-Type: application/x-www-form-urlencoded header to the TikTok access token endpoint request.
\n
PRO: Fix: Updated our code to use “Sign In with LinkedIn using OpenID Connect” instead of the old deprecated “Sign in with LinkedIn” product.
PRO: Improvement: LinkedIn Getting Started Update
PRO: Improvement: Added new “edd_before_purchase_form” action for our Easy Digital Downloads integration.
PRO: New provider: Kakao

3.1.9

Feature: Facebook provider – Added option to choose a custom profile image size.
Fix: renderButtonsWithContainerAndTitle() method will no longer render the connect buttons for the logged in users
Fix: renderLinkAndUnlinkButtons() method will no longer render the link and unlink buttons for the logged out users
\n
Improvement: Developers can now use the “nsl_autolink_error_redirect_url” filter to override the redirect URL when auto-linking fails.
\n
\n
PRO: Feature: TikTok provider – Sync data fields added.
\n
PRO: Improvement: TikTok provider – new OAuth2 endpoints and redirect_url introduced.
PRO: Improvement: TikTok Getting Started Update

3.1.8

Fix: In some cases we opened the login popup window in an incorrect position.
Fix: Some language files had wrong language codes in their names. For example es_LA had been renamed to es_ES and zh_ZH to zh_CN.
Improvement: Facebook Getting Started Update
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.
\n
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. )
\n
\n
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 ).
\n
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.
PRO: Feature: Discord provider – v10 API support
PRO: Feature: Discord provider – Sync data fields added.

3.1.7

Fix: The !important CSS rules can cause problems for AMP validators, so we will use more specific selectors instead.
Fix: Some object cache might caused a PHP warning when the login happened with third party login forms.
Fix: There was a JavaScript error in WordPress-like login forms that didn’t fire any login specific actions
Improvement: Twitter Getting Started Update
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
\n
Feature: Option to allow the profile syncing separately for the registration, login and link actions
\n
\n
PRO: Fix: Apple provider – There was an encoding problem with the scope parameter of the Apple authorization URL.
\n
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. )
PRO: Improvement: Microsoft Getting Started Update
PRO: New provider: Twitch

3.1.6

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.
\n
Improvement: The unlinked social media identifier will be now available from the “nsl_unlink_user” action parameters.
\n
\n
PRO: Fix: Microsoft provider – ErrorInsufficientPermissionsInAccessToken error when using the Personal Audience option.
\n
PRO: Fix: Steam provider – Error when pressing the “Got it” button on the “Fix OAuth Redirect URIs” page while the Steam provider was enabled.
PRO: Fix: TikTok provider – Invalid request parameters error
PRO: Improvement: TikTok provider – Getting Started Update
PRO: Feature: TikTok provider – button skin selector added.

3.1.5

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
\n
Improvement: Facebook provider – Graph API version of the used endpoints have been updated from v7.0 to v13.0
\n
\n
PRO: Fix: There was a JavaScript error on the WordPress default Lost Password page when separator layouts were used
\n
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
PRO: Feature: BuddyPress – option to show/hide the Social Accounts tab
PRO: Feature: BuddyPress – Introducing “nsl_bp_social_accounts_tab_slug” filter to modify the slug of the BuddyPress – Social Accounts tab.
PRO: Feature: Line – Initial Login method and Force initial login method settings.
PRO: New provider: Steam

3.1.4

Fix: PHP Warning on redirects, when the “Host” header is not sent by the browser ( e.g when an action happens with CLI )
Fix: The redirect parameter of the shortcode didn’t work in AJAX requests
Fix: Provider order modification didn’t work in WordPress 5.9
Improvement: Google Getting Started Update
Improvement: Twitter Getting Started Update
\n
Feature: Option to attempt to Bypass cache on redirect by adding a GET parameter to the redirect URL
\n
\n
PRO: New provider: TikTok
\n

3.1.3

Fix: Database error on clean install
Improvement: WPML Redirect URL compatibility
Improvement: Updated Italian translation files
Improvement: Twitter 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.
\n
Feature: Option to control the appearance of the Redirect Overlay
\n
\n
PRO: New provider: Slack
\n

3.1.2

\n
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.
\n
\n
PRO: New provider: Discord
\n
PRO: Fix: The Microsoft provider used a wrong redirect url, when the Frontend and the Backend URL of the site were different.
PRO: Improvement: New options for the Line provider: Force reauthorization on each login and Add LINE Official Account as a friend
PRO: Improvement: New options for the Microsoft provider: Audience and Authorization Prompt
PRO: Feature: Integration for Easy Digital Downloads Checkout form.
PRO: Feature: Display social buttons with layouts on Custom Actions

3.1.1

\n
Improvement: string paths from the language files have been removed.
\n
\n
PRO: Improvement: VKontakte provider – we will use the API version 5.131 for the endpoints, as API version 5.74 is deprecated.
\n
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
Improvement: Facebook Getting Started Update
\n
Improvement: WPML compatibility
\n
\n
PRO: New provider: Microsoft
\n
PRO: New provider: Line
PRO: Improvement: Optimized Light and Dark SVG for Apple
PRO: Improvement: Apple Getting Started Update
PRO: Improvement: PayPal Getting Started Update
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: Twitter Getting Started Update
Improvement: Google Getting Started Update
Improvement: Facebook Getting Started Update
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.
\n
Improvement: On the frontend we will use native JavaScript instead of jQuery.
\n
\n
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.
\n
PRO: Fix: Our integration for “Checkout for WooCommerce” didn’t work with their most recent versions.
PRO: Improvement: Apple Getting Started Update

3.0.27

Fix: Ultimate Member prevents our registration when we need to ask extra information before the registration.
Fix: post_mime_type PHP notice.
Improvement: Italian translation files added.
Improvement: Notice handling logic improvements.
Improvement: Twitter Getting Started Update
Improvement: Facebook Getting Started Update
Improvement: Facebook Warning for App replacing
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
\n
Improvement: We will override the WordPress default avatar using the “pre_get_avatar_data” filter instead of “get_avatar” filter.
\n
\n
PRO: Fix: Apple provider – Logo overlaps the box shadow of the light button skin
\n
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.
Improvement: 2 new filters for developers
Improvement: nsl_disabled_register_error_message filter will also work when the OAuth flow is being handled over the default login page.
Improvement: Facebook provider – Getting Started update.
Feature: Custom label for social buttons in register forms and new shortcode parameter to use the register labels.
\n
Black friday offer
\n
\n
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.
\n

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.
\n
Feature: Facebook provider – button skin selector added.
\n
\n
PRO: New provider: GitHub
\n
PRO: Improvement: WooCommerce Billing – Default with separator layout to display the buttons on the place where the action is fired.
PRO: Improvement: LinkedIn provider – updated steps in Getting Started section.
PRO: Improvement: Pro Addon PHP 7.0 version check to load Pro Addon only on compatible PHP versions.
PRO: Improvement: MemberPress Login form – option to hide the social buttons.
PRO: Feature: Show linked providers – Option to display the name of the providers which are linked to a WordPress account.

3.0.24

Fix: BuddyPress 6.0 compatibility fix.

3.0.23

Fix: PHP error when BuddyPress – Activity is disabled.
Fix: Support login restrictions – delete persistent data when the registration was prevented by a third party plugin
\n
Fix: Twitter – 48×48 avatars can be stored again
\n
\n
PRO: Fix: Longer Apple JWT token expiry.
\n
PRO: Improvement: compatibility with the forms generated by the plugin “Checkout for WooCommerce”
PRO: Improvement: Apple provider button skins to comply with Human Interface Guidelines

3.0.22

\n
Fix: Updated language files
\n
\n
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.
\n

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.
Improvement: Pages which are being used by other plugins will be filtered out from Page for register flow and OAuth redirect uri proxy page
Improvement: The Getting Started sections are updated with new steps.
Improvement: New registrations happening with social login will also be displayed in the BuddyPress – Activity log.
Improvement: Shortcode provider parameter will also define the visibility of the link and unlink buttons.
Feature: Option to disable the Google account select prompt on each login.
\n
For developers: The provider instance can now be accessed over “nsl_registration_form_start” and “nsl_registration_form_end” actions
\n
\n
PRO: New provider: Apple
\n
PRO: Fix: Plugin update error – WordPress cached the wrong update url.
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.
Feature: Shortcode – Grid style
Feature: German translation files added.
Improvement: redirect_to URL parameter will be stronger than current page url
\n
Improvement: nsl_registration_user_data filter can now be also used
\nfor preventing the registration.
\n
\n
PRO: Improvement: PayPal updated endpoints. New Sync Data field: PayPal account ID (payer ID)
\n
PRO: Removed: PayPal Sync Data fields: Date of birth, Age range, Phone, Account type, Account creation date, Time zone, Locale, Language.

3.0.19

Fix: Shortcode – align parameter notice
Fix: Social buttons didn’t show up properly when the action where we check jQuery was called multiple times.
\n
Improvement: Google Select account modal before the login.
\n
\n
PRO: Fix: Jetpack – display our social buttons on custom Jetpack comment form
\n
PRO: Feature: BuddyPress – option to disable the social buttons on the action: bp_sidebar_login_form
PRO: Improvement: LinkedIn v2 REST API update. Getting Started section updated with the new App creation steps.
PRO: Removed: LinkedIn Sync data

3.0.18

Fix: _nsl is not defined error
Fix: The shortcode of Page for register flow will be rendered into the correct position.
\n
Fix: Google – G+ logo is replaced with simple G logo.
\n
\n
PRO: Fix: Target window will open the auth window of the provider in the selected way again.
\n
PRO: Fix: Update notice when the Free and Pro Addon are not compatible.
PRO: Feature: Social buttons for BuddyPress – Login widget
PRO: Feature: Option to disable the WordPress Toolbar on the front-end for some roles.
PRO: New provider: Yahoo
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.
Feature: Russian translation added.
Feature: Display avatars in “All media items” – Images can now load faster in Media Library – Grid view, when this option is enabled.
Feature: Social button alignment option for WordPress forms, shortcode and widget.
Feature: Membership – is now available in the FREE version and provides support for WordPress default membership as well.
Feature: new hook allows overriding the username and email before registration – nsl_registration_user_data
Facebook – Graph API v3.2 – old API-s may require API Call version upgrade!
Old Nextend Facebook/Twitter/Google Connect compatibility has been removed.
\n
Social Buttons use flex-box layout now.
\n
\n
PRO: Fix: Internet Explorer – Pro Addon activation.
\n
PRO: Fix: Facebook provider – Sync data: Gender, Profile link, Age range can be retrieved again.
PRO: Feature: Social button alignment option for WooCommerce, Comment, BuddyPress, MemberPress, UserPro, Ultimate Member forms.
PRO: Feature: Unlink option to disable unlink buttons.
PRO: Feature: PayPal – Option to disable the email scope.
PRO: Removed: Facebook provider – Sync data fields: Currency, TimeZone, Locale became deprecated.
PRO: Improvement: Google+ API will shut down soon, so Google Sync data will use Google People API instead.

3.0.14

Fix: Conflict with Login with Ajax reset password.
Fix: BuddyPress related themes, that render the avatar with the bp_displayed_user_avatar() will be able to get the avatar of the user.
Fix: New email and profile Google scopes, since old ones became deprecated.
Fix: WooCommerce User Email Verification plugin prevented users with NSL from logging in.
Fix: registerComplete function is hooked later to let other plugins send their email notifications.
\n
Old Nextend Twitter/Google Connect – backwards compatibility notice added. In the 3.0.15 release the backward compatibility will be removed.
\n
\n
PRO: Fix: Ultimate Member – missing avatar when Support login restriction is disabled.
\n
PRO: Fix: Authorized domain notification when the page was authorized on non www but was visited on www or vice versa.
PRO: New provider: WordPress.com
PRO: New provider: Disqus

3.0.13

Fix: Twitter Getting Started and Settings page updated according to the new Twitter App creation.
Fix: Won’t stuck on a blank page anymore when the login and registration is blocked by WP Cerber.
Fix: Infinite redirect loop when home page was selected as OAuth redirect uri proxy page.
Fix: Safari will no longer close the page automatically after logging in with NSL.
Feature: Login restriction – Some plugins are now able to prevent the login of NSL when admin approval or email verification is necessary!
Feature: Google button skins.
Feature: Portuguese (Brazilian) …

\n","screenshots":"

$\"Nextend$
Nextend Social Login and Register on the main WP login page
$\"Nextend$
Nextend Social Login and Register in the profile page for account linking
$\"The$
The Providers page with the available providers and their states.
$\"The$
The Settings page of the Facebook provider.

"},"short_description":"One click registration & login plugin for Facebook, Google, X (formerly Twitter) and more. Quick setup and easy configuration.","download_link":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.14.zip","screenshots":{"1":{"src":"https://ps.w.org/nextend-facebook-connect/assets/screenshot-1.png?rev=2322319","caption":"Nextend Social Login and Register on the main WP login page"},"2":{"src":"https://ps.w.org/nextend-facebook-connect/assets/screenshot-2.png?rev=2511509","caption":"Nextend Social Login and Register in the profile page for account linking"},"3":{"src":"https://ps.w.org/nextend-facebook-connect/assets/screenshot-3.png?rev=2511509","caption":"The Providers page with the available providers and their states."},"4":{"src":"https://ps.w.org/nextend-facebook-connect/assets/screenshot-4.png?rev=2511509","caption":"The Settings page of the Facebook provider."}},"tags":{"facebook":"facebook","google":"google","social-login":"social login","twitter":"twitter","x":"x"},"versions":{"1.0":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.0.zip","1.1":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.1.zip","1.2":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.2.zip","1.4":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.4.zip","1.4.9":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.4.9.zip","1.6.0":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.1.6.0.zip","2.0.2":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.2.0.2.zip","3.0.1":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.1.zip","3.0.10":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.10.zip","3.0.11":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.11.zip","3.0.12":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.12.zip","3.0.13":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.13.zip","3.0.14":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.14.zip","3.0.15":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.15.zip","3.0.16":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.16.zip","3.0.17":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.17.zip","3.0.18":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.18.zip","3.0.19":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.19.zip","3.0.2":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.2.zip","3.0.20":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.20.zip","3.0.21":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.21.zip","3.0.22":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.22.zip","3.0.23":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.23.zip","3.0.24":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.24.zip","3.0.25":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.25.zip","3.0.27":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.27.zip","3.0.28":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.28.zip","3.0.29":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.29.zip","3.0.3":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.3.zip","3.0.4":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.4.zip","3.0.6":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.6.zip","3.0.7":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.7.zip","3.0.8":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.8.zip","3.0.9":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.0.9.zip","3.1.0":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.0.zip","3.1.1":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.1.zip","3.1.10":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.10.zip","3.1.11":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.11.zip","3.1.12":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.12.zip","3.1.13":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.13.zip","3.1.14":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.14.zip","3.1.2":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.2.zip","3.1.3":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.3.zip","3.1.4":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.4.zip","3.1.5":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.5.zip","3.1.6":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.6.zip","3.1.7":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.7.zip","3.1.8":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.8.zip","3.1.9":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.3.1.9.zip","trunk":"https://downloads.wordpress.org/plugin/nextend-facebook-connect.zip"},"donate_link":"https://www.facebook.com/nextendweb","icons":{"1x":"https://ps.w.org/nextend-facebook-connect/assets/icon.svg?rev=1825061","svg":"https://ps.w.org/nextend-facebook-connect/assets/icon.svg?rev=1825061"}},{"name":"Action Scheduler","slug":"action-scheduler","version":"3.8.2","author":"Automattic","author_profile":"https://profiles.wordpress.org/automattic/","requires":"6.4","tested":"6.6.2","requires_php":"7.0","requires_plugins":[],"rating":70,"ratings":{"1":3,"2":1,"3":0,"4":0,"5":6},"num_ratings":10,"support_threads":5,"support_threads_resolved":1,"downloaded":369661,"last_updated":"2024-09-12 11:30pm GMT","added":"2020-07-14","homepage":"https://actionscheduler.org","sections":{"description":"

Action Scheduler is a scalable, traceable job queue for background processing large sets of actions in WordPress. It’s specially designed to be distributed in WordPress plugins.

Action Scheduler works by triggering an action hook to run at some time in the future. Each hook can be scheduled with unique data, to allow callbacks to perform operations on that data. The hook can also be scheduled to run on one or more occasions.

Think of it like an extension to do_action() which adds the ability to delay and repeat a hook.

Battle-Tested Background Processing

Every month, Action Scheduler processes millions of payments for Subscriptions, webhooks for WooCommerce, as well as emails and other events for a range of other plugins.

It’s been seen on live sites processing queues in excess of 50,000 jobs and doing resource intensive operations, like processing payments and creating orders, at a sustained rate of over 10,000 / hour without negatively impacting normal site operations.

This is all on infrastructure and WordPress sites outside the control of the plugin author.

If your plugin needs background processing, especially of large sets of tasks, Action Scheduler can help.

Learn More

To learn more about how to Action Scheduler works, and how to use it in your plugin, check out the docs on ActionScheduler.org.

There you will find:

Usage guide: instructions on installing and using Action Scheduler
WP CLI guide: instructions on running Action Scheduler at scale via WP CLI
API Reference: complete reference guide for all API functions
Administration Guide: guide to managing scheduled actions via the administration screen
Guide to Background Processing at Scale: instructions for running Action Scheduler at scale via the default WP Cron queue runner

Credits

Action Scheduler is developed and maintained by Automattic with significant early development completed by Flightless.

Collaboration is cool. We’d love to work with you to improve Action Scheduler. Pull Requests welcome.

\n","changelog":"

3.8.2 – 2024-09-12

Add missing parameter to the pre_as_enqueue_async_action hook.
Bump minimum PHP version to 7.0.
Bump minimum WordPress version to 6.4.
Make the batch size adjustable during processing.

3.8.1 – 2024-06-20

Fix typos.
Improve the messaging in our unidentified action exceptions.

3.8.0 – 2024-05-22

Documentation – Fixed typos in perf.md.
Update – We now require WordPress 6.3 or higher.
Update – We now require PHP 7.0 or higher.

3.7.4 – 2024-04-05

Give a clear description of how the $unique parameter works.
Preserve the tab field if set.
Tweak – WP 6.5 compatibility.

3.7.3 – 2024-03-20

Do not iterate over all of GET when building form in list table.
Fix a few issues reported by PCP (Plugin Check Plugin).
Try to save actions as unique even when the store doesn’t support it.
Tweak – WP 6.4 compatibility.
Update “Tested up to” tag to WordPress 6.5.
update version in package-lock.json.

3.7.2 – 2024-02-14

No longer user variables in _n() translation function.

3.7.1 – 2023-12-13

update semver to 5.7.2 because of a security vulnerability in 5.7.1.

3.7.0 – 2023-11-20

Important: starting with this release, Action Scheduler follows an L-2 version policy (WordPress, and consequently PHP).
Add extended indexes for hook_status_scheduled_date_gmt and status_scheduled_date_gmt.
Catch and log exceptions thrown when actions can’t be created, e.g. under a corrupt database schema.
Tweak – WP 6.4 compatibility.
Update unit tests for upcoming dependency version policy.
make sure hook action_scheduler_failed_execution can access original exception object.
mention dependency version policy in usage.md.

3.6.4 – 2023-10-11

Performance improvements when bulk cancelling actions.
Dev-related fixes.

3.6.3 – 2023-09-13

Use _doing_it_wrong in initialization check.

3.6.2 – 2023-08-09

Add guidance about passing arguments.
Atomic option locking.
Improve bulk delete handling.
Include database error in the exception message.
Tweak – WP 6.3 compatibility.

3.6.1 – 2023-06-14

Document new optional $priority arg for various API functions.
Document the new --exclude-groups WP CLI option.
Document the new action_scheduler_init hook.
Ensure actions within each claim are executed in the expected order.
Fix incorrect text domain.
Remove SHOW TABLES usage when checking if tables exist.

3.6.0 – 2023-05-10

Add $unique parameter to function signatures.
Add a cast-to-int for extra safety before forming new DateTime object.
Add a hook allowing exceptions for consistently failing recurring actions.
Add action priorities.
Add init hook.
Always raise the time limit.
Bump minimatch from 3.0.4 to 3.0.8.
Bump yaml from 2.2.1 to 2.2.2.
Defensive coding relating to gaps in declared schedule types.
Do not process an action if it cannot be set to in-progress.
Filter view labels (status names) should be translatable | #919.
Fix WPCLI progress messages.
Improve data-store initialization flow.
Improve error handling across all supported PHP versions.
Improve logic for flushing the runtime cache.
Support exclusion of multiple groups.
Update lint-staged and Node/NPM requirements.
add CLI clean command.
add CLI exclude-group filter.
exclude past-due from list table all filter count.
throwing an exception if as_schedule_recurring_action interval param is not of type integer.

3.5.4 – 2023-01-17

Add pre filters during action registration.
Async scheduling.
Calculate timeouts based on total actions.
Correctly order the parameters for ActionScheduler_ActionFactory‘s calls to single_unique.
Fetch action in memory first before releasing claim to avoid deadlock.
PHP 8.2: declare property to fix creation of dynamic property warning.
PHP 8.2: fix “Using ${var} in strings is deprecated, use {$var} instead”.
Prevent undefined variable warning for $num_pastdue_actions.

3.5.3 – 2022-11-09

Query actions with partial match.

3.5.2 – 2022-09-16

Fix – erroneous 3.5.1 release.

3.5.1 – 2022-09-13

Maintenance on A/S docs.
fix: PHP 8.2 deprecated notice.

3.5.0 – 2022-08-25

Add – The active view link within the “Tools > Scheduled Actions” screen is now clickable.
Add – A warning when there are past-due actions.
Enhancement – Added the ability to schedule unique actions via an atomic operation.
Enhancement – Improvements to cache invalidation when processing batches (when running on WordPress 6.0+).
Enhancement – If a recurring action is found to be consistently failing, it will stop being rescheduled.
Enhancement – Adds a new “Past Due” view to the scheduled actions list table.

3.4.2 – 2022-06-08

Fix – Change the include for better linting.
Fix – update: Added Action scheduler completed action hook.

3.4.1 – 2022-05-24

Fix – Change the include for better linting.
Fix – Fix the documented return type.

3.4.0 – 2021-10-29

Enhancement – Number of items per page can now be set for the Scheduled Actions view (props @ovidiul). #771
Fix – Do not lower the max_execution_time if it is already set to 0 (unlimited) (props @barryhughes). #755
Fix – Avoid triggering autoloaders during the version resolution process (props @olegabr). #731 & #776
Dev – ActionScheduler_wcSystemStatus PHPCS fixes (props @ovidiul). #761
Dev – ActionScheduler_DBLogger.php PHPCS fixes (props @ovidiul). #768
Dev – Fixed phpcs for ActionScheduler_Schedule_Deprecated (props @ovidiul). #762
Dev – Improve actions table indices (props @glagonikas). #774 & #777
Dev – PHPCS fixes for ActionScheduler_DBStore.php (props @ovidiul). #769 & #778
Dev – PHPCS Fixes for ActionScheduler_Abstract_ListTable (props @ovidiul). #763 & #779
Dev – Adds new filter action_scheduler_claim_actions_order_by to allow tuning of the claim query (props @glagonikas). #773
Dev – PHPCS fixes for ActionScheduler_WpPostStore class (props @ovidiul). #780

3.3.0 – 2021-09-15

Enhancement – Adds as_has_scheduled_action() to provide a performant way to test for existing actions. #645
Fix – Improves compatibility with environments where NO_ZERO_DATE is enabled. #519
Fix – Adds safety checks to guard against errors when our database tables cannot be created. #645
Dev – Now supports queries that use multiple statuses. #649
Dev – Minimum requirements for WordPress and PHP bumped (to 5.2 and 5.6 respectively). #723

3.2.1 – 2021-06-21

Fix – Add extra safety/account for different versions of AS and different loading patterns. #714
Fix – Handle hidden columns (Tools → Scheduled Actions) | #600.

3.2.0 – 2021-06-03

Fix – Add “no ordering” option to as_next_scheduled_action().
Fix – Add secondary scheduled date checks when claiming actions (DBStore) | #634.
Fix – Add secondary scheduled date checks when claiming actions (wpPostStore) | #634.
Fix – Adds a new index to the action table, reducing the potential for deadlocks (props: @glagonikas).
Fix – Fix unit tests infrastructure and adapt tests to PHP 8.
Fix – Identify in-use data store.
Fix – Improve test_migration_is_scheduled.
Fix – PHP notice on list table.
Fix – Speed up clean up and batch selects.
Fix – Update pending dependencies.
Fix – [PHP 8.0] Only pass action arg values through to do_action_ref_array().
Fix – [PHP 8] Set the PHP version to 7.1 in composer.json for PHP 8 compatibility.
Fix – add is_initialized() to docs.
Fix – fix file permissions.
Fix – fixes #664 by replacing __ with esc_html__.

\n"},"short_description":"Action Scheduler - Job Queue for WordPress","download_link":"https://downloads.wordpress.org/plugin/action-scheduler.3.8.2.zip","screenshots":[],"tags":{"cron":"cron","scheduler":"scheduler"},"versions":{"3.1.6":"https://downloads.wordpress.org/plugin/action-scheduler.3.1.6.zip","3.2.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.2.0.zip","3.2.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.2.1.zip","3.3.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.3.0.zip","3.4.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.4.0.zip","3.4.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.4.1.zip","3.4.2":"https://downloads.wordpress.org/plugin/action-scheduler.3.4.2.zip","3.5.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.5.0.zip","3.5.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.5.1.zip","3.5.2":"https://downloads.wordpress.org/plugin/action-scheduler.3.5.2.zip","3.5.3":"https://downloads.wordpress.org/plugin/action-scheduler.3.5.3.zip","3.5.4":"https://downloads.wordpress.org/plugin/action-scheduler.3.5.4.zip","3.6.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.6.0.zip","3.6.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.6.1.zip","3.6.2":"https://downloads.wordpress.org/plugin/action-scheduler.3.6.2.zip","3.6.3":"https://downloads.wordpress.org/plugin/action-scheduler.3.6.3.zip","3.6.4":"https://downloads.wordpress.org/plugin/action-scheduler.3.6.4.zip","3.7.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.7.0.zip","3.7.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.7.1.zip","3.7.2":"https://downloads.wordpress.org/plugin/action-scheduler.3.7.2.zip","3.7.3":"https://downloads.wordpress.org/plugin/action-scheduler.3.7.3.zip","3.7.4":"https://downloads.wordpress.org/plugin/action-scheduler.3.7.4.zip","3.8.0":"https://downloads.wordpress.org/plugin/action-scheduler.3.8.0.zip","3.8.1":"https://downloads.wordpress.org/plugin/action-scheduler.3.8.1.zip","3.8.2":"https://downloads.wordpress.org/plugin/action-scheduler.3.8.2.zip","trunk":"https://downloads.wordpress.org/plugin/action-scheduler.zip"},"donate_link":"","icons":{"default":"https://s.w.org/plugins/geopattern-icon/action-scheduler.svg"}},{"name":"Incorrect Datetime Bug Fix","slug":"incorrect-datetime-bug-plugin-fix","version":"1.1","author":"Eddie Moya","author_profile":"https://profiles.wordpress.org/eddiemoya/","requires":false,"tested":"3.2.1","requires_php":false,"requires_plugins":[],"rating":100,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"num_ratings":2,"support_threads":0,"support_threads_resolved":0,"downloaded":2886,"last_updated":"2013-01-07 7:49pm GMT","added":"2011-08-23","homepage":"http://eddiemoya.com/plugins/incorrect-datetime-bug-fix-wordpress/","sections":{"description":"

This plugin was create to work around a problem caused by certain configurations in MySQL that lead to several odd symptoms including but not limited to:

Loss of ability to create new posts
Loss of ability to update posts
Errors regarding invalid timestamps
Admin interface reverts to lowest permissions ex:‘Publish’ button says ‘Submit Draft’.

In addition, this problem is often accompanied by an error like the following:

WordPress database error: [Incorrect datetime value: '0000-00-00 00:00:00' for column 'post_date_gmt' at row 1]\nINSERT INTO 'mg_posts' ('post_author','post_date','post_date_gmt','post_content','post_content_filtered','post_title',\n'post_excerpt','post_status','post_type','comment_status','ping_status','post_password','post_name','to_ping','pinged',\n'post_modified','post_modified_gmt','post_parent','menu_order','guid') VALUES (’1′,’2011-08-23 03:32:43′,\n’0000-00-00 00:00:00′,”,”,’Auto Draft’,”,’auto-draft’,'post’,'closed’,'open’,”,”,”,”,’2011-08-23 03:32:43′,’0000-00-00 00:00:00′,’0′,’0′,”)\n

The inability to pass zero dates breaks the ability to actually create a new post, but it also seems to have the odd secondary effect of confusing the heck out of nonces (noces are a security feature), probably because they too rely on timestamps.

This plugin strips out the sql_modes listed below from @@SESSION, thereby eliminating the problem while only effecting database sessions WordPress starts and not the whole database.

Explanation and history of the problem

The cause of this problem stems from an old (soon to be deprecated) odd behavior/feature of MySQL which WordPress came to depend on. My understanding is that it stems from problems in MySQL with regard to using the MySQL NOW() function in some contexts – so as a workaround it was decided that if a date of all zeros was entered on a column that was set as NOT NULL, then that date would not be rejected, but instead would be converted to the current date – to mimic NOW().

Subsequently this method was marginalized as generally a bad idea – and now values exist for a setting called sql_mode, which turn this behavior off and force errors when a null value is passed to a NOT NULL field. In many cases when there is an actual DBA in charge of the database, they will assign these values to the production database to force what outside of MySQL would be normal SQL behavior.

There are 3 sql_modes which will trigger the error by disabling the ability to enter zero dates.

NO_ZERO_DATE
NO_ZERO_IN_DATE
TRADITIONAL

It’s worth mentioning that the ALLOW_INVALID_DATES mode does NOT solve the problem, even though by the name of it, it would seem that it might.

The solution

This plugin solves the problem with minimal effect to the database environment. All this plugin does it check to see if the sql_modes in question are set, and if they are, it removes them.

Importantly, this plugin changes @@SESSION.sql_mode and not @@GLOBAL.sql_mode. By changing sql_mode via the session, it only takes effect on each specific connections WordPress makes with the database rather than changing it for the entire database permanently – as such this will have no effect whatsoever on any applications that might happen to be using the same database.

Other manifestations, alternative solutions.

WARNING: Whenever applicable, consult your DBA before making any changes to production databases.

This problem may (I have no idea) in fact be more common during installation. The errors are different, and although I have seen them, I do not have them handy at this time. In any case, if the sql_modes are set during installation – the process will fail from the start – because of this, it is my presumption that anyone encountering the errors as described above – has probably recently migrated to a new database, or perhaps recently acquired an enthusiastic new DBA who has made some changes.

This plugin DOES NOT FIX this problem for those encountering during installation – thats impossible because WordPress ignores all plugins during installation – so there is no way to hack around it via plugin and fix it before installation occurs.

If you are encountering this problem during installation you will need to find an alternative way to remove the modes. If this is a production environment this may require the cooperation of a DBA who may not like the idea. If met with resistance, I suggest the asking for the modes to be temporarily removed for installation, and then set back after its dont – at which point this plugin will handle the problem from then on.

If your encountering this locally, or on a environment whose database you have access to modify, you will want to make as few changes as possible, so go to whatever interface you use (command line, phpMyAdmin, whatever) and run this line of SQL:

SELECT @@GLOBAL.sql_mode;\n

This will show you all the sql modes currently defined. Copy all them them but if you have NO_ZERO_DATE, NO_ZERO_IN_DATE, or TRADITIONAL remove them. Then update sql_mode with the remaining modes as such:

SET @@GLOBAL.sql_mode = \"STRICT_TRANS_TABLES,STRICT_ALL_TABLES,ERROR_FOR_DIVISION_BY_ZERO\";\n

Please don’t simply use the sql_mode definition I have shown above, this is only an example – be sure to use the modes from your database configuration. Remember to keep everything together NO SPACES ALLOWED in the definition.

Finally, if your just working locally and don’t care about these sql_modes, you can just clear them all.

SET @@GLOBAL.sql_mode = \"\";\n

This will do the trick but is absolutely not recommended as a fix for production sites that might share environments.

Irrelevant Note: I struggled with naming this plugin, and settled on the terminology seen in the error message.

\n","installation":"

Upload plugin-name.php to the /wp-content/plugins/ directory
Activate the plugin through the ‘Plugins’ menu in WordPress

Will this fix sql_mode during installation?

No, plugins are not loaded during installation. For alternative solutions see
\n“Other manifestations, alternative solutions” on the plugin home page

Will this effect other applications that might run on the same database, and depend on these sql_mode settings?

No, it uses @@SESSION.sql_mode to change the settings for each WordPress session individually.

How do I undo what this plugin does?

Just turn off the plugin – because it uses @@SESSION, the changes wont persist.

If you’ve made other modifications explained in this plugin’s documentation, you will have to run similar SQL commands to apply the old settings.

\n","changelog":"

1.0

Initial plugin release

1.1

Bug fix: Corrected the way the plugin used wpdb::prepare().

\n"},"short_description":"This plugin was create to work around a problem caused by certain configurations in MySQL that lead to several odd symptoms including but not limited …","download_link":"https://downloads.wordpress.org/plugin/incorrect-datetime-bug-plugin-fix.1.1.zip","screenshots":[],"tags":{"mysql":"mysql","no_zero_date":"no_zero_date","no_zero_in_date":"no_zero_in_date","sql":"sql","sql_mode":"sql_mode"},"versions":{"1.0":"https://downloads.wordpress.org/plugin/incorrect-datetime-bug-plugin-fix.1.0.zip","1.1":"https://downloads.wordpress.org/plugin/incorrect-datetime-bug-plugin-fix.1.1.zip","trunk":"https://downloads.wordpress.org/plugin/incorrect-datetime-bug-plugin-fix.zip"},"donate_link":"http://eddiemoya.com","icons":{"default":"https://s.w.org/plugins/geopattern-icon/incorrect-datetime-bug-plugin-fix.svg"}}]

no_zero_date

Nextend Social Login and Register

Action Scheduler

Incorrect Datetime Bug Fix

Get New Themes & Resources