|
JessicaRodgers
|
January 30, 2019 at 1:36 pm
Event Espresso has a bug in line 102 of event-espresso-core-reg/core/templates/global_assets/scripts/form_section_validation.js
eei18n isn’t defined and so the datepicker errors out.
It kills all js to the page and prevents my navigation bar from functioning.
To fix this I commented out line 102 and uncommented line 103 and all errors to my page disappears and my navbar is functioning normal.
|
|
Josh
|
January 30, 2019 at 1:47 pm
Hi,
That’s not actually a bug in Event Espresso 4 core. What’s happening is something on your site is preventing eei18n from being defined.
The correct course of action here isn’t to comment out code, but instead find out why eei18n isn’t being defined, and make the correction there. May I ask has any other code in Event Espresso 4 been commented out?
|
|
Tony
|
January 30, 2019 at 1:47 pm
Hi there,
The issue is not actually the line mentioned, it’s the fact that eei18n hasn’t been defined at that point (it should be, and is on my test sites).
Looking at your site it looks like you are forcing all JavaScript files from plugins to load in the footer, the problem with that is the form_section_validation was likely loaded before eei18n was defined on the page.
Are you using a plugin to load all of the JS files in the footer? If so try disabling that as right now your checkout page is broken, you should see ‘1 ATTENDEE INFORMATION’ and ‘2 PAYMENT OPTIONS’ as they are display on initial load currently.
|
|
JessicaRodgers
|
January 30, 2019 at 2:57 pm
I reverted the 102 and 103 back to the way they were and attendee info is still missing. And now my navbar navigation is unusable.
We do not have any plugin forcing the js to load in the footer.
|
|
JessicaRodgers
|
January 30, 2019 at 3:20 pm
Also, when I do make it the checkout page is blank unless I refresh the page. I do not what my client to have to force his customers to do this.
|
|
JessicaRodgers
|
January 30, 2019 at 3:30 pm
Ok So I found the issue. We use ACF for our content editor and your shortcode doesn’t like it. So I enabled the wordpress content editor and not this issue is fix.
Thank you so much for taking the time to answer.
|
|
Josh
|
January 30, 2019 at 3:34 pm
Hi,
Something is definitely going wrong on your site, for example if I view the source of the page, many scripts are missing, and there are other JavaScript errors due to missing variables passed via wp_localize_script.
Usually this tends to happen if something is removing actions from the wp_footer() action (or if the wp_footer() hook isn’t in the expected location).
If you go into the theme’s footer.php template, is the wp_footer() call just before the closing </body> tag? It should look just like the _s theme’s footer.php:
https://github.com/Automattic/underscores.me/blob/master/footer.php#L29
|
