Be careful with the registration form

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

Hi Leon,

I agree with you, I will try to provide fixes and enhancements to this very soon!

Regards
Max

Thank you.

will you give a new information in this topic?

yes, but when I finish the basic new update for Chronoforms which has been delayed many times because I was crazy busy recently!😟

Regards
Max

yes, but when I finish the basic new update for Chronoforms which has been delayed many times because I was crazy busy recently!😟

Regards
Max

Hi,
How do you do ? 🙂

have you now time to solve the problem?

Thanks.
Leon

Hi Leon,

Not yet, a new release is out but its needs some enhancements, once ready I will solve this problem and add the necessary plugins!🙂

Regards,
Max