Robert

Hi @jkdsouljah

Please check these 2 options:
1. The “store” option on the Privacy tab:
https://nextendweb.com/nextend-social-login-docs/global-settings-privacy/
and ensure “Avatar” is selected there.
2. The “Sync data” settings for Google:
https://nextendweb.com/nextend-social-login-docs/provider-google/#sync_data
and ensure the “Sync fields” checkboxes are enabled.

Internal app type shouldn’t make a difference, it only determines who can use your app. So with an internal app type, anyone that is part of your organization, but not random users.

We store the connection between the social media accounts and the WordPress accounts in this table:

• <wp_prefix>social_users

e.g.:

• wp_social_users

Here is the explanation of the database fields:

• social_users_id – primary key of the social_users table, with auto-increment
• ID – this is the User ID of the WordPress account that was linked to the social media account
• type – identifies the provider the WordPress account has been linked to ( it says “google” if it is a link connected to Google)
• identifier – the unique identifier within the social app ( e.g. the ID of a Google user ). We usually use the original social media ID returned by the provider, but in the case of some providers, that won’t be unique, so we had to make it unique with a custom logic ( currently only the Slack provider has such custom logics ).
• register_date – contains the date when the user registered with a certain provider. (If it is NULL then the user registered with either a traditional registration form or with another social provider )
• login_date – the date the user logged in the last time
• link_date – the date when the user linked the social media account to the WordPress account

So like this with a custom SQL query you can find out if the given user has the provider you are looking for.

Hi @hasinthawk

You can enable the “Show linked providers” option on the General tab:
https://nextendweb.com/nextend-social-login-docs/global-settings/
This will add a new column in the Users table, that shows what providers are linked to the given WordPress account. This shows manual links as well, so not just registration.

Or if you need to run some code if the user registered with the social login, then in our developer docs:
https://nextendweb.com/nextend-social-login-docs/backend-developer/
You can see the “nsl_register_new_user” action. This is fired whenever we register a new user on your website with either of the providers. However, please note that we do not support custom coding.

At the moment, we can see on the page that Litespeed cache delays the loading of the JavaScript file, which contains our code, and also delays the loading of the images used in the slider, until the page is hovered over. Even if the cursor is right on the page, these files are still delayed, so currently we see the problem with Litespeed cache. You could turn it off temporarily to see if that resolves the problem. If it does, you can find out what setting does it by enabling the plugin again, and disable its settings one by one till you find out which does this delayed loading. The option will be called something that resembles delayed loading. I am not familiar with their settings, but in their docs I found “Load JS Deferred”:
https://docs.litespeedtech.com/lscache/lscwp/pageopt/#js-settings-tab
Possibly that is causing this.

In page speed tests, you often get a better score because of such optimization solutions, but in reality, your content is displayed more slowly due to delayed file loading.

Hi @wonderwooman

Smart Slider loads in a way that it needs to run its JavaScript codes to show a slider and this takes time. Some of these codes can run during page loading, but others can only run after the page finished loading. Because of this, our slider will be one of the last things that shows up on your website. We can’t really do anything with this, because we are running our codes as soon as possible. So your entire website’s speed defines how long it takes for a slider to show up. Your slider is probably optimized, so from our end there are no other settings to improve on this, but something is loading for long on your website. I recommend taking a deeper look at the page where this 10+ second load problem happens. You can use Chrome to see what is loading for how long into your website:
https://smartslider.helpscoutdocs.com/article/1925-how-to-speed-up-your-site#why-slow
If you eliminate long-loading files on the page, our slider will also appear sooner.

Hi @hasinthawk

We register the users the same way as WordPress does, with a random password initially. Then the password set notification goes out from WordPress to change the password if the users wants to.

Hi @emax3

The problem is caused by this custom CSS:

* {
    margin: 0 auto;
    text-decoration: none !important;
    outline: none !important;
    -webkit-font-smoothing: auto;
    -moz-osx-font-smoothing: auto;
    -webkit-font-smoothing: antialiased;
    text-rendering: optimizelegibility; 
}

More specifically, by the margin. This is code is from this file:
https://www.aiaspalermo.org/nuovo/wp-content/themes/adventz/assets/css/adventz-custom.css?ver=1728307365

It is generally a bad practice to add margin to the * selector, as that is way too generic, and will have an undesirable result most of the time. So you should remove it from there, or modify the selector, so it targets exactly what you need, and that will resolve the problem.

Hi @jimcee

Here you can find the most common ways why the shortcode appears instead of the slider:
https://smartslider.helpscoutdocs.com/article/1945-shortcode-displays-instead-of-the-slider
You mentioned the problem only happens with query strings, so I assume it is probably a result of a 3rd party. So first 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 causes it exactly.

Hi @danieldumitruavram

Please note that we are unable to provide support for custom coding of any kind.
Currently, your code will return the unchanged notification email in our case, as the condition you set will be evaluated to true.

If you cannot seem to make this happen, then I would rather recommend getting the Pro version, or hire a developer who can make the code for you.

Hi @safi2266

