|
effectdigital
|
January 24, 2019 at 2:55 am
Hi,
<p>I have event espresso 4.9.76. When using the registration form to go through to the checkout it says that the first name field is required when it has a value. If i then refresh and try the form again it works. This happens every time, we can replicate this constantly. Hope you can give us a hand as we are a bit stuck.</p>
<p>Also, we have a form.resetElements is not a function in the console on some forms.</p>
Many thanks,
Joe
|
|
Tony
|
January 24, 2019 at 3:40 am
Hi Joe,
Also, we have a form.resetElements is not a function in the console on some forms.
That will part of the reason you are getting the error above with the first name field.
Can you link me to an event I can use to view this, please?
|
|
effectdigital
|
January 24, 2019 at 4:19 am
This reply has been marked as private.
|
|
Tony
|
January 24, 2019 at 4:27 am
You can either set it in a private reply (I can then remove it from the reply should you wish but either way it wont be publicly viewable) or if I need to log in to view, you can use this form to send details:
https://eventespresso.com/send-login-details/
|
|
effectdigital
|
January 24, 2019 at 4:29 am
This reply has been marked as private.
|
|
Tony
|
January 24, 2019 at 4:53 am
I’m not getting the same error as you, I get an error stating an invalid response was received from the server – https://monosnap.com/file/LscquTvaHb3f7uozLpA8scJD1bfode
That usually means there’s an error/notice/warning being thrown on the AJAX request. If you check the servers error logs can you see any errors from the last few minutes?
|
|
effectdigital
|
January 28, 2019 at 8:54 am
Hi,
That gets sent if you are not logged in, the admin-ajax request returns 0. Is there a setting i can change to ensure this doesn’t happen when you try to register?
|
|
Josh
|
January 31, 2019 at 7:42 am
Yes, you’ll need to disable whatever is blocking admin-ajax request on the front end if not logged in. The reason is because the checkout requires admin-ajax.php.
|
|
effectdigital
|
January 31, 2019 at 8:09 am
This reply has been marked as private.
|
|
Josh
|
January 31, 2019 at 8:13 am
No, there’s no debug setting for this. Event Espresso requires admin-ajax on the front end or you’re get an error when you try to register.
With regards to the first name error, that’s probably a plugin conflict or a theme conflict, and you can rule out either of those by temporarily switching to the twentynineteen theme and temporarily deactivating all other WordPress plugins.
|
|
effectdigital
|
February 7, 2019 at 2:33 am
Hi Josh,
Yes switching the an alternative theme worked however disabling all plugins on our custom theme did not. Have you had other cases of this? If so how were they resolved? Potentially conflicting versions of jquery? or jquery validate?
Thanks for your help again.
|
|
Tony
|
February 7, 2019 at 5:38 am
It sounds like you think EE is blocking the request because we are not logged in, if so can I ask what makes you think that?
EE doesn’t block the request when not logged in so there’s no setting for it.
Any of the above could cause issues, but as we can’t see the problem, we can’t help troubleshoot it so the first step is to find out why we can’t test a registration whilst logged out.
If you switch to a default theme and test a registration whilst logged out, does it work?
|
|
effectdigital
|
February 7, 2019 at 5:57 am
Yes it does not throw a error with a default theme and not logged in. If this is to do with the validation conflicting, what would you suggest?
|
|
Tony
|
February 7, 2019 at 7:10 am
Find where in the theme is adding the additional (older) instances of jquery validate and comment it out, then retest.
I suspect there’s more to it than just that, the ajax request shouldn’t fail because of that conflict, you would normally just get a notice on the page staging the field wasn’t valid. I know that’s what you get when logged in but the ajax request failing is likely another clue to something else.
|
