Ramona

Hi @pedrorinconb

I wasn’t able to load the https://www.tank.nl/ site. Are you trying to create something like this?
https://alvarotrigo.com/fullPage/#page2/1
I’m sorry but this kind of behavior can’t be achieved with Smart Slider.

We also received your message in our ticket system. Since you’re a Smart Slider 3 Pro user please keep using that system for any further questions or suppor request in the future.

As per forum rules, commercial products are not supported in these forums. So we can’t support pro customers here.

Each of your links contains the following attribute: data-wpel-link which seems to be related to this plugin:
https://www.ads-software.com/plugins/wp-external-links/

Looking at its screenshots it has an option to make all internal links open in a new tab. So I recommend making sure that no internal links are set to open in a new tab at this plugin’s settings.

Hi @sayantansdas

We’re storing one version of the slider so from our end all changes are immediate and aren’t revertable without a user action. So, if you delete or change an image and save it it stays that way until the image is placed back manually by the user.

If you check this slider at your backend, do you see the “wrong” image there? The problematic image (wp-content/uploads/2022/10/TP-Resize-banners-Oct2022-The-label-2022-Collection-v1.png) seems to be the Content layer’s background:
https://smartslider.helpscoutdocs.com/article/1810-content-layer
of the “Tag Privé the label” slide: https://imgur.com/HYbZCcW
So please make sure no image is set there.

If this image is not set anymore at your backend, then it should not appear in the slider either.

If the image is not in the slider anymore and there are some times when it actually doesn’t appear, but after that it just “appears by itself” that suggests some kind of 3rd party cache gets mixed up and starts to load an older version of your site. This older version of your site has an old version of your slider where the old image was still used. That is why the slider attempts to load it, because in that old version that loads from the cache this image was still used.

What I recommend for now is to make sure that the correct image is set for your slider at its backend, then clear all your caches and temporarily (for a couple of days) disable all caching on your site. This should prevent the caches from loading the old slider version. Then enable your cache, clear it again and see if the issue comes back.

Do you have more than one caches on your site? Because using multiple caches can cause weird problems like this, so I recommend sticking with only one caching (the one that helps your site’s speed the most) and leave the others disabled.

Hi @evenstarhq

I checked your site and currently there are no texts on the slider even on the desktop version: https://imgur.com/zhHZhSD
Are you checking the site as a “logged in” user on desktop? Because generally caches don’t run for logged in users, which would explain why everything appears to be fine there.

Looking at the page I think the problem happens because of some kind of optimization, as when adding a query string after the URL (e.g. ?asdf) the slider loads just fine. Try running a plugin and theme conflict test:
https://smartslider.helpscoutdocs.com/article/1735-how-to-do-a-plugin-theme-conflict-test
and make sure you check your site as a non-logged in user.

You could also try to excluse us from WP Rocket’s optimization:
https://smartslider.helpscoutdocs.com/article/1976-cache-or-minification#wp-rocket

But since you’re a Pro customer, please contact us directly for any further support at: https://smartslider3.com/contact-us/support/
Feel free to refer to this topic.

As per forum rules, commercial products are not supported in these forums. So we can’t support our pro customers here.

Hi @wordpresswizard1001

I checked your site but I wasn’t able to reproduce this problem.

In any case, probaly the 400MS (which is 0.4 seconds) time is not enough for the video to start and if the video does not start then the “Stop on media” won’t have any effect.

What I suggest is to rather keep the 8000MS autoplay interval (so change the Slide level autoplay interval back to 0) and at your YouTube video layer:
https://smartslider.helpscoutdocs.com/article/1846-youtube-layer
change the “When ended” value to “Go to next slide”. This way, when the video finishes playing the slider will automatically move forward. Otherwise (depending on your autoplay configuration) it would wait for the autoplay interval before switching forward.

Hi @najeeborangerie

The Align thumbnails > Center option can only work of your thumbnails take up less space than what’s available for them. So e.g. if you have 1200px space to display the thumbnails and the thumbnails themselves take up less than 1200px space then you can center them. But if the thumbnails need more space then what’s available then then the Align thumbnails will not be able to do anything, as there’s no empty space to align the thumbnails within.

That being said, I’m sorry but we don’t have option to align the active thumbnail only. The position of the thumbnails are fix within the thumbnail container, so they can’t be moved around based on the position of the currently active thumbnail item (or anything else).

Hi @christopheran

I’m sorry but we don’t have any kind of option to disable or modify the default WordPress login or registration process.

WordPress does have an option to prevent new registrations at WordPress menu > Settings > General >Membership –?Membership Anyone can register. However this option will not prevent people who already have an account to log in using a regular WordPress form. From our end there’s no option to prevent that, so you’ll either need a plugin or write some custom codes for that. Please note that we’re unable to provide support for any kind of custom coding.

Also, you should know that by default Nextend Social Login inherits the WordPress Membership setting, which means if the “Anyone can register” is disabled Nextend Social Login won’t allow registrations either. If you want to allow the registration through Nextend Social Login only, then you should go to Nextend Social Login > Global Settings > General tab > Membership and set it to Enabled:
https://nextendweb.com/nextend-social-login-docs/global-settings/
In this way users with social providers will be able to login even when the default WordPress membership is disabled.

Hi @jason_hayes

Did you see any mentions of “nextend” in your theme’s files? If not, you could try running a plugin and theme conflict test: https://smartslider.helpscoutdocs.com/article/1735-how-to-do-a-plugin-theme-conflict-test
just in case some 3rd party inserts the button.

Hiding the button with CSS is also a good idea if it’s okay for you that the button “is there” even if not visible. What’s the CSS you used? Based on the theme’s demo page: https://demos.appthemes.com/classipress/profile/
the buttons should be inside the #profile form element, so using a CSS like this one shouldn’t affect the “sidebar” button, as they’re in separate container:

