tbenyon

Hey Leif,

Just wanted to say thanks for the beers!

If you’re ever back in England down Brighton way let me know and we can toast your project properly!

Just updating to say I haven’t forgotten about you and have seen your other thread but prob won’t be looking at this till the weekend but will at least update you on progress by end of Sunday.

Will keep your posted 😊

Hey @leifharmsen,

Agreed – could definitely be an add on for the future. I keep toying with the idea of investing a bit more in the plugin and creating a ‘Pro’ paid for version but the legwork in setting that all up is hard to justify.

Thanks for your positive attitude and your comments. It’s always great to hear another perspective.

For now I will plod along with the hook for you and I’ll write you some Pseudocode to help you get started with adding the hook to your setup.

I’ll try my best to keep you posted but feel free to check in with me in a week or so if you haven’t heard from me.

Thanks,

Tom 🙂

Hey @drblackerror,

Really appreciate you taking the time to write a review 🙂

Thanks a lot,

Tom 🙂

Hey @drblackerror,

This is actually the default behaviour of the plugin. Every time the user logs in they get their credentials checked against the current password in the external database.

The only time this doesn’t happen is if you’ve ticked migration mode.

This will then check to see if the user already exists in the WordPress database, and if they do, will use the details stored there.

Can you check if this is checked for me and let me know if this solves your problem 🙂

Thanks,

Tom 🙂

Hey @yigitkeremoktay,

The External Login plugin allows users to login to WordPress with credentials stored in an external database.

It creates users in WordPress when they are authenticated with the external database.

I’m not sure what you mean exactly, does this answer your question?

Hey @goerg1980,

Apologies for the delayed response. I actually wrote you a response midweek but having come back to check in I see that I never sent it?! Will write again now . . .

If the fields that you require are in the same table on the external database, there is a hook that I’ve added which will help achieve what you are looking for.

There’s some information in the FAQ on the available hooks but I’ll write you some basic pseudo code to get you going 🙂

function my_function_to_do_something_after_authentication($wp_user, $exlog_user_data) {

  $updated = update_user_meta( $wp_user->ID, 'client_pet_name', $exlog_user_data['pets_name'] );

  // Checking if added ok
  if ($updated) {
    error_log('Additional field added');
  } else {
    error_log('Unable to add additional field');
  }
}

add_action('exlog_hook_action_authenticated', 'my_function_to_do_something_after_authentication', 10, 2);

Not tested but in theory this would get information stored in your external database under the field ‘pets_name’ and would store it in the WordPress meta value ‘client_pet_name’.

Let me know if you have any questions and apologies again for the delay 🙂

Thanks,

Tom

Hey @lvelve,

In most cases the plugin, by default, assumes that you are using the external database as the centre of truth and after each login you we should update WordPress with any setting that may have changed in the external db. This includes:

• name
• password
• email
• roles
• etc.

There is a migration mode option that will only take this information on initial login. Then, if the user already exists you just login with their WordPress user and nothing gets updated again.

Of course another solution is to put the roles that you require for the user into the external database and mage roles there.

Does this meet your needs or do you need certain information to keep being updated and just roles to be referenced by WordPress? If this is the case, there is a hook that should help you achieve this, which I can write you some pseudocode for.

Thanks,

Tom