I have created a new site, and asked some people to try and register on it, and tell me anything that confused them.
And it seems there is something about the registration sequence of Tiki that can be confusing to end users.
In Tiki, the sequence (as I have configured it) looks like this:
A) User registers
Admin receives a notification
C) Admin approves
D) User receives a notification asking for him to confirm his email. He clicks on a link to validate that he controls that email.
Because I am the sole admin and am not at my computer all the time (I do sleep 8h a day ;-)), there can be sometimes a couple of hours between A) and D). This means that for many hours, the user no “persistent” confirmation that his registration request has been noted. To be sure, when you register, Tiki prints a message on the screen that says you will receive an email notification and that this can take several hours. But it doesn’t send you an email until the Admin has approved the account. So, for say, 12 hours, you are wondering what’s going on, and you don’t have anything anymore that tells you it’s being processed (because the Tiki message is now gone from your browser). It’s easy for people to start wondering “Did this REALLY work? Did I REALLY see that message from the server saying that I would receive an email message?”. This is what happend to my test user.
In most systems I have worked with, the sequence is more like this:
1) User registers
2) User immediately receives a notification asking him to confirm his email. User clicks on a link to validate that he controls that email.
3) Admin receives a notification that someone with a valid email has requested a registration
4) Admin approves
5) User receives a note that his account has been approved
With this sequence, even if the admin takes a long time to approve the request, during that time, the user has a PERSISTENT acknowledgement in his email inbox.
Another advantage of the later sequence is that we don’t bug the Admin until we know that the email address is valid. With the current approach, if a spammer tries to register with an email that doesn’t exist, the Admin will be asked to approve the account anyway, and we will end up with an account that exists, but was never validated.
Do people agree with this analysis? And if so, do we know how easy or hard it would be to change the order so that step D) happens right after A) instead.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tikiwiki.org instance. To start, simply select a version and click on "Create show2.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tikiwiki.org.
The URL for the show2.tikiwiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tikiwiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|