View Issue Details

IDProjectCategoryView StatusLast Update
0000017WackoWikiemailpublic2009-10-13 17:19
Reporterpascalvmf Assigned ToTann San  
Status resolvedResolutionfixed 
Product Version4.2 
Fixed in Version4.3.rc 
Summary0000017: email verification procedure is confusing
Descriptionvmf_pascal 24-01-2005 21:17:
category could be : user registration

when a new user registers, an email is sent to him so that he can confirm his email by clicking on a special link.

if you are not logged in into the wiki with your new login, this link will give you an email verification error.

This link only works if you are previously log in the wiki with the browser.

What would be better is a behaviour we find in all other email verification system : the link given in the email valids the user account email regardless of whether the browser is already logged in the wiki or not.
TagsNo tags attached.


related to 0000018 resolvedTann San email_confirm is not populated in the database 
related to 0000335 resolvedadministrator improve text for email verification 



2008-07-02 20:11

administrator   ~0000403

on the other hand the description of the whole process is poor and needs some improvements too

Tann San

2008-07-02 20:24

manager   ~0000404

I'm confused by this bug report!


2008-07-03 15:15

administrator   ~0000407

Last edited: 2009-01-06 10:26

"If you want receive notifications, you need to approve your email."

notifications -> the message should say what kind of notifications

You have successfully registered on the site% 1. Your login:% 2. \ N \ n "." To receive alerts, be able to recover, "." Forgotten password to use private communications, you'll need. "Verify your email address. To do this, please. "Follow this link: \ n". "% 3 \ n \ n". "If you did not request any registration on our site, and it is." Message is in error, please contact Customer Services "." Abuse at 4%. \ N \ n

If you did not request any registration, ignore this message and nothing will


2009-01-06 15:27

developer   ~0000555

this bug seems resolved in R4.3 for me.

Issue History

Date Modified Username Field Change
2007-08-28 00:19 EoNy New Issue
2007-08-29 05:58 administrator Legacy => NPJ
2007-11-01 13:49 administrator Status new => acknowledged
2007-11-01 13:49 administrator Description Updated
2007-12-01 15:32 Tann San Status acknowledged => assigned
2007-12-01 15:32 Tann San Assigned To => Tann San
2007-12-02 20:26 administrator Relationship added related to 0000018
2008-07-02 20:08 administrator Description Updated
2008-07-02 20:11 administrator Note Added: 0000403
2008-07-02 20:24 Tann San Note Added: 0000404
2008-07-03 15:15 administrator Note Added: 0000407
2009-01-05 18:30 administrator Reporter EoNy => pascalvmf
2009-01-06 08:39 administrator Note Edited: 0000407
2009-01-06 10:26 administrator Note Edited: 0000407
2009-01-06 15:27 pascalvmf Note Added: 0000555
2009-10-13 12:13 Tann San Status assigned => resolved
2009-10-13 12:13 Tann San Fixed in Version => 4.3.rc
2009-10-13 12:13 Tann San Resolution open => fixed
2009-10-13 17:19 administrator Issue cloned: 0000335
2009-10-13 17:20 administrator Relationship added related to 0000335
2010-03-08 10:13 administrator Category Email => email