Email validation without access

[LS]

Hi. If this possible?

1) A new user registers on Website.
2) The user receives an email ONLY for confirm that their email account is valid.
3) After verify it, the user still can’t access to website. He needs to wait for Admin approval.
4) After Admin approval, the user receives an email notification with confirmation and now can access to Website.

Thanks!

[keyhanjun]

Hi LS,

not exactly but why not using only one home/landing page but the content shown depends on being logged in or logged out. Pending users are logged in but shouldn’t be shown verified-only content.

Shortcode:

[userpro_private restrict_to_verified=1]Content to restrict to verified accounts only…[/userpro_private]

[admin]

You want to make both EMAIL VALIDATION + ADMIN APPROVAL before he can access and not just one validation? either email or admin? Did I get it right?

[LS]

Exactly! i need first email validation from user and after account approval from Admin.

[admin]

You need to modify code to do this. e.g. When user validates his email this action is run in api.php

$this->activate( $_GET['user_id'] );

you need to change that line to stop activating account when user validates email, and add code that makes is pending admin approve.

API function pending_admin_approve() look it up in api.php

You need some php knowledge to figure it out

[ssuess]

Hi, This feature would be very useful for a site I am building as well. I tried following your instructions above, but there are too many other places in the code that would not be changed by merely replacing this, and I am worried about that breaking updatability of the plugin.

Specifically when I allowed verification but prevented activation, there are still the following elements unaccounted for:

1. In backend Requests tab still shows user as needing email validation, even though they have validated
2. If user tried to login, they still get error message about needing to verify (instead of message about awaiting admin approval)
3. As mentioned above, any of these changes would need to be reapplied at every plugin update

Is there any way this might be added to the plugin in the next update or two?

Thanks!