Forum Replies Created
-
Posts
-
Hey there Victor,
I can’t believe I missed your message. Two techs I’d hired were also stumped, so we decided I rebuild the site from the server up and hope the problem goes away… =/
We have removed Dokan, which may have been conflicting (we will never know), and because Community Tickets has its own marketplace-style setup, including adaptive payments.
With the rebuild, I am using Paypal Express (and soon Adaptive Payments) instead of regular Paypal plugin, so referring to below link, will IPN/PDT issue will not apply here?
https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNPDTAnAlternativetoIPN/Is it possible that ETP was getting more than one “payment approved” message from Paypal (because of IPN, or both IPN and PDT) and generating multiple tickets in the order? If this is the case, would it be possible to put in the pipeline that it needs a fix? I wouldn’t ever wish this on anyone.. It has been hell – a lot of annoyed customers, a very angry client, a number of free tickets to customer (to apologise for error), manual data entry/checking, and then there were the costs for the two techs who were stumped. I just hope our site rebuild will mean no further issues with the plugin… So if any action is able to be taken to lead to an eventual fix it’d sure be appreciated! I’d hate for anyone in the situation in future to have have to go through it.
Anyway back to business, next up, it says PDT sends confirmations once and only once. Would this explain why, sometimes, even though I have the autocomplete orders snippet in my functions.php, I still had to go through and manually complete orders occasionally?
The Paypal dev article also says there is “material lag”; I imagine it would only mean a few seconds. This is fine with tickets as you would appreciate – I mean anything up to 5-10 minutes to send tickets isn’t really an issue.
I don’t know how to code, and don’t know the inner workings of what “triggers” ETP to generate the tickets for an order so am very hopeful, in attending to this IPN/PDT issue, we won’t experience the issue again. Moving forward, would you recommend IPN is turned off and to use PDT only, or perhaps visa versa – if that is possible? As I’m not sure of the logic behind the tribe plugins generating tickets the way they do, I’d appreciate Tribe’s collective advice here.
Finally, I have taken your advice and set “WooCommerce Support” settings (wp-admin/edit.php?page=tribe-common&tab=event-tickets&post_type=tribe_events) only to “completed” and “completed”. I am hopeful it will also help with these scenarios:
In the past, I would put, say, 100 tickets on sale, and we’d never sell exactly 100 tickets.. It would always be something less, like 91 tickets. These 9 tickets would be “cancelled orders” – orders that user has put into their cart, gone through to pay but hasn’t completed payment. These extra tickets would also show up for the user in mywebsite.com/abcevent/tickets/, albeit with “cancelled” next to them. Although the ticket says “cancelled”, next to it, there’s not really been a way to prevent it from showing – besides manual deletion from back end (I think?).
It would be great if these incomplete orders instead go back into available tickets – or even better aren’t generated in the first place, so we actually do sell the 100 tickets.In that scenario, if I have selected “completed” and completed” (wp-admin/edit.php?page=tribe-common&tab=event-tickets&post_type=tribe_events), would it be safe to say that this wouldn’t occur and we’d go through the full 100 tickets?
Final scenario: there is a rush of tickets, and one ticket is remaining. Two different users add that one ticket to their cart within a few seconds of each other and complete checkout.
Would this explain why we sometimes have more than 100 tickets being sold, say, 103? A few extra tickets oversold doesn’t bother me, but it would be good to know the cause.Many thanks Victor,
Adam
Thanks Cliff, this is great.
What would I have to change the above code to, to have that column display the full ticket check-in URL instead of just ticket id? I imagine just a simple concatenate.. However I’m not familiar with php!
Hi Stéphane,
I am currently contracting a programmer to link the Events Calendar/Event Tickets Plus API to the Qflow API (http://www.getqflow.com/contact). I hope to open it up for all ETP users as a paid plugin at some stage, but would you be interested in testing it out once it’s ready?
Warm regards,
Adam
Hey András,
Thanks for your help.
I only seem to be able to charge per event with the plugin. You will see extra column in cart totals because of custom coding in my functions.php – hoping to remove this and just use your plugin. The custom coding is the correct fee, however community tickets (total at bottom) seems to be charging $1 plus 5% for 2 tickets (should be $2 plus 5% for two tickets)Hi there Timm,
Can I please ask what code you added/edited to get this to work?
Thanks for your help!
Adam
I found out what was wrong. I didn’t want a particular tier of ticket to show up as it had sold out, so I’d set its (woocommerce product setting) as private. This meant the names & attendees didn’t show up in the event info.
Will go in and manually set on-sale dates as “yesterday” when they run out of stock, but hopefully won’t be too long until out of stock items hide themselves automatically.. I think I saw earlier that it was in the pipeline?
/wp-admin/admin.php?page=wc-settings&tab=products§ion=inventory
