The registration form works well,
but you must be careful with it.
I have discovered the following problems:
1. delete a user in backend (in user table) DO NOT delete the corresponding record in chronoform_registration table.
2. when adding record in chronoform_registration table is not cf_user_id uniqueness reviewed.
(!!!) therefore, a user (user_id) may correspond to multiple records (what one is elected later?)
3. if email is incorrect, there comes an error message.
But a record in the chronoform_registration table is created (with cf_user_id = 0); (in user table - do not).
Important result:
a user should not be removed in backend, otherwise the Problem 2(!!!) can occur.
You can block the unwanted user, or, if delete, must clean chronoform_registration table by hand (eg with phpmyadmin).
Regards,
Leon
but you must be careful with it.
I have discovered the following problems:
1. delete a user in backend (in user table) DO NOT delete the corresponding record in chronoform_registration table.
2. when adding record in chronoform_registration table is not cf_user_id uniqueness reviewed.
(!!!) therefore, a user (user_id) may correspond to multiple records (what one is elected later?)
3. if email is incorrect, there comes an error message.
But a record in the chronoform_registration table is created (with cf_user_id = 0); (in user table - do not).
Important result:
a user should not be removed in backend, otherwise the Problem 2(!!!) can occur.
You can block the unwanted user, or, if delete, must clean chronoform_registration table by hand (eg with phpmyadmin).
Regards,
Leon