hectavex

Good question…I might need to add an option for this. We have the option for Redirect after login, but not sure this works for Registering.

Sorry for late reply.

There is no widget included, but you can use the shortcode to put a login form/link on any page:

[wpoa_login_form]

Please see the Installation tab on the plugin page for more information.

If you need it in a widget, you’ll need to find another a plugin that lets you put shortcodes in widgets, then just use the shortcode above.

I’ll think about adding a widget to WP-OAuth so you don’t have to use an extra plugin.

Thanks, I merged this in at the Github repo. It should be in the next version.

In case anyone is wondering, the notices come from trying to start a session when it’s already started. These notices should not harm or compromise the plugin at all. They are not really errors, but the notices can leave some junk in your server log etc.

Thanks for the info, I’ll see what I can do about these.

I appreciate the review ??

LinkedIn made some unannounced changes to their API this week which seems to have broken many cURL implementations across the web.

https://stackoverflow.com/questions/29503312/linkedin-api-suddenly-returning-405-error

Go ahead and use Stream Context for now until I hear official word on these changes, or until I roll out a cURL fix in the next version.

Thanks, closing this.

Once you log into Google, you will remain logged in with that account until you specifically log out of Google or close all browser windows to terminate your logged in status. WP-OAuth will recognize that you’re still logged into this Google account and attempt to match an existing WordPress account which may have been registered using that Google account.

If you want to experiment with two Google accounts on one computer, try opening an Incognito window. That should create a separate session, where you can log into a separate Google account and register a separate WordPress account with it through WP-OAuth.

Have you tried setting the HTTP utility to Stream Context? That appears to be working for me, and I think I see the problem affecting cURL now…

I’m having this issue with LinkedIn as well. It looks like their API may have changed recently. Will keep you posted…

Hi Dan,

I’ll double check my live site to make sure LinkedIn is still working in the latest version. Other than that I’d say make sure to double check that your Redirect URLs match, and that you’re satisfying the conditions in the LinkedIn instructions (on the plugin settings page). I’ll let you know if I need more details.

dub, thanks for trying out the plugin! WP-OAuth can automatically register users who login with Facebook at your site for the first time. They will end up with a WordPress account at your site which is tied to their Facebook identity, but they may customize their WordPress account (profile) with a nickname and email address that is separate from Facebook. When a user returns to your site again and logs in with Facebook, their Facebook identity will be matched to their existing WordPress account they registered earlier, and they get logged in automatically. So the plugin still uses WordPress accounts to function, but allows bypassing the whole need for a username/password. You should also have the ability to use the traditional registration form alongside WP-OAuth. Hope that explains it better.

kkara, thanks for the update. Sounds like your server wasn’t configured for cURL. I’ll make a note that we should test for cURL/Stream capabilities before attempting to crash and burn ??

Thanks for trying out the plugin! Your assessment is correct. This thread should have the answer you’re looking for: https://www.ads-software.com/support/topic/how-can-i-get-the-user-name-and-the-email-address-with-facebook

This plugin does not fetch username or email address from their provider out of respect for the user’s privacy. It can also deter users from your site who do not wish to give out their email address (they are prompted to grant your site access to their email address which can be a deterrent). However, this is a common feature request and it will be added sooner or later. You might find this helpful: https://github.com/perrybutler/WP-OAuth/issues/5