-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Registration form bug, needs immediate fix #239
Comments
@grzegorzgit are you using the release zip or dev branch ? |
The zip, from here https://github.com/prestarocket-agence/classic-rocket It is not only in the address form but also in the registration form... how is it possible that such bug got through? Literally your theme disables registering new customers |
I'm using develop branch, and I cannot reproduce, neither on registration nor on address form. |
Ok, I am glad that it works on dev :D but the link that people download the theme, the official version is broken. Commenting out validation in form.js fixes the problem (form.js:58). |
Dev does not work on PrestShop 1.7.7.3 and 1.7.7.4 :-( Is there anyone who can handle this? It is not possible to run a store where customers have trouble registering. |
Hi,
I have just found out that new customers cannot register, and it's because of invalid address form.
If you fill the address form (in checkout, as a new customer), but you skip one required field, the form is submitted but come back with an error. After this submit (and new page load) the submit button is no longer active, and filling out the missing required field doesn't make the button active again.
So basically if you fill out the address form, but you forget to fill one required field, you will be stacked with that page and not able to go further.
Refreshing page sometimes helps and activate the button. My guess is that in JS validation, there is missing something that checks if the required field was filled and makes the submit button active.
Please consider fixing this immediately, it is a serious problem.
The text was updated successfully, but these errors were encountered: