Checkout unavailable error even after connecting Paypal

Interesting, I get a similar result with a staging server on a windows setup. PayPal seems to connect ok, but when I go back to the Tickets Commerce tab there isn’t the green text to show it is connected. (You don’t seem to have the green text either.) I can see some errors in the Javascript console, do you?

I created a fresh install with versions as below (and no other plugins) and got the same result:

WordPress version
6.6.2
PHP version
8.2.12
Theme
Twenty Twenty-Four
Plugins
Event Tickets version 5.16.1 by The Events Calendar
The Events Calendar version 6.8.1 by The Events Calendar
Common Library Dir
C:\xxxx\fresh\wordpress-6.6.2\wordpress\wp-content\plugins\event-tickets/common/src/Tribe
Common Library Version
6.3.1

Hi @manifestdev ,

Thank you for reaching out.

We’ve seen this happen with PayPal test (or sandbox) accounts being connected with another e-commerce platform. Have you tried connecting Tickets Commerce to a different PayPal sandbox account or switching to a live PayPal account?

Essentially, when a handshake is successful between Tickets Commerce and PayPal, there should be a “Enabled for Checkout” notice in Tickets -> Settings -> Payments (tab) -> Tickets Commerce (sub-tab) — see https://go.screenpal.com/watch/cZXI6enV1fo.

Hello @tristan083

Thank you for your reply here.

We have tried 2 different Paypal account and getting the same result in both the cases.

Here I have recorded a video while connecting a new sandbox account, https://capture.dropbox.com/CiAkryRfdqEGjhvx

Please review the video and let me know if we are doing anything wrong. The green line you have shown in your comment is not being reflected on my end.

Hello @tristan083
Can you please look into our query and suggest a fix?

We need to complete the project at the earliest.
Thank you.

Hi @manifestdev ,

Thank you for your message and the information.

Regrettably, I have not been able to reproduce the issue in my WordPress testing environment and PayPal sandbox to be able to provide an adequate solution. Does the issue persist when connecting Tickets Commerce to a live PayPal account?

Hi @manifestdev

I hope you’re doing well. I just wanted to touch base and check in with you. It’s been a little while since we’ve heard from you. I was just curious if you had the chance to try out the recommendation provided above.

Let me know if there’s anything I can assist you with.

I still get the same error after doing another fresh install with WordPress 6.7.

These two plugins and nothing else:
Event Tickets version 5.17.0 by The Events Calendar
The Events Calendar version 6.8.2 by The Events Calendar

Attempting to connect in Paypal test mode always gives this error:

Uncaught TypeError: referenceNode.parentNode is undefined
insertAfter https://nntest.local/wp-content/plugins/event-tickets/common/src/resources/js/tec-a11y-dialog.min.js?ver=6.3.2:11
render https://nntest.local/wp-content/plugins/event-tickets/common/src/resources/js/tec-a11y-dialog.min.js?ver=6.3.2:11
show https://nntest.local/wp-content/plugins/event-tickets/common/src/resources/js/tec-a11y-dialog.min.js?ver=6.3.2:11
maybeShowModalAfterConnection https://nntest.local/wp-content/plugins/event-tickets/src/resources/js/admin/tickets-commerce-settings.min.js?ver=5.17.0:11
maybeShowModalAfterConnection https://nntest.local/wp-content/plugins/event-tickets/src/resources/js/admin/tickets-commerce-settings.min.js?ver=5.17.0:11
ready https://nntest.local/wp-content/plugins/event-tickets/src/resources/js/admin/tickets-commerce-settings.min.js?ver=5.17.0:11
jQuery 13
tec-a11y-dialog.min.js:11:4298

When I debug this I find that referenceNode is not a node but an array containing one node:
button#paypal-connected-modal-button.tribe-button

The render function supplies referenceNode like this:

if (this.options.appendTarget.length) {
    appendTarget = document.querySelectorAll(this.options.appendTarget)[0] || this.trigger;
}

In my case this.trigger is being used, which is an array. If I change the code to this.trigger[0] then I don’t get the Javascript error and the success dialog now shows. However, this doesn’t appear to solve all the problems because the Tickets Commerce tab does not show that PayPal is connected with the green text.

If you don’t see this Javascript error in your test environments can you confirm that you only have these two plugins installed and active. i.e. no other related or pro plugins.

Thanks

Hello Darian,
Thanks for the message, the status is same as it was.

Its now working.
I tried a couple of new Paypal Sandbox Accounts as well but none of them worked!
The green line you mentioned is not coming there on the payment settings page.

Hi @meet1347 ,

We have an internal bug report with our product team, investigating this issue. I have added this support thread to the bug report so when any update is available, you’ll be notified through this thread.

Your patience on this matter is highly appreciated.

—

Internal Bug Ticket Reference: ET-2244

One other thing I would say is that I got the same Javascript error when testing on a live url with a valid SSL certificate and attempting to connect with a PayPal sandbox account of type Business. (I pasted the error from a localhost testing environment.)

A minor error also worth noting is that the PayPal partner.js request always get redirected with a 301 permanent redirect.

https://paypal.com/webapps/merchantboarding/js/lib/lightbox/partner.js

Should be:

https://www.paypal.com/webapps/merchantboarding/js/lib/lightbox/partner.js

The PayPal examples in their docs have the “www”.

The address seems to be put together with Client.php and get_home_page_url()

We appreciate the information, @max-dayala ! I’ll be sure to add those information in the bug report.

Hi,

We prioritize bugs by taking into consideration the number of users impacted as well as how the bug impacts one’s ability to run an event/sell tickets. I don’t have a specific timeline as to when this issue will be resolved, but trust that our team is aware. Our team communicates updates and bug fixes in our newsletter and via our changelog. We will also be updating this thread once the fix is out.

I’m happy to help if any other questions are coming up around this topic, otherwise I’ll go ahead and close this ticket for now.