tbenyon

I believe this got rolled into regular release. I would advise upgrading the version on a test environment first to ensure everything works as expected.

Thanks,

Tom

Fantastic news. Good luck with your project.

If you get a minute to write a review I’d be very grateful.

Hey there Sascha,

I’ve not worked on this plugin for some time so apologies that my answer may not be perfect.

As that is a beta feature it may not work, however it may not work well with the empty state.

What I would be more confident would work would be the exlog_hook_filter_custom_should_exclude hook. Here’s the notes on it from the documentation:

- exlog_hook_filter_custom_should_exclude

This hook allows you to add custom logic to exclude users.

It provides you with all the data for the user that is stored in the external database users table.
If you return true (or a string - see below regarding custom error messages) from this function it will prevent the
user logging in, and returning false will bypass this exclusion.

For example, let's say your external users table had a field called expiry which stored a date. In this example we
want to block users if they login after their expiry date.

Adding the following to your functions.php would achieve this:

<br>function myExlogCustomExcluder($userData) {<br>return strtotime($userData['expiry']) < strtotime('now');<br>}<br>add_filter('exlog_hook_filter_custom_should_exclude', 'myExlogCustomExcluder', 10, 1);<br>

Alternatively if you provide a string the user will be blocked and the string will be used as the error for the user.
<br>function myExlogCustomExcluder($userData) {<br>return strtotime($userData['expiry']) < strtotime('now') ? 'Your account has expired' : false;<br>}<br>add_filter('exlog_hook_filter_custom_should_exclude', 'myExlogCustomExcluder', 10, 1);<br>

The below code is what I imagine would work for you but I haven’t done any testing.

function myExlogCustomExcluder($userData) {
    return empty($userData['email_verified_at') ? 'Your e-mail has not been verified' : false;
}

add_filter('exlog_hook_filter_custom_should_exclude', 'myExlogCustomExcluder', 10, 1);

that’s great news 😊

Also, what happens if you press the test button?

This is the default behaviour of the plugin so you simply need to fill in the rest of the settings.

I’m assuming “Site A” is a site with existing users and “Site B” is where you will be installing this plugin and expecting users from “Site A” to be able to login to “Site B”.

If this is what you want this is exactly what the plugin does. It does not sync user changes back to site A. When a user logs into Site B, a clone of that user is migrated to Site B.

I think I’ve answered your questions so I’m marking as resolved but if you have any other questions please keep firing questions.

Thanks 🙂

Hey Dario,

Thanks for the positive feedback.

To answer your question, the answer is no not really. To have a logged in session, WordPress relies on their being a logged in user stored.

You could theoretically use the hook exlog_hook_action_authenticated to annonomise the login details or something? I don’t know your use case for not wanting the users stored there.

Thanks,

Tom

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