Forum Replies Created
-
AuthorPosts
-
scottlyttleParticipant
Hi George,
The code that should be updating the currency came from the Events Calendar website: https://theeventscalendar.com/knowledgebase/change-the-currency-for-eventbrite-tickets. If this code no longer works could it please be removed or updated.
I don’t quite understand what you mean about the payment info requirements. Do you mean that everyone using The Events Calendar with the Eventbrite add-on must go to Eventbrite and enter the payment info after creating a new event in WordPress?
To answer your last question, the publishing of the event to Eventbrite is working fine, with or without your custom code.
November 16, 2015 at 2:39 pm in reply to: Event ticket form no longer showing on front-end after update to 3.12.1 #1026622scottlyttleParticipantHi Nico,
I updated to the new release (3.12.6) and the previously published public events now have their ticket boxes showing. Awesomeness! Whatever was in that update seemed to work. Either that or it was due to a API change on Eventbrite’s end. Nonetheless thanks for you help.
Cheers,
Scott- This reply was modified 8 years, 5 months ago by scottlyttle.
November 9, 2015 at 2:09 pm in reply to: Event ticket form no longer showing on front-end after update to 3.12.1 #1023458scottlyttleParticipantThis reply is private.
November 9, 2015 at 1:14 pm in reply to: Event ticket form no longer showing on front-end after update to 3.12.1 #1023435scottlyttleParticipantThis reply is private.
November 8, 2015 at 8:13 pm in reply to: Event ticket form no longer showing on front-end after update to 3.12.1 #1023120scottlyttleParticipantAnother point for the troubleshooting:
tribe_eb_get_ticket_count()
is returning the correct number so it appears the site is connected to Eventbrite.
scottlyttleParticipantHey Barry,
Thanks for getting back to me. Makes sense, I guess.
I’m curious why the ticket numbers are linked to the ticket’s ID?
Could some meta get saved along with the ticket – like ‘start_ticket_number’ set to ‘0’ – and then the ticket number iterates upwards from there (re-saving the meta value on purchase) each time that type of ticket is sold?
Vague example I know, but it seems more intuitive for each type of ticket to count from 1 up to the maximum available of that ticket, as apposed to the very first ticket sold being a random number like #43,816.Cheers
-
AuthorPosts