[Cliff]

This reply is private.

[Cliff]

Sorry for the delay getting back to you.

I passed this along to our developers as a bug report, same issue as reported here.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I’m uncertain, but the tribe_eb_api_sync_event filter in /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php filter might come in handy if you need it fixed before we release the fix.

If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.

I apologize for this issue and appreciate your understanding and patience.

[Cliff]

This reply is private.

[Cliff]

Thanks for that. I’ve passed it along to our developers.

You might try downloading your .ics file, copying the TZID line and change “TZID” to “VTIMEZONE” — so that you have both TZID and VTIMEZONE in the header of the .ics file — and then manually import that .ics file (not the URL).

If you do try this, please report back your findings.

[Cliff]

Note that I re-opened this and set it back to Pending Fix.

It should not have Closed.

Yes, this bug is still outstanding but is a priority issue.

[Cliff]

Does changing this event’s timezone to New York time fix it (i.e. change the JSON-LD in your page source)?

[Cliff]

I dug further into this and see it is documented on their API site at https://www.eventbrite.com/developer/v3/response_formats/event/ (but their search box on this site doesn’t work)

From their API, I see their valid statuses are:

• canceled
• live
• started
• ended
• completed

Looking into the code for our Eventbrite Tickets add-on, it seems we check exclusively for ‘live’ for whether or not we should display the tickets.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

In the meantime, you can choose to do the following to get it to work (although it’ll still show “Draft” in the wp-admin Event edit screen):

• on your server (via SFTP or cPanel File Manager, for example), navigate to /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php
• Replace all of that single API.php file’s contents with this version: https://gist.github.com/cliffordp/43727f6a982aa2638e06c2f838ae6a98 — make sure to first click “Raw” and then copy the entire contents and paste it in API.php

Of course, we always recommend restorable database and file backups before modifying anything on your site.

Also note that if this fix isn’t included in the next Eventbrite Tickets update(s), you’ll have to keep manually making this fix and it may not be advisable to use this version of API.php with future versions of Eventbrite Tickets.

Please let me know how this goes for you.

[Cliff]

A non-recurring event would have a URL like your-site-com/event/event-name/

A single instance from a recurring event series would have a URL like your-site-com/event/event-name/2017-05-10/

However, I see the event URL you shared with me is missing the “event-name” (i.e. the slug) part of the URL and is just your-site-com/event/2017-05-10/, which isn’t right.

Changing your Permalink structure shouldn’t affect this, though.

Could you please provide us an Administrator login so we can use that Rewrite Rules Inspector ourselves? We will not modify any settings on your site, but we still always recommend having restorable database and file backups for your site before giving us a login.

Make sure to post the credentials in a Private Reply if you do choose to share the login.

[Cliff]

Thank you for confirming you read it.

To answer your question:

• When in Sandbox mode, all Sandbox credentials should be used.
• When in Live mode, all Live credentials should be used.

[Cliff]

Thank you. The screenshots came through this time.

Is this by chance a recurring event or a single event that was broken out from a recurrence series?

If not, what if you change the event’s slug from “2017-05-09” to something that’s not a date format, like “my-event-title”?

[Cliff]

Michael, I’ve verified this looks to be similar to a couple other similar bug reports so I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Cliff]

Interesting but excellent work on your and their part.

Thanks for the thorough update!

[Cliff]

Thanks for your patience. Here’s what I’ve found out…

This is the API call URL: https://www.eventbriteapi.com/v3/events/32736564947/?token=YOUR_TOKEN_HERE

And here’s the response: https://cl.ly/3n1G2z1N2v3p

And here’s what gets saved in the postmeta table: https://cl.ly/3c102K2P3l09

The issue here is that Eventbrite’s API returns the “status” as “started”.

I’ve tested a couple other Eventbrite events and didn’t see the status as “started”.

Our Eventbrite Tickets add-on is displaying “Draft” status if it doesn’t recognize the API’s returned status.

I didn’t find “status” in their API documentation so please contact Eventbrite’s support about this issue and report back.

Thank you.

[Cliff]

Please reference https://theeventscalendar.com/support/forums/topic/help-setting-up-paypal-api-for-split-payments-in-community-tickets/#post-1068501 and let me know if you have any follow-up questions on this topic before contacting PayPal.

[Cliff]

I didn’t hear any audio in that video and it looks like it took a really long time to eventually get to a PDF URL, which is where it displays that error message.

Obviously, something isn’t right here. Therefore, I’d suggest following these recommended troubleshooting steps for your own site:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you find at /wp-content/debug.log (on your server via SFTP or cPanel File Manager) while purchasing and then trying to PDF-print a ticket.

Then, please share your System Information (while in Testing for Conflicts Mode). That will give me a lot of extra information to help diagnose the problem.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Author]

Posts