Posted: May 1, 2023 at 2:31 pm
I don’t remember noticing this before, but I had a bunch of late night registrations yesterday that highlighted this situation, so maybe I just never noticed – the date/time groups in csv export files is in Zulu (GMT+0), while I’m in the GMT-8. WordPress Settings/General Timezone is Los Angeles, which is correct. EE4 General Settings/Your Organizations is San Diego CA 92111, US which is the same GMT-8. I saw another post in here about this problem – response was basically set your city correctly and that will take care of the problem; but the settings were already accurate so that’s not it, unless there’s another timezone setting somewhere. Thanks! |
|
Hi Michael, This is what I see in my csv report. The time format is 24-hour clock, but the time of registration is correct: https://www.screencast.com/t/hHc0FRac4GI |
|
Ok, fine, but here’s what I’m seeing https://www.ninthdistrictpta.org/wp-content/uploads/2023/05/Screen-Shot-2023-05-16-at-9.18.29-AM.png Same registration, PII blanked for the usual reasons, time is different by 7 hours and a few minutes. My local time right now is -7 from GMT. So, after looking at this, the dates puzzling me are Col W Payment Dates apparently being reported in GMT or something, but Col N Time Registration Occurred seem correct to me. Maybe you could explain why they are so different but for now I guess the solution to my problem is to use Col N. Is that the time when the buyer gets the COMPLETE confirmation screen or something like that? Thanks! |
|
Can you expand the columns so it’s clear what the column labels are? What payment gateway are you using? |
|
expanded view is at https://www.ninthdistrictpta.org/wp-content/uploads/2023/05/Screen-Shot-2023-05-17-at-5.07.28-PM.png with a selection of several. I added the “difference” column which is Payment Date minus Time Registration Occurred. Always 7 hours and a few minutes. I know from experience that the payment confirmation comes to buyers immediately, not 7 hours later, so that makes me think that is somehow is GMT, not my -7. I think I can live with this as-is now that I’ve discovered the Registration Occurred date/time is more correct, especially if it’s a Braintree artifact since I think we will be giving that up in favor of some other method. Thanks! |
|
Another thought – tickets have an on-sale end date/time-which of these fields is tied to that? |
|
The support post ‘Time coming out in Zulu (GMT+0)’ 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.