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
4 Hour Difference Between WordPress Settings and Registration Time | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › 4 Hour Difference Between WordPress Settings and Registration Time

4 Hour Difference Between WordPress Settings and Registration Time

Posted: September 3, 2013 at 2:45 pm

Viewing 5 reply threads


Hugo Azzolini

September 3, 2013 at 2:45 pm

Hi.

There seems to be a discrepancy between WordPress’ time settings and when the event is recorded as registered.

Is the ‘Registered’ field (as circled in the linked image: http://imgur.com/0uAedhr generated by WordPress, EventEspresso, our payment Gateway, or some other source?


Anonymous

September 3, 2013 at 3:53 pm

Hi Hugo,

The Registered field is generated through EE but through WordPress :)

If you go to Event Espresso -> General Settings.
Under Organisation Settings you’ll find. Time and Date settings.

I’m going to guess its about 4 hours out based on your title :D

You’ll see a link under it to change the setting which takes you to the WordPress Options page to set it. At a guess you’ll currently be set for UTC. You need to chose a Timezone closest to your city and NOT UTC times.

This should fix the issue.


Hugo Azzolini

September 4, 2013 at 7:17 am

Perhaps I am missing something.

WordPress is set to New York’s timezone: http://imgur.com/5EkEEN8

And EventEspresso is consistently displaying the time: http://imgur.com/iWuDC1p

And yet the discrepancy persists.

I don’t have access to the authorize.net account- it seems to be the only other possible culprit.

Is it possible that the ‘Registered’ field is being pulled from there?


Hugo Azzolini

September 4, 2013 at 7:20 am

EDIT:

The images can be seen here:

http://i.imgur.com/5EkEEN8.png

http://i.imgur.com/iWuDC1p.png


Josh

September 4, 2013 at 12:23 pm

Hi Hugo,

Is the ‘Registered’ field (as circled in the linked image: http://imgur.com/0uAedhr generated by WordPress, EventEspresso, our payment Gateway, or some other source?

It turns out that the time discrepancy is from a time zone setting on your server. I’m afraid there isn’t much that can be done about this by the current version of Event Espresso. The way Event Espresso uses dates and times is dependent on the server timezone being set the same. Future iterations of Event Espresso (starting with Event Espresso 4.0) will have a different system in place to record the date times and this issue will no longer happen.


Hugo Azzolini

September 5, 2013 at 8:41 am

We’ll sic our server admin on the issue.

Thanks Josh.
Viewing 5 reply threads

The support post ‘4 Hour Difference Between WordPress Settings and Registration Time’ 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 Hugo Azzolini 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server