Robert

Hi @joandelfin

We do not have any actions or filters that would help with this. We register users the same way as WordPress does, so the default “register_new_user” action is fired. You could try getting the attachment id over that using the global $wpdb variable, but we override the default avatar, so I am actually not sure if you would get the result you are looking for. Could you please let me know how you intend on using the id?

Hi @chengjianping

If I take a look at the page:
https://luxesensychic.com/wp9217
it does not exist. So I assume you already disabled this page.

And I see in the meantime you configured the Oauth redirect uri proxy page, which will make Nextend Social Login handle its login flow over that page. This will make the redirect uri change as well, which should resolve the problem you saw. That notice appears when the stored redirect uri is different to what you need to use. For example, by default we handle our flows over the /wp-login.php page, but if you have a url that points to the /wp-login.php page, then we could discover that, and suggest that for the redirect uri, which could result in a problem like this. The solution is to either disable the wp-login.php page, and keep the other login url, or a more practical solution is to configure our “Oauth redirect uri proxy page” and “Page for register flow” settings. Both of these can be found on the general tab:
https://nextendweb.com/nextend-social-login-docs/global-settings/

And you should configure them in the following way:

• For the Page for register flow: You should create a new page and add the shortcode into it: [nextend_social_login_register_flow] then select that page for this setting. Extra information before the registration with social login – like Terms and Conditions, Username, Password, Email – would be asked on this page. ( Make sure you don’t use this page for anything else! )
• For the OAuth redirect uri proxy page: You should create another new and completely empty page ( that you won’t use for anything else either ) and select it as OAuth redirect uri proxy page. Once it is done, the redirect URL of each configured provider will change, as the OAuth flow will be handled over this new page instead of the /wp-login.php page. So, you will need to add the new redirect URLs into each of your configured Apps again. ( Nextend Social Login will also warn you about this with a message, where you can see all the steps, but actually, you can find the redirect URLs in the Getting Started section of the providers, too. – The redirect URLs are the URLs that usually contain this query string: “?loginSocial=” )

Additionally, you must ensure that both of these pages are excluded from all kinds of caching, as we need to run PHP codes on these pages, which won’t be possible if they are cached. I see you already configured the Oauth redirect uri proxy page, but it appears that you either selected the same page for the Page for register flow, or you did not select anything, and like that the social login does not work when you want to register.

Let me know if you still have problems after this!

Hi @gwenm

Unfortunately, Facebook as of February 1, 2023, requires Business Verification in order to have access to the Facebook login feature. If you do not have the business verification done, then only those will be able to use the Facebook social login, who have a role assigned to them in your Facebook App (like you as the owner of the app), so random users will not be able to use it, and they will receive an error.

Hi @calado

The slider cannot work properly in the Elementor popup due to how it works, but as you see here:
https://smartslider.helpscoutdocs.com/article/1791-smart-slider-3-elementor#elementor-popup
you could try publishing the slider as an iframe, and see if it works fine afterwards. But either way, please keep in mind that as we note in the documentation above, we do not support this use-case.

Hi @locha9066

We need to load our CSS and JavaScript to other pages too, as the social buttons can be published not only with shortcode but with normal HTML as well.
So we can not know in advance the pages where the social buttons will appear and for that reason, we need to load our scripts and styles. If you do know that you will not have any buttons elsewhere besides the /my-account page, then with some custom code you can remove our styles and scripts, but I personally do not think you actually need to do it, as the impact of those are so minimal. Anyway, if you really want to remove them, you can do it with a code like this:

add_action('wp', function () {
    if (class_exists('NextendSocialLogin', false)) {
        global $pagenow;
        $whiteListedPageIDs=array(10,15);
        
        if('wp-login.php' !== $pagenow && !is_page($whiteListedPageIDs)){
            NextendSocialLogin::removeLoginFormAssets();
            remove_action('wp_head', 'NextendSocialLogin::styles', 100);
            remove_action('wp_print_scripts', 'NextendSocialLogin::checkJqueryLoaded');
        }
    }
});

This code will remove our styles and scripts from everywhere, except:

• the /wp-login.php where we display the social buttons by default
• and from the pages with the IDs: 10 and 15

Of course, you can modify the condition according to your needs, however please note that we are unable to provide any kind of support for custom coding.

Hi @gianniggb

Could you please get in touch with us over our ticket system?:
https://smartslider3.com/contact-us/support/
And we’ll continue debugging there.
In the meantime, please also try if the issue happens with only Smart Slider 3 and Divi enabled.

Hi @pigsound

I was not able to reproduce this issue on WordPress 6.7 and PHP 7.4.

I would recommend doing a conflict test:
https://smartslider.helpscoutdocs.com/article/1735-how-to-do-a-plugin-theme-conflict-test
to find out what exactly causes it. It is possible a 3rd party plugin causes the issue.
For example, we have seen an issue with the WP External Links plugin before:
https://wordpress.org/support/topic/conflict-with-wp-external-links/

If it is truly a conflict between the theme and Smart Slider 3, please let us know what theme you are using exactly, and we’ll take a look.

Hi @lopezj

Are you using the latest Smart Slider 3 version? Just in case do a reinstallation first:
https://smartslider.helpscoutdocs.com/article/1717-wordpress-installation#ftp

If this does not resolve the issue, then please go to a page where the issue happens, and open up the browser developer console:
https://developer.chrome.com/docs/devtools/open
https://firefox-source-docs.mozilla.org/devtools-user/browser_console/index.html
(or F12 -> Console)
Once the console is open, refresh the page, and see what error message is shown.