michaelchuchro

Here is the code i’m using

/* ULTIMATE MEMBER PLUGIN DOMAIN WHITELISTING CODE SNIPPET
   The following code will require a domain name to be whitelisted for user registrations.     
   It forces a user email to match one included in this code at registration.
   You can add any provider you want by copying and pasting a new line as per instructions.

add_action('um_before_new_user_register', 'force_google_email_for_avnw_signup');
        function force_google_email_for_avnw_signup( $args ) {
           extract($args);
           if ( !strstr( $user_email, '@anydomain.com' ) )

              exit( wp_redirect( add_query_arg('err', 'whitelisted_email_required') ) );
        }*/

I am also having the same problem. Any solutions?

Hello,
Do you have any solutions to this problem, it is becoming an ever increasing issue and happening more frequently.

Yes, I have recreated this. You can see a video of it at the link below.

https://www.chicagocop.com/wp-content/uploads/Activation-Link-Expired.mov

Hello again,

Ok, I figured out the issue with the custom fields nots saving, It was rather simple to fix. Somehow the two fields were duplicated on the profile page. That is the fields on the registration form, although labeled identically were different from the ones on the Profile page, which is why the information wasn’t displaying.

That just leaves me with the issue of the first and last name not saving to the WP backend. When you view the users through the Users tab on WP the first and last name are not stored when the account is created. However the username and email are getting stored. I did use the predefined fields on the UM registration page. Conflict test conducted with UM as the only active plugin with the same results.

Hello,

Well I tried a conflict test and disabled every plugin except Ultimate Member and still have the same results. I forgot to mention in addition to the standard WP user fields only one custom field “Agency” gets stored while the other two do not.

I tried disabling the database cache but that did not solve the issue for me. Still trying to figure it out, very frustrating especially with the other issues I’m having with this plug-in.

Thank You, I have made the recomended changes.

hello, sorry for the delay in responding. I did the conflict test and it appears that the conflict is with WP-SpamShield plugin. Login and account registration work perfectly on the affected computers in the same browser session when the plugin is deactivated. When it is activated the error message is received.

I don’t think you understood what I meant.

$err = __(‘We do not accept registrations from that domain’,’ultimatemember’);

is coded into the Ultimate Member plugin and it is the message that appears when a user tries to register an e-mail that is blacklisted. The string you recommend replacing/editing in your tutorial does’t display when a user enters a blacklisted e-mail address.

• This reply was modified 7 years, 7 months ago by michaelchuchro.

Thank You that seemed to do the trick. Much appreciated. The only difference was in changing the error message.

Instead of replacing this string:

$err = __(‘An error has been encountered’,’ultimatemember’);

replace this string:

$err = __(‘We do not accept registrations from that domain’,’ultimatemember’);

with this string:

$err = __(‘Your email service is not allowed to register here ‘,’ultimatemember’);