|
Steve Fallet
|
April 21, 2014 at 11:38 am
I upgrade to EE4.2.1 migrate my data from EE4.1 and now have the following error when I clic on “Register Now” button of an event.
EE2 is the only plugin activated and run on WP 3.9
You can try with : http://practice-bassecourt.ch/events/tournois-de-bois/
Fatal error: Uncaught exception ‘EE_Error’ with message ‘Something went wrong with setting the date/time. Likely, either there is an invalid datetime string or an invalid timezone string being used.’ in /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugins/eventespresso.tmp/core/db_models/fields/EE_Datetime_Field.php:420 Stack trace: #0 /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugins/eventespresso.tmp/core/db_models/fields/EE_Datetime_Field.php(384): EE_Datetime_Field->_convert_from_string_value_to_utc_unixtimestamp(’21 April 2014 1…’) #1 /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugins/eventespresso.tmp/core/db_models/fields/EE_Datetime_Field.php(84): EE_Datetime_Field->_convert_to_utc_unixtimestamp(’21 April 2014 1…’) #2 /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugins/eventespresso.tmp/core/db_classes/EE_Base_Class.class.php(209): EE_Datetime_Field->prepare_for_set(’21 April 2014 1…’) #3 /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugi in /home/www/a73308bd6be61da3ee37d185695d44a2/web/wp-content/plugins/eventespresso.tmp/core/db_models/fields/EE_Datetime_Field.php on line 420
|
|
Lorenzo Orlando Caum
|
April 21, 2014 at 12:32 pm
Hi Steve,
It looks like Event Espresso is having some trouble with your custom date format. Could you please try temporarily changing it to this:
http://cl.ly/image/3S160Z0Q0J36
This option is available in WP-admin –> Settings –> General.
—
Lorenzo
|
|
Steve Fallet
|
April 21, 2014 at 12:46 pm
I change with (F j, Y) but error still there
|
|
Steve Fallet
|
April 21, 2014 at 12:50 pm
I change (G \h i \m\i\n) with (H:i) and now it works !
|
|
Lorenzo Orlando Caum
|
April 21, 2014 at 2:54 pm
Thanks, I was able to duplicate this issue on a test site and I’ve reported it to the developers. We’ll get this corrected in an upcoming maintenance release.
—
Lorenzo
|
