Archive > Technical discussions

Email confirmation functionality

<< < (2/4) > >>

EHM-1703 Philip:
Yeah, mine worked as well on the second attempt. Pls disregard my earlier post Murray.

EHM-0654 Murray:

--- Quote ---Originally posted by EHM-0641
DEBUG: pID
DEBUG: emailaddr
DEBUG: eID

Email address confirmed

--- End quote ---


Glad it worked in the end Rico, but I'm very concerned about those three debug values being blank... Looks like there may be a problem after all.

EVERYONE I'll mod the post-confirmation page again in a wee while (I'm at work now, so have to do such things with great care), but if you go through the process and it doesn't work first time, follow this modified method:

[*]Log in on the main website home page.
[*]Click on the "Confirm Email" link on your pilot page.
[*]Once your pilot page reloads, go back to the main website home page and log out.
[*]Wait patiently for the new confirmation email to arrive.
[*]Click on the URL in the new confirmation email.
[*]Let me know if it still doesn't work.[/list]

EHM-0654 Murray:
Everyone

In an effort to nail the problems in the email confirmation code for existing pilots, I've modified my code a little.

First-off, I've changed the field used to identify you to the script that sends you the confirmation email. I'm hoping this will put a stop to the blank DEBUG values Rico saw (and possibly a few more of you...)

Second, it sends me a debugging email for every email it sends y'all, which should give me some insight as to what exactly is going on. With all the extra debugging that I've now added, getting it totally fixed should be easy.

Bruno

While I've been working on the DB trying to debug the problems, I noticed you'd somehow managed to put a pair of confirmation records into the DB (thought I'd prevented it doing that, clearly not...). I've removed the oldest one; the newest one should still work...

EHM-0654 Murray:
OK...

I still don't know the why of what's going wrong, but I'm getting a hang on the what.

It seems like the wrong timestamp is issued occassionally - the timestamp that goes into the database isn't always the same as the timestamp that is used to calculate the SSHA hash (that long string of "gibberish" at the end of the URL that is emailed out) even though it's the same variable in the same source file.

I've seen this a few times now, but there's no reason in the code why that should be the case. Only course I can suggest at this juncture is if it doesn't work for you, wait a few minutes and try again... (Bruno, that means you too :))

BTW: I've pulled all the additional debug information out of the page you see after clicking the URL that is emailed to you. I've built myself a special webpage elsewhere that recreates what that page you see does on-the-fly, and see everything that is going on that is otherwise hidden, so the debugging information on that page is redundant.

EHM-1617 Iain:
The 'modified method' worked for me. Using the 'still logged in method' which I tried first didn't work.

Navigation

[0] Message Index

[#] Next page

[*] Previous page