I’m sorry, but currently we don’t have plans for Google One Tap login, and as such there is no way to enable it either. The problem with it is, that our entire system was designed for OAuth2 authentication:
https://datatracker.ietf.org/doc/html/rfc6749
and that is used by all our providers. Google One Tap would need a different type of authentication, which would be very difficult to implement into our code. So for now we do not support Google One Tap.

Hi @confusedneedhelp

Sure, I restored it now, so you should be able to access it again on the original link:
https://www.dropbox.com/scl/fi/qjpvap6mo00r4wftwuavz/nextend-social-login-feature-NSLDEV-649-bfcache-cannot-work-because-of-broadcastchannel.zip?rlkey=mggie9mk6tevzx7896tlomjtg&st=h9sl5eip&dl=1

Hi @jfoc

In the debug mode we only try to check if your server is able to communicate with the servers of the provider, to do this we send a text request, and we dump out the response. All that matters there is if you receive the Network connection successful message at the top of the page or not, everything else are just the verbose text of the API response, so you can ignore that. I do not know if your message says the connection is successful, as you included only the error message part, but if you see “Network connection successful *” notice at the top, then you do not need to worry about this debug mode.

You mentioned all settings are verified, so if you haven’t done already, please enable the provider, and you can check it on the /wp-login.php page whether the login with the social button works or not. If it doesn’t, let me know what error you get.

And if you would like to publish the buttons somewhere else, in the Free version you can use the shortcode for that:
https://nextendweb.com/nextend-social-login-docs/usage/

Hi @dragansk!

Thanks for contacting us!

I’m sorry, but in WebView browsers we hide the Google button on purpose, as Google doesn’t allow using their OAuth endpoints over WebView, since according to them that is not secure ( https://auth0.com/blog/google-blocks-oauth-requests-from-embedded-browsers/ ).

This means whenever a user tries to connect with Google while they are browsing over WebView, they would only see an error message that states this problem. So because it cannot work, we are hiding the Google button on WebView browsers by default. However, since Nextend Social Login 3.1.12, we have a new option – Unsupported WebView Behavior:
https://nextendweb.com/nextend-social-login-docs/global-settings/#unsupported-webview-behavior
With this option you can either remove the buttons (default behavior), or you can disable them (in this case the buttons will still show up, but will be grayed out), and if the user still clicks on the button it will show an error notice stating this limitation.

If you have any questions, let me know!

@julescameron

On second thought, we have managed to find out what the problem is. The problem is caused by the fact that you have set the slider size similar to the browser’s size. So these are the events that lead to the problem:

• You need to look at the slider on a browser size that is just a little bit smaller than the slider itself. Like this the slider’s height is e.g. 5px bigger than the browser’s. Because of this, the browser’s scrollbar will appear.
• Since the scrollbar appeared, the width of the browser gets reduced by that much.
• Our slider by default uses a size ratio to determine the size. So since the browser became smaller in width, the slider become smaller in width and height to keep the size ratio.
• Since the slider’s height has become smaller (and you have no other content on the page), the slider is no longer bigger than the browser, thus the browser hides the scrollbar, since there is nothing to scroll to.
• And the issue from now on repeats, since that way the browser becomes bigger -> the slider becomes bigger in width and height due to the size ratio, and we end up at the beginning of the cycle again.

There are 2 possible solutions to this:
1. Use the following CSS code to always show the scrollbar:

body{
   overflow-y: scroll;
}

You could go to the slider’s settings -> Developer tab and insert the code into the CSS field:
https://smartslider.helpscoutdocs.com/article/1806-slider-settings-developer#css

2. In the Pro version we have a Fullpage layout:
https://smartslider.helpscoutdocs.com/article/1777-fullpage-layout
which achieves the design you originally intended to achieve, so it makes the slider as big as the browser.

However due to the forum guidelines, we can only provide support for the Free version here, so in case you have further questions related to Pro features, please rather contact us here:
https://smartslider3.com/contact-us/support/

Hi @tmora

The entire error message is rather strange. It refers to a function called shmop_delete:
https://www.php.net/manual/en/function.shmop-delete.php
We do not use this in our code, or any low level memory management function for that matter, so our code might have been modified somehow on your website. First, please check this file:

• wp-content/plugins/nextend-facebook-connect/includes/oauth2.php

And go to line 220. You should see this:

        if (function_exists('random_bytes')) {
            return $this->bytesToString(random_bytes(self::CSRF_LENGTH));
        }

Do you see the same code part as above? According to your error message it looks like random_bytes might have been replaced by this shmop_delete funciton.

If that is the case, please delete your current Nextend Social Login installation, and install it again. Your plugin settings will stay, so don’t worry about those.

If the problem still appears afterwards, then if you make a test php file (e.g. test.php) with this code:

<?php
var_dump(random_bytes(32));

And open this test file in your browser, do you see the problem there? And also please check this code as well:

<?php
var_dump(substr(bin2hex(random_bytes(32)), 0, 32));

If you see the error still, then we suspect that somehow the random_bytes function is incorrectly configured, or an issue similar to it.