nope. checked it in the latest WSN language file: {DIRURL}/activate.php?memid={MEMBERID}&acti vation={MEMBERACTIVATIONCODE}
Still doing the same. I attached a debug info for the page I visit when hitting the activation link. Does that help, or should I grab debug info from another stage in the signup process?
no cache system. i just reverted all the way back to 4.x and the verification code is still the same... is there something in the WSN filesystem that needs some special permissions or something? That's the only thing I can think of now.
Interesting though, that in 4.x, when I visit the activation link, I actually get logged in. In 5.x I don't even get logged in.
What php or other files are responsible for generating this code and ensuring that when the activation code is visited, the person gets logged in? My guess is that something is wrong with file/folder permissions (even though I don't get errors).
by the way, is it possible that the admin panel shows that the cache system is not active, while it actually is... ? the 'cacheload' field in the DB is empty.
cacheload is irrelevant, it's a matter of whether you've selected any usergroups there.
Maybe I misunderstand you. I presume you're saying every member gets the same verification code. If you just mean that the same member gets the same code on each re-request, then of course that's true.
Paul wrote: I presume you're saying every member gets the same verification code. If you just mean that the same member gets the same code on each re-request, then of course that's true.
Yes, that's what I mean. What is true? I don't get it. You mean it's true that the cache could be on even though it is showing off?
Which of the two possible things I said you might have meant does "Yes, that's what I mean" reference?
I said nothing about the cache. I said that any particular member will get the same activation code each time they re-request it, unless their email address has changed, and that's very much intentional and proper.
Comments on account verification code error
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
No matter what browser, any time a new member signs up, the same verification code is sent out to them. What could be causing this?
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
Also, when the verification link is visited, it does verify the member, but doesn't sign them in, whereas this happened automatically before in 5.0.5.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Possibly you're using an old language file with the wrong variable for the activation code?
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
nope. checked it in the latest WSN language file:
{DIRURL}/activate.php?memid={MEMBERID}&acti vation={MEMBERACTIVATIONCODE}
Still doing the same. I attached a debug info for the page I visit when hitting the activation link. Does that help, or should I grab debug info from another stage in the signup process?
Thanks
David
Attached Files:
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Are you using the cache system?
Debug mode won't help here since queries aren't at issue.
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
no cache system.
i just reverted all the way back to 4.x and the verification code is still the same...
Interesting though, that in 4.x, when I visit the activation link, I actually get logged in. In 5.x I don't even get logged in.
What php or other files are responsible for generating this code and ensuring that when the activation code is visited, the person gets logged in? My guess is that something is wrong with file/folder permissions (even though I don't get errors).
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
by the way, is it possible that the admin panel shows that the cache system is not active, while it actually is... ? the 'cacheload' field in the DB is empty.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
cacheload is irrelevant, it's a matter of whether you've selected any usergroups there.
Maybe I misunderstand you. I presume you're saying every member gets the same verification code. If you just mean that the same member gets the same code on each re-request, then of course that's true.
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
I presume you're saying every member gets the same verification code. If you just mean that the same member gets the same code on each re-request, then of course that's true.
Yes, that's what I mean. What is true? I don't get it. You mean it's true that the cache could be on even though it is showing off?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Which of the two possible things I said you might have meant does "Yes, that's what I mean" reference?
I said nothing about the cache. I said that any particular member will get the same activation code each time they re-request it, unless their email address has changed, and that's very much intentional and proper.
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
cool. so each new email gets a different registration code.
Forum Regular
Usergroup: Customer
Joined: Jun 22, 2005
Total Topics: 91
Total Comments: 305
The login problem is there though. when a person registers and visits the activation url, they don't get logged in automatically.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
It's not even possible to auto-login unless the password is stored as cleartext, since the system doesn't know their password.