Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the sign-up process #34

Open
lhark opened this issue Jan 8, 2015 · 5 comments
Open

Improve the sign-up process #34

lhark opened this issue Jan 8, 2015 · 5 comments
Milestone

Comments

@lhark
Copy link
Contributor

lhark commented Jan 8, 2015

For now, this process is, to say the least, tidious. you need to go back to your mail-box at least twice, which isn't really user friendly. Moreover, each time, the user do have any feedback about the fact he need to check his email (or at least it's not always obvious). Furthermore, the link in the mail that is supposed to bring you to the account creation page isn't working. I haven't looked into it, this is just feedback from the rezotage.

@liusiqi43
Copy link
Contributor

Hi, quick suggestion:

  • Keep things short (i.e get rid of "to say the least, First, Moreover, Furthermore" etc, use bullet if needed)
  • Be precise (I don't catch what you mean following "Moreover")
  • Be constructive (what alternative/solution do you propose to solve this), or even better, write code instead :).

As far as I understand, users are asked to check their Mailbox once for verification? What's the second time? If the link isn't working, what's the error?

@lhark
Copy link
Contributor Author

lhark commented Jan 9, 2015

  • The only way to get the link to confirm the email, is through the newsfeed, going back to the first arcticle.
  • once you click it, it say your email isn't verified : you then have to guess that a mail has been sent to you.
  • After that, you'll need to guess once again that you have to refresh the page in order to get the confirm button that allows you continue the registration process.
  • At that point, i believe nothing was happening when you ckicked confirm ; the page just kept refreshing.
  • The only way to get to get around this problem is to use the "i forgot my password" button of the login screen, that allows for a mail being sent to you, containing a link to the registration page.
  • And when you've registered, you still need to go back to the login screen to log into your account.

Quite the journey, isn't it ? I believe that without our help at the rezotage, most of the users would not have been able to create an account by themselves :/

@liusiqi43
Copy link
Contributor

I see what you mean. Email verification is necessary though,otherwise we
can't make sure that the user is really a resident.

We shall put the instruction as a permanent alert then, or add a sign up
button which doesn't really mean "sign up"..

On Fri, Jan 9, 2015, 01:38 lhark [email protected] wrote:

  • The only way to get the link to confirm the email, is through the
    newsfeed, going back to the first arcticle.
  • once you click it, it say your email isn't verified : you then have
    to guess that a mail has been sent to you.
  • After that, you'll need to guess once again that you have to refresh
    the page in order to get the confirm button that allows you continue the
    registration process.
  • At that point, i believe nothing was happening when you ckicked
    confirm ; the page just kept refreshing.
  • The only way to get to get around this problem is to use the "i
    forgot my password" button of the login screen, that allows for a mail
    being sent to you, containing a link to the registration page.
  • And when you've registered, you still need to go back to the login
    screen to log into your account.

Quite the journey, isn't it ? I believe that without our help at the
rezotage, most of the users would not have been able to create an account
by themselves :/


Reply to this email directly or view it on GitHub
#34 (comment).

@gpichot gpichot changed the title Improve the sign-in process Improve the sign-up process Jan 9, 2015
@gpichot
Copy link
Member

gpichot commented Jan 9, 2015

I do not see the point here, it is pretty straightforward if your talking about this file:
https://github.com/rezometz/paiji2/blob/master/rezo/templates/rezo/claim_account.html

First point: on the previous version there was a banner telling people to sign up with the link.
Use the homepage_alert application on the admin site.

Second point: the process was designed like that as paiji was running at the same time (nobody was required to register to see his quotas). So everybody had his rezo account since a long time. I never thought you were gonna release paiji2 so soon :).

Third point: we just need to add some note to address this point.

Fourth: how many time did you wait?

Fifth: can you forward us the mail? I tried with my account and all was fine...

Sixth: we have to change the name of the redirect url.

@liusiqi43
Copy link
Contributor

I agree... I don't think we can do better given our constraints. We should
move the instructions in an alert though.

On Fri, Jan 9, 2015, 10:07 Gabriel Pichot [email protected] wrote:

I do not see the point here, it is pretty straightforward if your talking
about this file:

https://github.com/rezometz/paiji2/blob/master/rezo/templates/rezo/claim_account.html

First point: on the previous version there was a banner telling people to
sign up with the link.
Use the homepage_alert application on the admin site.

Second point: the process was designed like that as paiji was running at
the same time (nobody was required to register to see its quotas). So
everybody had his rezo account since a long time. I never thought you were
gonna release paiji2 so soon :).

Third point: we just need to add some note to address this point.

Fourth: how many time did you wait?

Fifth: can you forward us the mail? I tried with my account and all was
fine...

Sixth: we have to change the name of the redirect url.


Reply to this email directly or view it on GitHub
#34 (comment).

@gpichot gpichot added this to the backlog milestone Jan 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants