[potential feature] user-approval feature about huge HOT 8 CLOSED

I'm looking for the same exact thing.

I don't need a fancy GUI though. I'd like to be able to write the logic to handle whether or not the user can self register. In my case, I'm going to do a rest call to my CRM database and see if they're already in it. If they are they can self register... if they aren't they can't.

What I would like is for your "framework" to be able to send an email to an administrator with a link in it saying... "so and so is requesting access. Click this link to grant them access". Then, once the link is clicked the user who tried to register initially gets an email saying they're account has been approved and that they can login.

I'm willing to fund this development. Please shoot me an email to blake [at] alertustech.com.

from huge.

The email verification feature is released in the development branch!

from huge.

@blak3r This is the first time i see this ticket ;) ... This is quite specific and is probably not needed by 99.5% of the users, but i think we can make this in a special branch. I will have some thoughts on this and give you feedback in the next few days.

from huge.

I got this under control no worries.

~blake

On May 22, 2013, at 10:03 AM, panique [email protected] wrote:

@blak3r This is the first time i see this ticket ;) ... This is quite specific and is probably not needed by 99.5% of the users, but i think we can make this in a special branch. I will have some thoughts on this and give you feedback in the next few days.

—
Reply to this email directly or view it on GitHub.

from huge.

@blak3r I currently want to implement all the missing features, and in this case I'm not sure how to implement it. What should the criteria be that make a decision possible ? When a user registers with, let's say, a username and an email adress, what would qualify or disqualify him/her ? Or is it more a real-world-decision, like "i know that guy('s email adress) because he's from a partner company that handles our food shippings etc. ?

I understand that this makes sense, but i'm not sure how to do the approval process.

from huge.

This feature is pretty specific to the end user. I think it should be left up to them to define a function that does their proprietary business logic. In my case, I check the email address against my crm system.

But, I think there is a few things that fall into the php-login realm.

1. Come up with a simple "logic hook" convention. LIke create a custom folder. During registration it'd look in custom/ModeratorApprovalLogicHook.php... if that exists it'd call a method like performHook() in that class that would return true or false.
2. if false is returned, then you do something special... you show the views/ModeratorApprovalRequired error message.
3. Send the email to the moderator instead of the end user with a "moderator=1" query param tacked on.
4. Update the registration class to detect that moderator is clicking the link...
5. Once moderator approves automatically send the email back to the end user for them to click the link and verify their email.

Let me know if you want me to go into it more. Like I said, I already implemented it for my needs. So, only do this unless others want it.

I could think as an example you could provide with the product is a simple ModeratorApprovalHook for don't allow free email accounts. Like if it's from yahoo.com, live.com, gmail.com, etc. then they would have to go to moderation. I've seen that on lots of sites that are Business to Business related.

~blake

from huge.

Let's put this into Milestone 2 of the project!

from huge.

Let's put this (potentially) into 3.0 of the project.
https://github.com/panique/php-login/issues/milestones

from huge.