Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Timezone Fatal Error | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Timezone Fatal Error

Timezone Fatal Error

Posted: April 18, 2013 at 6:29 am

Viewing 3 reply threads


Christopher Crowhurst

April 18, 2013 at 6:29 am

When I attempt to edit an event from the Event Overview Screen I receive this error message:

Uncaught exception ‘Exception’ with message ‘DateTimeZone::__construct() [<a href=’datetimezone.–construct’>datetimezone.–construct</a>]: Unknown or bad timezone (UTC-6)’ in /home/content/22/8813822/html/wp-content/plugins/event-espresso/includes/functions/time_date.php:534 Stack trace: #0 /home/content/22/8813822/html/wp-content/plugins/event-espresso/includes/functions/time_date.php(534): DateTimeZone->__construct(‘UTC-6’) #1 /home/content/22/8813822/html/wp-content/plugins/event-espresso/includes/event-management/edit_event.php(500): eventespresso_ddtimezone(‘1’) #2 /home/content/22/8813822/html/wp-content/plugins/event-espresso/includes/event-management/index.php(95): edit_event(‘1’) #3 [internal function]: event_espresso_manage_events(”) #4 /home/content/22/8813822/html/wp-includes/plugin.php(406): call_user_func_array(‘event_espresso_…’, Array) #5 /home/content/22/8813822/html/wp-admin/admin.php(151): do_action(‘event-espresso_…’) #6 {main} thrown in /home/content/22/8813822/html/wp-content/plugins/event-espresso/includes/functions/time_date.php on line 534

The Event Timezone is set to UTC-6

other pertinent data shown is:

UTC time is 2013-04-18 12:25:30
Local time is 2013-04-18 6:25:30
This timezone is currently in standard time.

I am using Version 3.1.31.1

And running WordPress 3.5.1

Does anyone have any advice?

Thanks


Christopher Crowhurst

April 18, 2013 at 6:50 am

As an update, if I disable custom timezones then the page renders without errors.

I have confirmed that I my general setting timezone is set to Chicago.

 


Christopher Crowhurst

April 18, 2013 at 7:00 am

Okay I have now resolved this issue. Here is what I discovered.

 

What I did to cause the issue:

Originally I had created 4 events with my wordpress systems timezone set to UTC-6.

I then enabled custom timezones. I then created an event in London timezone.

This event worked great. All my previous events then error-ed out as described.

What i did to fix the issue:

1. I changed my WordPress system timezone to Chicago having seen the warning about UTC settings.

2. I then turned off custom timezones.

3. I then opened each of the previous event, and resaved them – this caused the timezone to be reset to Chicago from UTC-6.

4. I then re-enabled custom time zones and everything is happy.

So the moral of the story is you must never use UTC timezone settings!!


Dean

  • Support Staff

    •

April 18, 2013 at 11:45 pm

Hey,

Sorry for the delay in responding, but glad that you worked things out, and yes UTC timezones are a no no!
Viewing 3 reply threads

The support post ‘Timezone Fatal Error’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Dean 11 years, 10 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server