[Barry]

Hi Douglas,

I’m sorry to hear that your test from Friday didn’t work. The log data makes me wonder if the entire transaction was processed using something other than our own Tribe Adaptive Payments gateway – and if you have any further feedback on that count we’d love to hear from you.

I think I’ve fixed it – I deactivated PayPal Payments for WooC. and the payment was split properly.

Great! Are the problems now resolved?

[Barry]

Great – and please don’t hesitate to let us know if you need further assistance (once this topic is closed, you can of course link back to it if helps to provide context in a future exchange).

[Barry]

Ah, I see – so yep you’d create a further personal or business sandbox account over at developer.paypal.com, for instance I was recently conducting tests using a set of three accounts like so:

• [email protected] (business – entered as the receiver email in Events → Settings → Community)
• [email protected] (personal – used as the organizer’s email address in events/community/payment-options)
• [email protected] (personal – used for the customer purchasing the ticket or tickets)

Does that clarify things?

[Barry]

Well, to be clear, the adaptive payments gateway bundled in our own plugin in no way negates or impedes the functionality of WooCommerce’s own PayPal gateway – but if both are enabled there is definitely potential for confusion and a customer could unknowingly select the wrong one.

how exactly do i enable an organizer’s email? in the Business addresses in Sandbox?

So this is really something (typically) the organizer themselves would set up. If in testing you are in control of the organizer’s user account then of course you can take care of it 🙂

Basically, if the organizer visits the events/community/list page (assuming default slugs) they’ll see a Payment Options link: they should click through to this and add the correct PayPal email address there.

Does that help?

[Barry]

Hi Douglas,

thanks – this sounds like the problem: “…that all accounts – including that of the organizer – are also Sandbox-enabled”

Taking the time to confirm this is definitely worthwhile. A live PayPal account cannot receive funds from a sandbox account and vice versa.

I’ll look over our setup guide and see if we can emphasize this – please do let me know if that proves to be the answer.

Do you mean that there are different PayPal API credentials?

So in the list of active plugins you provided I see an entry for PayPal for WooCommerce by Angell EYE and, of course, WooCommerce also ships with a PayPal gateway out-of-the-box. If either is enabled and payment was processed using one of those, split payments would not function as expected here.

Does that make more sense?

[Barry]

Hi Douglas,

Thanks for those credentials: generally we do not login to customer websites but let’s keep that as an option we can use if needed.

At this point, I want to be absolutely sure we’re on the same page – let’s assume we have the following actors:

• Site owner [email protected]
• Event organizer [email protected]
• Customer [email protected]

So long as the event organizer has provided their email address via the /events/community/payment-options page and it maps to a valid PayPal account, etc, then assuming there is a flat fee of $5.00 things ought to flow like this if $200.00 of tickets are purchased:

• $200.00 flows from [email protected] to [email protected]
• $195.00 flows from [email protected] to [email protected]

What you seem to be telling me is that the first part of the process is working as expected (the site owner is receiving the expected funds) but nothing is transmitted from there to the organizer. Is that correct? If so can you please confirm that:

• The event organizer did indeed provide their PayPal email address via the /events/community/payment-options page
• If you are testing via the PayPal sandbox that all accounts – including that of the organizer – are also Sandbox-enabled

I do realize you’ve been seeking help for various things in a few different support threads, but it wasn’t absolutely clear to me that these bases were covered so I wanted to check now before going any further.

Beyond this, I wonder if you could follow the steps described here (you may anyway be watching this one for updates?) to enable error logging for split payments specifically then try another couple of test transactions – it’s not impossible that we’ll get some useful information coming back from the PayPal API.

Last but not least, it looks like you have an additional PayPal gateway installed. Could this be confusing things? Are you certain that in your tests you are utilizing the PayPal gateway packaged with Community Events Tickets?

Thanks once more for your patience and cooperation: I do realize how frustrating this is but we’ll do our best to work through this with you.

[Barry]

Hi Sara,

