|
AmritYoga2015
|
September 30, 2016 at 1:49 pm
An error has occurred:
First Name is a required value.
This seems like a pretty common issue ’round these parts. Issue on the registration page rejecting first name entry in the personal information area
We updated to EE4 4.9.13 2-3 Days ago (09-28-16ish)
Also Running
Wordpress 4.6.1
Theme – Karma Builder 1.9
Many of your support forums point to a theme-plugin interaction issue with JavaScript, typically pointed at the theme. However, no issue arose until updating EE4. Only after the update did this begin.
I have attempted to located the file main.min.js for the href modification as suggested in this forum
https://eventespresso.com/topic/an-error-has-occurred-first-name-is-a-required-value-10/
But where in the directory would this be located – under karma builder files? EE4?. A global search yielded no results.
Thank you for your support and Guidance in this issue. We need to get this fixed soon.
|
|
Josh
|
September 30, 2016 at 2:26 pm
I’m afraid it’s a pretty common issue because it turns out many WordPress themes were poorly coded. Can you try deactivating your Facebook plugin? It’s throwing errors in the browser when I visit your site, which if you get a JavaScript error, that will break the registration form validation.
This is the error:
Facebook Pixel Error: Duplicate Pixel ID: 1771154986437566
|
|
AmritYoga2015
|
September 30, 2016 at 2:35 pm
Hello!
Deactivated Facebook Conversion Pixel Plugin. Issue remains.
|
|
Josh
|
September 30, 2016 at 2:48 pm
You can rule out a potential theme or plugin conflict by following these steps:
1) A theme conflict. You can rule this out by temporarily switching to the default WordPress theme, then test. For a live site, it’s recommended to install the theme test drive plugin. The theme test drive plugin allows for testing another theme without actually changing your site’s theme.
2) A plugin conflict. You can rule this out by temporarily deactivating any other installed WordPress plugins. Then you reactivate them one by one, while testing the error condition between each reactivation.
It may also help to turn on debug mode. You can set wp_debug to true by editing the wp-config.php file.
You can use an [FTP client][1] and [a text editor][2] to access change this line to the site’s wp-config.php file:
define(‘WP_DEBUG’, true);
[1]: http://codex.wordpress.org/FTP_Clients
[2]: http://codex.wordpress.org/Editing_Files#Acceptable_External_Editors
|
|
AmritYoga2015
|
September 30, 2016 at 3:35 pm
I have switched themes. No fix
I have reverted EE4 to version 4.9.12 and that fixes the issue. This clearly demonstrates the conflict is EE4, or at least a interaction conflict between EE4 and another plugin.
|
|
Josh
|
September 30, 2016 at 4:31 pm
Which plugin do you think there’s a conflict with?
|
|
AmritYoga2015
|
October 3, 2016 at 9:18 am
Okay, So! After following the protocol outlined above I was able to isolate a conflict with our personnel directory database plugin called Connections-Pro: http://connections-pro.com/
The plugin was not updated concurrently with EE4 (4.9.13). Connections-Pro has remained on version 8.5.26 for several weeks. The EE4 4.9.12 to 4.9.13 created a conflict with Connections-Pro. This doesn’t really explain the Facebook Pixel Code error message you discovered… not sure about that.
Because registrations are primary importance to us, we have deactivated connections-pro and began a support ticket with Steve Zahm at Connections. Any coordination you could begin with him would be very helpful – EE4 and Connections generate the bulk of our plugin conflicts.
|
|
cirobe
|
October 3, 2016 at 10:03 am
Thanks for posting, AmritYoga, we are using both plugins and experiencing the same issue. Unfortunately, both plugins are important to us especially this week so here’s hoping Steve Zahm can come up with a solution. He was good at finding our last problem. I’m not very pleased with how easily EE breaks right now; I have some pretty unhappy customers.
|
|
Josh
|
October 3, 2016 at 12:33 pm
You can apply a temporarily fix that will eliminate the conflict from the Connections plugin by adding the following to your site:
add_action( 'wp_enqueue_scripts', 'my_temp_fix_for_connections_and_ee', 9 );
function my_temp_fix_for_connections_and_ee() {
// change 'registration-checkout' to match *your* Event Espresso registration checkout page
if( is_page( 'registration-checkout' ) ) {
wp_deregister_script( 'jquery-validate' );
}
}
You can add the above to a functions plugin or into your WordPress theme’s functions.php file.
|
|
AmritYoga2015
|
October 3, 2016 at 1:25 pm
I have added the above code to a custom CSS plugin. Issue remains the same
|
|
Josh
|
October 3, 2016 at 1:59 pm
That would be expected since the above code is PHP and needs to be placed into a functions.php file or into its own WordPress plugin. A Custom CSS plugin is for adding custom CSS to a website, it will not load in PHP code.
|
|
Josh
|
October 3, 2016 at 3:08 pm
Update:
You shouldn’t need to apply the temporary fix that that posted above. Event Espresso 4.9.14.p has been released. The code that conflicted with the Connections plugin was removed in the new version.
|
|
cirobe
|
October 3, 2016 at 3:32 pm
Thanks for the responsiveness to this issue, Josh. I’m so relieved we have so quickly narrowed down the issue between the two plugins and the underlying issue.
|
|
AmritYoga2015
|
October 4, 2016 at 8:52 am
updated to EE4 4.9.14 and new formmating issues began. The first name field does not produce any issues now, however in event post page ticket pricing is not displayed and formatting in venue listed has been changed to a “Stretch” kind of row formatting.
Ex. https://amrityoga.org/allevents/integral-breath-therapy-2016/
This issue began with the update
|
|
AmritYoga2015
|
October 4, 2016 at 8:54 am
Also, connection pro active or deactivate does not matter with formatting issue
|
|
Josh
|
October 4, 2016 at 1:46 pm
The formatting bug is fixed in Event Espresso 4.9.15.p.
|
|
AmritYoga2015
|
October 4, 2016 at 2:01 pm
Thank you – That will fix the prices not displaying and the venue formatting?
When will it go live?
|
|
Josh
|
October 4, 2016 at 3:17 pm
It’s been released for a few hours now, and it will fix the formatting issues you reported about earlier.
|
|
AmritYoga2015
|
October 5, 2016 at 7:38 am
Okay great, the formatting one venues is fixed.
We are still having some issues with displaying ticket prices. The ticket options appear, but the prices do not.
Ex. https://amrityoga.org/allevents/womens-retreat-with-jamie-marich/
the two tickets appear with the selector, but the prices are missing?
|
|
Josh
|
October 5, 2016 at 1:54 pm
I see a column for Price, but there appears to be some CSS the actual rows that display ticket information. A closer look at the CSS that’s in the custom CSS plugin output looks like it’s hiding tickets that are not for sale yet, is that the case for the event you linked to there?
|
