rob66bnu

I can now confirm that the update released in version 5.3 does resolve the issue, allowing us to sell tickets without requiring users to log in. If the purchaser is NOT logged in, the “get tickets” dialog now prompts them for their Name and the Email address they want the tickets sent to. If they ARE logged in, the dialog goes straight to payment method and the system uses the Name and Email address from their user profile. Perfect. Thanks.

I can now confirm that the update released in version 5.3 does resolve the issue, allowing us to sell tickets without requiring users to log in. If the purchaser is NOT logged in, the “get tickets” dialog now prompts them for their Name and the Email address they want the tickets sent to. If they ARE logged in, the dialog goes straight to payment method and the system uses the Name and Email address from their user profile. Perfect. Thanks.

Thanks, @masoodak, I’m looking forward to installing and testing the new version.

Hi @juanfra – Thanks for clearing that up, this is much more acceptable. Respectfully, you had us worried!

@tdorn Your response is unworthy of a serious software company. You should listen to YOUR customers as we are listening to OUR customers, who are telling US that it IS a big deal to have to login to our website just to purchase a ticket. What makes your response even more galling is that you chose to change the way your software has worked for many years without any consideration at all for this reality. Wake up! We are losing sales because, while people are quite happy to provide name and email address as part of the ticket purchase transaction, they do NOT want to mess with registering on our website, especially if they view this purchase as a one time relationship with us. Since your software used to allow this approach it can’t be that difficult to incorporate it into the new Tickets Commerce solution. Get busy!

Was your customer logged in? This sounds like the same as the problem I reported nearly a week ago tickets-commerce-not-collecting-email-address-if-purchaser-not-logged-in/ and have yet to receive an acknowledgment from the developer.

Yes, that does the trick. Thanks, Rafsun.

I am abandoning Tribe Commerce and shifting to the new Tickets Commerce introduced in Event Tickets v5.2

Question: does Tribe Commerce use Access Control List (ACL) or filters on IP addresses for the IPNs received from PayPal? If so, did you add the new IP addresses that PayPal introduced on May 1, 2021? According to PayPal, “Doing so will help avoid missing IPNs from PayPal.”

Thanks, Sky. The suggested interim fix works for me and I appreciate your prompt support.

Thanks for sharing this. It’s a great feature that should be in the core plug-in.

For pages that have multiple reports (and I have several), I found it necessary to change the line:
var $title = $(“.ELISQLREPORTS-Report-Name”)[0].textContent;
to:
var $title = $(this).siblings(“.ELISQLREPORTS-Report-Name”)[0].textContent;

so that exported file name for every report matches its own report name (instead of them all taking the name from the first report on the page).

When I checked back, the second change had propogated from WP to MC so the connection appears to be working normally.

The mc4wp General Settings page is STILL showing 503 Service Unavailable message and Status = Not Connected. That is misleading and a time waster. Fix that and I’ll be happy. ??

Thanks for your help. My host provider is GoDaddy.

Looking at my MailChimp.com Account > Extras > API keys page, I see my SSH curl call from yesterday with Source IP 45.40… followed by a series of mc4wp calls from this morning with source 72.167…144. All appear to have been handled successfull (Result = check, Throttled = nope, Response = n/a).

In WordPress, the mc4wp General Settings page is still showing 503 Service Unavailable message and Status = Not Connected, BUT my list is now showing correctly in the MailChimp Account section at the bottom (it wasn’t before) AND the MailChimp User Sync page is now correctly populated with the list name and additional fields (these were not available before).

I made a trivial change (in the bio info field, which is NOT passed to MC) to one user and the mc4wp Debug Log reported “Sync > Successfully updated user 4 …”. In the MailChimp.com Account > Extras > API keys page, I see two new mc4wp calls from 72.167…126 with corresponding timestamp.

Next I changed the same user’s first name (a field which IS passed to MC) and saved it. That change was about an hour ago but has not been logged in the mc4wp debug log, nor are there any new entries in the MC API keys log. Is a delay normal?

I’ll check again later and report back.

Thanks for the quick response.
Selecting “Record “IP address Cache”” in “Privacy and record settings” did the trick.