Does WebSignup have e-mail verification?

Hello,

I’m just checking out your cms at opensourcecms.com and I wondered how that WebSignup snippet works.. Does it have a e-mail verification? Will it add the users automatically or will admin have to approve them? If it adds users automatic, can it be configured to inform admins of account request and have ability to approve/decline them?

I know, this all could be done probably by customizing the snippets, but I’d like to know what can be done out-of-the-box version of WebSingup. Thanks!

Take a look at this post:

http://modxcms.com/forums/index.php/topic,3050.0.html

I’ve tackled this problem here.

Thanks for the fast reply! The modification you’ve made looks good. What I gathered from the thread is that users won’t be inputting passwords to the websingup form, they are auto generated and sent to the e-mail they give in the registration. Correct? This surely validates the e-mail address.. but what about the accounts that get made when users have set up a bogus e-mail address, will the system be able to "wipe out" bogus accounts so that the db wouldn’t fill up with unnecessary accounts..?

Good point. I haven’t planned for that. I’ll pass that on! Anyone?

Looks like we need an extra field in the database (verified) and a way to peruse unverified accounts in the manager, or a custom front end page.

Be careful about "wiping out bogus accounts" if you mean to deal with emails that bounce back. Down that road lies madness

A easier way to manage this (from a process standpoint) is to have an account set to bogus at creation time. Then if a user clicks on a link in an email, then the account is activated. Have a weekly (or whatever) process to check for for any accounts that are older than a week (or whatever time you want) and are still bogus -- those are the ones you want to purge.

that should be easy enough, make a document that contains only a snippet that activates the account and redirects the user to the login page or the home page (make that an argument in the activating snippet).

Put a link to that document in the template for the email, with a message that the user must click that link to activate his account.

You could even use the "blocked" field, setting it to 2 to indicate not validated, then add a line to the login.processor script for when blocked == 2, exactly like the one for when it’s == 1 only using a different message.

Use the lastlogin field for the create time. Then it would be easy to delete all users where blocked == 2 and the lastlogin is before a given value. Clear that field when activating the account.

Actually, I’m surprised that there isn’t a createdon field for users.

Susan, good point. Let’s make sure to get that in the next 0.9.2... can you track it?

Tracked. (I presume you mean the createdon field for web users)

Yes, thanks.