|
woocom
|
July 2, 2015 at 10:26 pm
I’ve installed the latest version of EE as of writing (4.7.5p), and I’m using it without any additional add-on plugins.
The problems I’m having appear to be fundamental in nature with regard to how EE handles form customizations and locations. Specifically, I am using Australia as the country and have needed to add the 8 states/territories manually. By default both Canada and United States were set to “YES” for appearing in dropdown select lists. I have set both Canada and USA to “NO”, leaving only Australia as “YES”. States are all set as “YES” and are displaying correctly.
This is what is happening… After clicking to register for an event and selecting 2 tickets I am taken to the first Registration Checkout page. No surprises there and the 2 attendee forms (both question groups – personal and address details) are displayed for each attendee.
Note that I have edited the question groups (under management -> registration form) so that the ordering and placement of the fields, as well as the label names are slightly different to default, e.g. “Suburb” instead of “City”, and “Postcode” instead of “Zip Code” etc… but nothing of a functional nature or in the code base. I also moved the Phone Number field from the Address details group to the Personal details group, again using the built-in functionality.
Form validation works so if I miss a field I’m seeing the red borders on fields… all good so far. The problem starts when submitting the form. Regardless of whether I am using free tickets (where it would be to “Finalize Registration”) or priced tickets (where it would be showing “Proceed to Payment Options”) — the problem is the same:
The form POSTs to registration-checkout/?step=attendee_information and does not return an error. It merely reloads the page with empty form fields. The action parameter of the POST has a value of “process_reg_step”.
In the EE – registrations I can see incomplete registrations for the 2 attendees I just submitted. The “Name” column is empty for both contacts 1/2 and 2/2. I am concerned that perhaps my changes to the question groups are somehow breaking the expected form fields, although I did not touch the First Name / Last Name fields at all.
The second issue which is more difficult to troubleshoot is the State select box. Instead of only the Australian states, it is also showing the USA & Canada states and provinces. This only seems to happen after the initial post, if I manually navigate to the page through the address bar only the Australian states are showing.
I can continue to fill the form out and each time it simply reloads without any errors and I can never get past the attendee information stage of the checkout.
For what it’s worth – I did have custom templates in uploads/espresso, but I have removed them for troubleshooting these problems. I’m essentially running a clean/vanilla install of the EE plugin.
I’d be grateful for any help you can provide, and would be able to give you access to my WordPress install on our staging server.
|
|
Dean
|
July 3, 2015 at 3:20 am
Hi,
The first things I would check are:
That the core pages in General Settings > Critical Pages tab are set correctly
That the county in the General Settings > Your Organization tab is set to Australia
That there is no caching plugin active and cache has been cleared and that there is no server level caching. If there is you can add EE pages to the whitelist: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
Changing the question wording and order should have no impact on this, so long as the key First name/, Last name and Email questions are OK.
If the above doesn’t help, please provide a link to the site so we can examine it more closely. We may ask for login details after that point.
|
|
woocom
|
July 12, 2015 at 7:03 pm
Hi Dean,
After many hours of poking through code and a lot of head scratching – we managed to resolve this issue in about 5 seconds!
We feel rather foolish… but hopefully this will save someone else from a similar fate in future.
I didn’t mention that we are using a Yoo Theme (with custom styles) for the page templates. One thing that the templates do is strip off a lot of the WordPress boilerplate function calls in the main template file. We only needed to add the wp_footer() functional call…
<?php
/* Always have wp_footer() just before the closing </body>
* tag of your theme, or you will break many plugins, which
* generally use this hook to reference JavaScript files.
*/
wp_footer();
?>
There may have been some lazy-loaded js that was getting left out… we’re not sure in the end, only that adding wp_footer solved all our problems with the registration. I’ve been away so not looked into the State select box anomaly any further. I’ll let you know if that crops up again.
thanks,
Larry.
|
|
Lorenzo Orlando Caum
|
July 12, 2015 at 8:16 pm
Hi Larry, thanks for updating us on this issue. Event Espresso does need wp_footer called via the theme to work correctly. This is because some resources are loaded in the page footer.
—
Lorenzo
|
