kilianso

Hey @laszloszalvak

Thanks for the quick response. Oh good catch! Since i am the admin of the facebook app, facebook login worked for me all the time. Should have tested with other users before launching. ??

Anyway, i’m going to submit the business for review and check wether this resolves the issue.

But it’s still strange that my profile picture can be sideloaded after completing the registration even though the image URL is invalid during the registration flow. Something is sketchy. I’ll figure it out. Thanks for the help!

Hey Chris. Your plugin throws an error 500 on my class based theme setup. I’m loading Timber through composer and instantiate it like this directly in the functions.php:

require_once( __DIR__ . '/vendor/autoload.php' );
$timber = new Timber\Timber();

All the other classes are loaded with autoload. Does this have an impact, or am i missing something else? Any hint would be appreciated.

Hey Laszlo

Great answer! Thank you.

One more follow up.

1. You write:

If you are not sure about the available keys, then you could check them in the getAuthUserData() function of each providers

How? Where is this documented? If i just do $provider->getAuthUserData() without params, it fails since it expects a key. But how do i get those keys and aren’t they normalized across providers through your plugin? I mean, let’s say the key on Tiktok is firstName and on Google it’s first_name, would i need to write additional logic to uniform the data for displaying, or do your plugin take care of that? And is this even the case or is it safe to just call $providers->getAuthUserData(‘first_name’) across all providers?

2. And what about the Avatar? How can i display that one on e.g. the page for register flow?

3. Wouldn’t it make sense to put all the data the provider offers in the $userData object? I mean userId, avatarURL, first_name, last_name, username, email… just everything. What’s the reason of separating these things even though the data is available anyway?

Thanks a lot for your amazing support!

Okay so i figured out, what’s causing the validation problem. Leaving that here in case someone or you @laszloszalvak is running into the same issue.

On single pages and single posts i’m using the first few words of the content as the meta description. This is also the case for a page that is set as “page for register flow.”

Now since Nextend is dynamically prepending html to the content to style and output validation errors, it interferes with the meta description mechanism. Causing a semantic error where html is not getting stripped and therefore, the layout breaks. Even using striptags does not help and the html by Nextend persists in the meta description.

This could also cause conflicts with SEO plugins.
So my (clearly not perfect) solution is to check if the slug is the page for register flow and then just output a static description. This is resolving the issue and the form validation appears at the right spot with the right styling of Nextend.

Few more questions:
1. How can i overwrite the form or parts of it? Like adding additional CSS classes to the submit button or even replace it entirely?
2. How can i display data on that page for register flow, that already has been fetched from social media? E.g. I’d like to show a page that says: “Complete your registration” where you can already see your profile image, first- and lastname and nickname but then, you need to fill out additional fields to submit your registration.
3. How can i display a field like “nickname” and if already set, let the user change it in that moment?
4. How can i change / style that “Hold on” overlay that appears before redirect?

Thank you so much! Fantastic support ??

• This reply was modified 2 years, 6 months ago by kilianso.
• This reply was modified 2 years, 6 months ago by kilianso.
• This reply was modified 2 years, 6 months ago by kilianso.
• This reply was modified 2 years, 6 months ago by kilianso.

Hey @laszloszalvak

No, i did not made any changes. Just copied your example code. The problem remains the same.

Where do you handle this error object?

Hey Laszlo

Thanks for your fast answer. Regarding the form validation: It does something really strange. It seems like the validation error is placed in the head of the site rather than within the form container. This causes some weird glitch where all the other head stuff is placed within body as well.

Additionally, the form validation does not appear within the form and the form labels (without inputs) are repeated on top of the page.

Check out this screensshot:
https://ibb.co/6FDVRZt

I don’t use the OAuth redirect url proxy page. Just a custom page for register flow.

Hey Laszlo

Thanks for the tips.

I was able to set it up and did a test using your “favorite color” example. Now since i’m using a custom page (user-signup-additional) for the register flow, i’m struggling to control the form validation.

My error messages are placed directly after the opening body tag causing a strange visual result. How can i control the position of validation error messages? Like directly below the affected form field?

And what would be the recommended approach if i have a more complex form and don’t want to pollute the the nsl_before_register with all the additional form markup? As an example, i’d like to let new users set a country from a dropdown and based on the country, a city dropdown should update. Building that on top of the example showed in your developer docs is just not feasible for this kind of form logic. Also, i’d like to have a custom submit button and form layout. So basically a entirely custom form to add additional fields before completing registration.

I’m using Timber/Twig for rendering. Is there a way to just setup a template and pass data from and to the Nextend registration flow?

Many thanks
Kilian

• This reply was modified 2 years, 6 months ago by kilianso.
• This reply was modified 2 years, 6 months ago by kilianso.
• This reply was modified 2 years, 6 months ago by kilianso.

Yes, it is the same. I’m pretty sure it’s not a license problem. There must be an issue with the resource / files / URL of this update package. As written in the error message: Update package not available. I’ll get in touch with the support.

Hello. I tried that and it’s not working. The license key is used on one domain and it’s valid.

Nevermind, i think i just found the solution on my own. https://nextendweb.com/nextend-social-login-docs/backend-developer/#custom-fields

Hello @lukecarbis

Thanks for the support and the gist.
It’s perfectly working now! For some reasons, I have to add /website/ to the URL in order to make the images load. It’s where WordPress is installed in a subdirectory. I don’t know why I have to add it here, but at least it’s working.

Thanks!

I tried now every single thing from your documentation.
Using postman, implicit or not, redirect url or not, all grant types available in free version and it’s just not working anymore! I made no changes at all and all off the sudden it just stopped working since the i updated WordPress. This breaks our whole website functionality.

Can you please give a PRECISE step by step auth workflow using the FREE version of your plugin. I’m trying to access the WPAPI from an external tool using your plugin.