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
Incorrect registration date and time in Attendee Report | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Incorrect registration date and time in Attendee Report

Incorrect registration date and time in Attendee Report

Posted: June 10, 2013 at 10:37 pm

Viewing 12 reply threads


Jake Vizner

June 10, 2013 at 10:37 pm

I registered for an existing event on June 10, 11:50 pm. The date/time shown in Attendee Report is June 11, 3:50 am. Current Time shown under Event Espresso | General Settings is correct.


Dean

  • Support Staff

    •

June 11, 2013 at 3:58 am

Hi,

Is your timezone in the General Settings set to your closest city or UTC? If UTC please change to the closest city.


Jake Vizner

June 11, 2013 at 4:00 am

Time zone is set to New York.

Thank you,

Jake


Josh

June 11, 2013 at 7:48 am

Hi Jake,

This may be from the server’s MySQL date time settings being set to another timezone than EDT. You can check with your host to see which zone it is set at.


Jake Vizner

June 12, 2013 at 11:28 am

This is a response I received from the hosting company support person:
Hello!
Thanks for your message! In regards to the time stamp right here is the only place to make that change:http://d37toastmasters.org/wp-admin/options-general.php
The server itself has it’s own time settings which will always be UTC by default and there is not any way to change that. If the setting at the link above is not doing the trick then some rules will need to be added to the logic of the registration functionality to adjust the timestamp accordingly. Was there anything else that I could assist with?
 


Josh

June 14, 2013 at 8:27 am

Hi Jake,

This gets tricky, because if the scripts that are calling the current time need to be adjusted to offset a time difference, you’ll end up needing to rework a lot of code.

This typically isn’t a problem for most installations of Event Espresso. Which hosting company is the site hosted on?


Jake Vizner

June 14, 2013 at 8:43 am

Hi Josh,

I’m using WP Engine. http://wpengine.com/

Jake


Josh

June 14, 2013 at 10:16 am

That’s good to know. I have a site on WP Engine where I can run some tests. I’ll let you know if I can find any work arounds.


Jake Vizner

June 19, 2013 at 3:04 am

Hi Josh,

Is this a known bug?

Thank you,

Jake


Josh

June 19, 2013 at 9:37 am

Hi Jake,

It’s doing what it’s programmed to do. It’s a known issue in that if the server’s timezone is set to UTC 0, then the attendee data (like registration time) will use UTC 0. In Event Espresso 4.x they’ve changed the entire system over to use UNIX timestamps so that the registration time (and all other features that use current time) will not be affected by the server’s timezone.


Jake Vizner

June 19, 2013 at 4:06 pm

Cool. When do you expect Event Espresso 4.x general availability?


Dean

  • Support Staff

    •

June 20, 2013 at 2:19 am

Soon, very soon. However please remember that 4.0 will not be compatible with a 3.1.X system (i.e. it will need a fresh install) and there will be no add ons initially.


Jake Vizner

June 20, 2013 at 3:39 am

Dean,

Thank you,

Jake
Viewing 12 reply threads

The support post ‘Incorrect registration date and time in Attendee Report’ 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 Jake Vizner 11 years, 8 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server