|
Ross Willits
|
February 15, 2013 at 10:50 am
This is strange, and it seems to have just begun recently.
When a customer adds an event to the cart (using multiple Registrations), and then clicks on “Enter Attendee Information,” when they get to the cart, if they click in any field, they are bounced back to the Add to Cart page, and cannot complete the transaction.
If instead of clicking into a field, they hit TAB to enter and exit any field, the form works properly.
It seems as if the entire form is acting like the “View Cart” button, and perhaps a tag isn’t closed properly with the “View Cart” button. But I can’t see where/how to fix it.
You can see this behavior by going to https://www.steppingstonetheatre.org/programs/event-registration/?ee=22 and trying to register.
Any help is much appreciated.
I have just updated to EE 3.1.30.7, and all my other EE plugins are up to date as well.
|
|
Josh
|
February 15, 2013 at 4:32 pm
Hi Ross,
The first thing to check is those templates that are in /wp-content/uploads/espresso/templates. If those were copied over from an older version of Event Espresso, they may not work with the current version of Event Espresso. I noticed the registration page you linked to had content that wasn’t being contained within the div there too.
The other thing that may help is you could change the setting in Event Espresso>Template settings to make it so the event description doesn’t display above the Multi Event Registration forms. It may even be an unclosed element in the event description, so you could check in the event editor for any missing closing tags.
|
|
Ross Willits
|
February 15, 2013 at 4:46 pm
Thank you for the response. With the help of our developer, I was able to track the issue down to exactly where you said it might be!
The Event descriptions had a link with a label of “<< Back to Class List" and the left arrows were being parsed as a tag opening, and the rest of the page was ignored.
When that description was pulled into the Registration page, the open tag made the rest of the form into a button.
I have fixed it now.
The odd thing is that on the event page, the "<" character was "<" in the code, but it was read as a < instead.
Poor decision on our part to use that character in a link!
|