form#profile .nsl-container {
    display: none;
}

Hi @jason_hayes

Does your theme have any kind of integration with Nextend Social Login? Perhaps this button is the result of their integration.

Did you use your theme’s functions to create the “SSO settings” section? I’m wondering if your theme maybe has a hook that is fired at both of your “SSO settings” section and for some reason, at the “Extended Profile” section, too.

Or, if you didn’t use any hooks, perhaps it would worth a shot to download your theme from your site via FTP and search through it’s files as you can see here:
https://smartslider.helpscoutdocs.com/article/1935-troubleshooting-with-your-browser#search
and search for, for example, “nextend” which would display all results for our shortcode or PHP code so you could see if there are any mentions of them besides your “SSO settings” code. If you have a child theme it would also worth searching through that.

Hi @illustrata

The problem on your site happens because of a 3rd party optimization plugin that modifies the code of the images (as if it was trying to lazy load them) but it fails to add the proper images back to the slider.

We generally don’t recommend using any kind of 3rd party optimization with the slider, because they usually cause problems like this.

I can see that the images are coming from Shortpixel URLs when the images works so I think they might have some kind of lazy loading that causes this to happen. Can you try temporarily disabling Shortpixel and clear the caches of your site (if there’s any) and see if that makes any difference?

Usually optimization plugins have some kind of option to exclude images which have a certain class. We add the following class to all of our images: skip-lazy you could try adding this class for exclusion.

Hi @jakub78

I’m from Smart Slider’s support and while I’m not familiar with Adminimize I can tell you that by default Smart Slider is only accessible for admin level users. Based on Adminimize’s description, it can enable/disable the already available options for users.

This part of the plugin’s description makes me think that:

There are lots of things in the WordPress admin area that your users don’t need to see or use. This plugin help you to hide unnecessary items from WordPress admin area.

So I think the main problem is that the shop manager role does not have access to Smart Slider at all, which can be the reason why Adminimize doesn’t do anything.

To be able to make other user roles access Smart Slider, they need to be given the proper capabilities to manage the slider:
https://smartslider.helpscoutdocs.com/article/1983-how-to-give-access-to-smart-slider-for-non-admin-users#wordpress

Can you double check that the Shop manager role has the necessary capabilities to access Smart Slider?

Hi @aamir2007

Yes, we’re loading our CSS and JS codes on all pages because the login buttons can also be published by simple HTML. If any button is published with HTML, then we don’t have any way of knowing which page contains our login buttons from the PHP side, that is why the codes appear everywhere.

That being said, you can exclude our scripts and styles by doing a condition check via PHP. Please note that, we can not provide support for custom coding, but here is an example that shows how you can do that:

$pageID = get_the_ID(); 
if ($pageID !== 61) {
    remove_action('wp_head', 'NextendSocialLogin::styles', 100);
    remove_action('wp_print_scripts', 'NextendSocialLogin::nslDOMReady');
    remove_action('wp_print_footer_scripts', 'NextendSocialLogin::scripts', 100);
}

Hi @alexg9

Do you have any enabled providers? https://imgur.com/XPkDv5w

Nextend Social Login can only display the login buttons on the frontend if there are any enabled providers. So first I recommend making sure that you have at least one enabled provider.

Hi @pao2

That’s the correct behavior. The nsl_registration_form_start is a custom action that Nextend Social Login fires when its own registration starts. No Nextend Social Login related action runs during a normal WordPress registration process, so you can’t use our hooks to modify the default WordPress registration behavior. All our hooks only run during the social registration (or login, depending on the hook) process.

If you want to ask custom data during the normal WordPress registration then you’ll need to write custom codes to hook into the normal WordPress registration flow. Try looking around here: https://developer.www.ads-software.com/reference/hooks/ to find the hook you need.

Please note that we’re unable to provide any kind of support for custom coding.

Hi @ecoshopn

I think the problem on your website is caused by a firewall ( probably ModSecurity ) that blocks requests when they contain certain strings, more specifically “.profile”:

• https://nextendweb.com/nextend-social-login-docs/google-403-and-404-errors/

With ModSecurity this is actually a very common problem, as they have this string on their black list, however one of the scopes that Google use:

• https://www.googleapis.com/auth/userinfo.profile

also contains that “.profile” string, which means the OAuth requests of Google will be blocked.

You can easily check if this is you issue even without Nextend Social Login. You just need to open the /wp-login.php page with the .profile string appearing in a GET parameters value, e.g.:

• /wp-login.php?test=.profile

The request will be blocked and will return a 403 or 404 error. But if you make it no longer contain the blacklisted “.profile” string, e.g. you remove the last “e” character:

• /wp-login.php?test=.profil

that will load the /wp-login.php page just fine.

If this is your problem, you should get in touch with your host and ask them to disable the rule that causes the the 403/403. They have an error log that contains all kinds of error messages, including the ones triggered by the firewall. And that should contain the rule ID that causes this 403/404 error.

Once that rule is removed, the problem will no longer occur.

Or my other idea is that perhaps something (like a 3rd party) prevents us from finishing the OAuth communication. So if the previous test wouldn’t be any different for you, what I suggest is to configure our “OAuth redirect uri proxy page” and “Page for register flow” settings. Both of these can be found at our Global settings > General tab: https://nextendweb.com/nextend-social-login-docs/global-settings/

And you should configure them this 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 – 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 ( or in your case “loginwp-chistudio-admin1234” ). 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 that message that you saw earlier, and there you can see all the steps, but actually, you can find the redirect URLs in the Getting Started section of the providers, too. )

This way we will handle our codes over these 2 pages that you created, instead of the /wp-login.php. So the OAuth process should be able to finish.