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 Bug Report: Time Zone Issue | Event Espresso - Staging Server
In the general settings, I set my time zone for New York. This seemed to be fine, but when I reached the gateway page (FirstData) I kept getting an error that the “time period for the action had elapsed.”
I took a lot at the source code generated by the PHP on the page directly before the gateway. In the hidden form data I noticed that the correct date and time for my timezone were being sent, but the variable entitled “timezone” was being sent with the value “GMT”. It seems like it should be EST or UTC-3 or something of the sort to show New York. I went back into the general settings for Event Espresso and switched the timezone to UTC and now the transactions go through as they should.
So it seems that, at least with this gateway, when the timezone for New York is set, it is sending the wrong info (GMT) to the gateway, resulting in the error that the transaction appears to be three hours old, since the timestamp was indeed New York Time.
Hey Brian,
There is a seperate timezone setting in the FirstData Connect 2.0 payment settings. Just in case the server is physical location is different than the organization options setting, we wanted to make the system as flexible as possible. Sorry for any confusion.
Thanks.
Viewing 1 reply thread
The support post ‘Bug Report: Time Zone Issue’ 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.