Forum Replies Created
-
AuthorPosts
-
Thomas
ParticipantThanks for the quick bug fix release! Working again 🙂
Thomas
ParticipantSorry for not checking all relevant data upfront and post it here. The direct debit gateway comes with
A plugin often used in Germany to take care of the specific legal issues in the EU.
I am not to familiar with wordpress and woocommerce. The direct debit implementation just seems to be old fashioned/wrong if it doesn’t generate a post for each order position!?
Thank you!Thomas
ParticipantSuffering on the same issue. Glad to hear you are working on it.
TomThomas
ParticipantHi Nico, hi Kris,
thanks for the replies! Since this seemed to be a long lasting nasty problem I debugged it myself. Outcome:
My WordPress allows two different – non AM/PM – time formats: “G:i” and “H:i”
When “G:i” is used the /event-tickets/src/admin-views/meta-box.php in line 127 and 152 will show the AM/PM selector even though it’s not necessary. (The function there tests only on “H” instead of “H” and “G”)
Due to this bug the “ticket_start_meridian” and “ticket_ned_meridian” will be returned by the ajax function when the ticket is saved.
Due to the presence of those meridians it will be attached to the date in event-tickets/src/Tribe/tickets.php in line 372 and 377.
This results in a wrong date string (e.g. “2016-12-15 14:05:00 pm”) which makes “strtotime” return FALSE for every time >= 13:00. FALSE means 0 for timestamp in the date function and returns 1970…. (lines 373/378)
So, long story short:
Easiest would be to add the check on “G” in the admin-view as described above.For all the others with this problem: Temporarily switch your wordpress time format to “H:i”. Afterwards you should not see the “PM/AM” in the ticket creation process anymore.
-
AuthorPosts
