NateJacobs

https://github.com/NateJacobs/User-Access-Expiration/issues/2

On the user profile page there is a label that reads “Does this person have access to the site?” with either a “Yes” or “No”.

I don’t have plans to add this in the immediate future, but I will keep it around as an idea. Thanks

Hmm, I have tested that on my local test site and don’t get that behavior. I will look into it more. Thank you.

I will take a look and exempt admin and super-admins from the expiration time limit.

I don’t plan on adding the functionality to change the email from name/address. There are other plugins to handle that. Or you can create your own. Take a look at these two filters: wp_mail_from; wp_mail_from_name.

There is no time limit. This plugin was created for a someone who wanted the ability to require the user enter an activation code in addition to the registration link to log in. I built it and then thought I would release it.

I like the idea of adding a filter to sort by users not yet activated. I’ll take a look at that for a future release.

Issue fixed with update.

Resolved with an answer.

There are other plugins out there that provide that ability. I would take a look at those. I don’t have any plans to provide that functionality in this plugin.

wp_login_form() does not provide for the ability to add additional input fields. I’ll take a look at using wp_signon.

I am not sure what you mean by “code to insert custom forms for email validation”? The plugin works by sending an email upon initial registration.

Hi Taylor, It may have something to do with BuddyPress sending its own registration emails. I don’t have buddy press installed. I will try and get BuddyPress installed and test it out.

I am not sure I will be adding this functionality in anytime soon, but here is a function you can play with to do it for your site.

https://wp-snippets.com/redirect-user-after-login

Do you mean add the extra form field for activation code to a sign-in form created using the wp_login_form() function?

No, it was a bug in the code I missed from the last commit. I have pushed a new version, 0.4, that fixes the issue. Thank you for bringing it to my attention.