I set up a Tiki with User Registration with some required fields and using a pretty tracker.
When a user fills the registration form with no value in a mandatory field, the tracker item is not created and a failure message is displayed with the form so the user can try again. BUT the user is still created.
So, the next attempt will fail again because the user already exist
Also, the admin will not get the email about a new user registration.
In this case, the user should not be created
More info:
The issue is only when using pretty tracker templates.
When not using a template, the validation prevents from leaving the registration page, so the issue is not there.
So, a fix would be to make the validation work even when a template is being used for registration.
For reference, the template file ask-registration.tpl
is:
<div class="registration_form"> <div id="registration" class="panel panel-default"> <div class="panel-body"> <div class="form"> <label for="name" class="control-label titlefield">username</label> {$register_login} </div> <div class="form"> <label for="name" class="control-label titlefield">{tr}Email{/tr}</label> {$register_email} </div> <div class="form"> <label for="pass1" class="control-label">{tr}New Password{/tr}</label> {$register_pass} </div> <div class="form"> <label for="pass2" class="control-label">{tr}Confirm password{/tr}</label> {$register_pass2} </div> <div class="form"> <label for="ins_6" class="control-label titlefield">Not mandatory</label> {$f_1} </div> <div class="form"> <label for="ins_3" class="control-label titlefield">Mandatory field</label> {$f_3} </div> <div>{$register_antibot}</div> </div> </div> </div>
The real issue was, people could leave mandatory fields empty and click on save.
Victor fixed this, so that saving the form is forbidden unless all mandatory fields are filled.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.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.tiki.org.
The URL for the show.tikiwiki.org instance that demonstrates this bug is at: http://jyhem-9952-6670.show.tikiwiki.org. 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://jyhem-9952-6670.show.tikiwiki.org/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 show.tikiwiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http://jyhem-9952-6670.show.tikiwiki.org/snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Create new snapshotfilename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |