It is the correct behavior, it shouldn't redirect to the second step when the user click register from the quick registration form.

Because you can assign other step custom field to show in this quick registration form.

I see, but its not soo relevant to see again fields that we already filled in quick registration, users need to click on next to see next step .. i think there is some thing to enhace here

That is difficult to check this if you do not want to show those custom field which user already filled in their data from quick registration form.

Imagine some of the user site if the registration form first step not all the custom field show in the quick registration form? The system also will redirect user to the full registration form first step since there got other custom field not showing in quick registration form.

Yes, no matter how there also will have a way to check this but from the performance wise it gonna be bad, because it probably need to execute a few SQL query to check :

1. Check for the current user workflow which custom field not showing in quick registration form.

2. Check for the user which quick registration form custom field not fill in yet (probably that is optional field), but also need to render it on the full registration form since system will redirect user to full registration form.

3. Check whether we render the registration first step when the user click on that register button from the quick registration form.

4. Check whether need to skip one the registration form step or not if some of the user site registration form step custom field configure to show all in quick registration form.

5. and etc.

Hello Arlex, i see the complicated side of this.

Another thing that (i am pretty sure) will increase registrations,
Save emails addresses filled by users in quick registration form and if the person dosent complete the process the system send a follow up, why not have a page in back end to see not completed registrations and send them manually invites for example.


Or a light version of this, just save the emails (or/and other custom fields in quick regist) somewhere in back end, until admins can send invites or followups.

I think this will not work if you would like GDPR compliance on your website, unless you have show them a very clear state like whatever you fill in your personal data like email before complete the registration, it will store into the website and etc.

Because the current system do not store any custom field data into your database yet if the user haven't complete the registration, it will only store those data into session from the browser.

If you really want implement this on your site, you can always request for a quote from us at https://crm.stackideas.com and select "Customizations" . Our sales person would gladly send you a quote for the customization that you have requested.