Thanks for your patience so far.

I work alongside Josh here at Modern Tribe and wanted to update this topic before the weekend arrives, as though we probably won’t be able to respond again before Monday morning I figured we could set in motion another test and possibly capture some useful data before then.

Can I ask you to temporarily add the following line of code in a suitable location (such as a custom plugin, a mu-plugin file or even your theme’s functions.php file – the latter often being the easiest if you’re already familiar with that approach):

add_filter( 'tribe_community_tickets_woocommerce_paypal_debug', '__return_true' );

This simply ensures that various bits of potentially useful information are recorded when things go wrong. With that done, please try to recreate the problem.

Next, visit WooCommerce → System Status → Logs and you will hopefully see a dropdown near the top right corner of the screen containing an option named something like tribe-adaptive-payments-abc012xyz (date). If there is more than one option with the same prefix, please select the most recent by date and click on View.

You should then be able to see various bits of information that our plugin logged while trying to process the transaction. Can you copy this and share it in here by private reply? It is probably a good idea to save it as a plain text file and share via a Dropbox link or similar if that’s possible on your end.

Thanks so much for your continued cooperation: Josh or I will check back in as soon as we can.

[Barry]

Hi Douglas,

I’m sorry to hear you have been experiencing difficulties.

Before we get started in earnest, can I ask you to share (by private reply) your system information? I’m particularly interested to know which version of Community Tickets you are using.

Apologies for the inconvenience, however I did scan back through some of your previous topics to see if I could find the information there, but none seemed to have it (and of course this request may apply to a different site).

Thanks!

[Barry]

Hi Aindreas,

In terms of which template renders the additional fields, it is the following Events Calendar PRO template:

pro/modules/meta/additional-fields.php

If you are asking where the list of names and values comes from, it’s from a call to tribe_get_custom_fields() made in:

Tribe__Events__Pro__Single_Event_Meta::additional_fields()

The above class is located in src/Tribe/Single_Event_Meta.php within the Events Calendar Pro plugin directory.

[Barry]

Is there maybe an article you could send me a link to for working with those custom fields?

Sure, we’ve got this:

theeventscalendar.com/knowledgebase/pro-additional-fields

PS: maybe leave this ticket open and if I do find the reason its not working I will post it here

Sounds good (though do note topics are automatically closed after two weeks by our support droid, but of course you can always create a fresh topic and post your findings there – and simply link to this one).

[Barry]

Hmm, not seeing anything there that would obviously conflict, but unless I was looking at the wrong WB Yeats event (is there more than one?) something still doesn’t feel right.

Ordinarily, with an additional field like the one we discussed in place, I’d expect to see something along these lines in the grey meta area:

This is notable by its absence on the WB Yeats event/any of your events, which is why I wanted to double check if you either had customizations in place or if you were certain you had supplied a value for that field.

Ultimately … I’m sorry we’ve not been able to get you on track here, but since this is really a customization task we may need to bail out at this point and leave it in your hands – as the suggested solution does seem to work as expected on a clean test site.

[Barry]

Hi Nahar,

Please do create a new topic of your own and one of the team will be happy to help 🙂

We often find having more than one voice in the same topic – with potentially separate (if superficially similar) problems and people at different stages of the troubleshooting process – can get a little confusing.

Thanks!

[Barry]

Hi Aindreas,

Just checking in here as some gremlins in our forum software may have caused you some problems if you tried to reply yesterday.

How are things coming along?

[Barry]

How odd!

There remains a discrepancy in terms of what we both see as, looking at your test site in Firefox (44) running on OS X, I still do not need to hit any button to see the changes (in fact no such button is even visible) — but as you say if this isn’t a big worry we can move on and see if those two plugins are indeed the source of the main conflict.

Let me know how you get on 🙂

[Barry]

Hi Dien – how are you getting on here? Did you find you were able to get things working with Firefox on a clean installation, in the end – or are you still hitting up against difficulties?

[Author]

Posts