Verify email upon sign-up

[iam1980]

Is anyone planning on implementing this?

[donjakobo]

I haven't thought of adding it... all yours :)

[donjakobo]

@AdwinTrave did you add this to your CI3 branch?

[StorytellerCZ]

@donjakobo No, I don't have this feature yet. I will work on it, but currently other task have taken priority.

[StorytellerCZ]

Presently working on this. Will be part of the next CI3 merge. After we test it more in the CI3 branch I will port it back to to CI2 branch as well.

[StorytellerCZ]

Done, will be merging soon.
Upon sign-up an email will be send to verify user e-mail address. There is an option that will stop user for signing in until their email is verified (at the same time I've also added made sure that it checks that the user isn't suspended).

So the basic thing is done, now more things can be added like, resends and reminders in user settings if the user hasn't verified their e-mail.

[donjakobo]

Thanks for the commit, I'll review and merge.

[StorytellerCZ]

I think that this is done in the CI3 version.

@donjakobo I found this: https://github.com/EllisLab/CodeIgniter/wiki/A3M-Account-Authentication-and-Authorization
I think we should probably update it. Also it might not hurt to start putting version number on our progress again. Hence "officially" release the current progress as version 0.7 and keep track of changes for the future. If we want we can then port features like this one from the CI3 branch and release version 0.8
What are your thoughts?

[donjakobo]

We can do that, the numbering I would try to stick to say v1.0 being CI 2.X as typically the X.Y is X = major, Y = minor.

Also, CI 3 would be at least a jump to 2.0 since it is a huge architectural change and not compatible with the previous 1.X

Thoughts? I typically jump from 1.Y -> 2.Y if we change something big time (like Bootstrap 2x -> 3.x) or php dependancies like CI 2.x to CI 3.x

[StorytellerCZ]

I would go as far as X.Y.Z
X - major
Y - minor
Z - patch

I agree with having the current CI2 branch being 1.Y and the CI 3 being 2.Y, it makes sense.

If you are fine with that I will create milestones so that we can separate issues based on which version they are related to.

[donjakobo]

yeah, Z for patch is preferred, I just forgot to mention it ;) 👍
work has been completed on version v1.0

If you want you can setup a tag for the CI3 as well, I will go and update the Ellislab wiki