Thanks for the replies, guys.
Ypsilon, thank you for the link, but that infusion doesn't address my problem. I actually have that infusion and it works quite well for when a user is awaiting admin validation or is already a validated member. I've used it very effectively with a few spammers to ban/block them when email validation was on. But if, such as in the example above, the user's name and email address are in "limbo" (email validation is on but the user can't validate via email for whatever reason) then the User Control infusion, like the rest of the site, doesn't see him, yet.
The example I gave in my prior post is very similar to something that has actually happened in the past on my site even with this infusion running. I can't find the user in question on the system and he's still locked out unless he creates another email address and user name. The user in question is a member of the board of directors but a little technically challenged and, because I am the admin, doesn't understand why I can't "just fix it!" :o
------------------------
I believe that there are four states of membership on PHPFusion:
1) Awaiting administrator validation.
2) Awaiting system validation via user email.
3) Pre-validated member (admin creates the account for the user in the admin CP).
4) Fully validated member.
Only three of these states (1, 3, 4) is parsed for the admin to be able to manipulate. It seems to me that state number 2) was indirectly coded with the (false in this case) assumption that the admin would never need to address it since the system itself, with the user's help, would take care of validation, freeing the admin to worry about other things. As we can see from my prior example, the system is imperfect (thanks to faulty user interaction) and there will be times that state number 2) needs to be addressed by an administrator.
The email validation system works and is very convenient for the admin if the user doesn't fumble it. The user is the weak link in the chain. Once a technically challenged user, which is sadly sometimes the vast majority, breaks that chain somehow, it becomes inconvenient for the admin in the extreme to rectify.
The ideal would be that the admin could see the account in state number 2) and either validate it manually, resend the validation email or delete the account altogether, freeing up the email address and user name for another attempt. I believe this state was overlooked in the initial coding stages of v7 and further believe that an infusion could be relatively easily made or found that should address this problem and its three ideal solutions. Sadly, I don't have the skill set to create such an infusion myself nor have I, as yet, found one that can do what I ask.
I guess I am asking (nay, humbly begging) the PHPFusion community and its pool of genius coders to address this problem and create said infusion, if possible, or help me find a better solution should one already exist.
Any further help would be much appreciated,
B) LJ
0 replies