Curriki

Sometimes, the user's validation does not come through

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.10.6 Facebook Connect / Improved Login / Join
  • Fix Version/s: 1.11 New Core 3.5
  • Component/s: My Curriki / Registration
  • Labels:
    None
  • Similar issues:
    CURRIKI-5424Search Sometimes Slow for Logged in User
    CURRIKI-6038Sometimes Favorites does not work / it is not created
    CURRIKI-391The GWT service should not assume WebHome is valid if it exists.
    CURRIKI-4683Logging in does not take me to my profile page.
    CURRIKI-6032Progress bar sometimes fails.
    CURRIKI-5618Users should be automatically logged-in after validating account
    CURRIKI-5896Validation for Newsletter does not work
    CURRIKI-5588social-tools enabled accounts should be validated if existing
    CURRIKI-1846Forgot login -> Without entering email id, Go button clicked, validation message needs to be checked.
    CURRIKI-2304Changing email address to a new address in edit profile is no longer invoking the validation path

Description

There seems to be times when the user registers, then enters validation, then sees a page that is properly showing that it is valid but suddenly gets invalidated again and has to re-input the validation, which works again.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Paul Libbrecht added a comment -

Joshua formulated the hypothesis that the user is not properly saved... which may be true and seems to have been true in the current reading of Complete.vm.

I had a fix committed but rolled-it back first in order to evaluate.
And indeed I could:

  • click on a login-or-join
  • then on join-now
  • fill registration
  • validate by enter code
  • check that you are validated by looking at the header
  • flushed the cache in another browser
  • reload that same page where the header was wrong: you are inactive

paul

Show
Paul Libbrecht added a comment - Joshua formulated the hypothesis that the user is not properly saved... which may be true and seems to have been true in the current reading of Complete.vm. I had a fix committed but rolled-it back first in order to evaluate. And indeed I could: click on a login-or-join then on join-now fill registration validate by enter code check that you are validated by looking at the header flushed the cache in another browser reload that same page where the header was wrong: you are inactive paul
Hide
Permalink
Paul Libbrecht added a comment -

A fix is now committed.
It should be tested with a cache clearance after the key input.

paul

Show
Paul Libbrecht added a comment - A fix is now committed. It should be tested with a cache clearance after the key input. paul
Hide
Permalink
Paul Libbrecht added a comment -

I conclude that "only" less than 207 users had the bug and I propose to do one of the following:

  • (a) call that same URL once again, it will validate them successfully and should send then another welcome mail
  • (b) do the same but enriching the Complete script or mail so that an added message appears indicating the apology
  • (c) craft another script for this which would send a dedicated mail

Which one do you prefer?
What text should be mailed or added to the mail?

thanks in advance

Paul

Show
Paul Libbrecht added a comment - I conclude that "only" less than 207 users had the bug and I propose to do one of the following: (a) call that same URL once again, it will validate them successfully and should send then another welcome mail (b) do the same but enriching the Complete script or mail so that an added message appears indicating the apology (c) craft another script for this which would send a dedicated mail Which one do you prefer? What text should be mailed or added to the mail? thanks in advance Paul
Hide
Permalink
Todd Sherman added a comment -

Just do this one. (a) call that same URL once again, it will validate them successfully and should send then another welcome mail.

Show
Todd Sherman added a comment - Just do this one. (a) call that same URL once again, it will validate them successfully and should send then another welcome mail.
Hide
Permalink
Joshua Marks added a comment -

(d) combine this with the issue related to validation requests and automating the process for those who send an e-mail saying they did not receive their validation e-mail. (Basically paste in an email or user ID (Or send a list of them), the system will find them and if they are not valid, validate them and send a validation compete e-mail ("Your account was validated by administrator request..." or something like that)

Show
Joshua Marks added a comment - (d) combine this with the issue related to validation requests and automating the process for those who send an e-mail saying they did not receive their validation e-mail. (Basically paste in an email or user ID (Or send a list of them), the system will find them and if they are not valid, validate them and send a validation compete e-mail ("Your account was validated by administrator request..." or something like that)

People

  • Assignee:
    Paul Libbrecht
    Reporter:
    Paul Libbrecht
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Date of First Response: