tbenyon

Regarding your database error, it appears that this is an issue with the authentication on your MSSQL server.

There are lots of other threads that talk about these errors but it does seem to be an issue not related to the plugin.

I found Googling sql state 28000 18456 listed a bunch of suggested resolutions.

If you read something that leads you to think that this may be an issue with the plugin, please let me know and I’ll be happy to look further.

Regarding your PBKDF2 request, I’ll follow this up with another comment 🙂

Hey @rperrett,

Be careful with asking for people’s personal details. I know the moderators sometimes close peoples accounts for it.

However, really appreciate how helpful you’re being to the others 🙂

Thanks!

Tom 🙂

Apologies for that brief message before I was out and only had my phone to send a quick one.

Cool, just checking as someone has just flagged a bug with MSSQL that means it won’t call the described hook. Wanted to rule this out.

May I suggest that the next step is to:
1) ensure that the external database is what is authenticating the user
– To double check this, use the setting to disable local login. That way if you do login it must be with the external database
2) ensure that the hook is getting called when a user is authenticated with the external database
– To check this I am going to suggest you put the following code in your functions.php file so that you can check the logs and make sure you can see the notes.

function philengel_exlog_add_additional_user_data($wp_user, $exlog_user_data) {
    error_log('----------------philengel--START----------------------');

    add_user_meta(
        $wp_user->ID,                          // User ID
        'fav_colour',                          // WP Meta field key
        'red',                                 // String
        false                                  // Not unique
    );

    error_log('----------------philengel--END----------------------');

}

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

In your PHP error logs you should see two logs next to each other. This is what I saw when I just tested the code . . .

[Mon Jan 13 17:41:20.403030 2020] [php7:notice] [pid 88] [client 177.23.0.1:46688] ----------------philengel--START----------------------, referer: //localhost:8000/wp-login.php
[Mon Jan 13 17:41:20.404221 2020] [php7:notice] [pid 88] [client 177.23.0.1:46688] ----------------philengel--END----------------------, referer: //localhost:8000/wp-login.php

Secondly in the wp_usermeta table you should find a meta_key of “fav_color” for one of the entries and that same entry will have the value field stored as “red”.

Let me know which of this you can’t see.

Hey Brad,

GREAT SPOT!

Apologies for my mistake. Really appreciate you taking the time to diagnose the problem yourself. 🙂

I’ll get the fix in and deployed within a week for you, I’m hoping it’ll be this weekend but just can’t promise that.

Will keep you posted with updates and if you haven’t heard from me I won’t be offended if you chase.

Thanks again,

Tom

Hey @philengel,

Apologies for the delay.

Basically to add the required functionality to the plugin, you would need to add a small bit of custom code to your functions.php file in your theme.

An example of this can be seen below.

Basically, when a user is authenticated from the external database, the function philengel_exlog_add_additional_user_data will get called and you get access to the new user that was created in wordpress ($wp_user) and all the data from the user table where the user name and password were stored on the external database ($exlog_user_data).

In the below example I use WordPress’ add_user_meta function to add a new meta field called ‘fav_colour’ to the WordPress database. The data I’m storing in that meta field in wordpress is from the ‘favourite_colour’ field from the external database.

You could call add_user_meta() again for each of the different bits of data from that table you wanted to store.

function philengel_exlog_add_additional_user_data($wp_user, $exlog_user_data) {
  add_user_meta(
    $wp_user->ID,                          // User ID
    'fav_colour',                          // WP Meta field key
    $exlog_user_data['favourite_colour'],  // External table data
    false                                  // Not unique
  );
}

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

If you have any further questions, don’t hesitate to get back in contact 🙂

Thanks,

Tom

As I haven’t heard back from you I’m going to assume no more help is needed for now.

If you have any further issues, don’t hesitate to get back in contact.

🙂

Reset only uses the local WordPress database. Data does NOT get written back to the external database.

You could use a hook to make this happen if you needed to in your case.

Hope this helps 😊

• This reply was modified 6 years, 5 months ago by tbenyon.