Eventbrite v3 Search API is deprecated. Turning off Feb 20, 2020
mrwweb opened this issue · 6 comments
From any email I just received from a client:
We’re writing to inform you of some changes we’re making to our APIs and the steps you need to take to continue retrieving your events without disruption. Effective December 12, 2019, we’ll be removing public access to Eventbrite Event Search API (GET /v3/events/search/). However, as an Eventbrite creator, your API keys have been whitelisted to access this API until 11:59 pm PT on February 20, 2019.
Starting December 12, 2019, until February 20, 2020, each of your API keys will be able to make up to 10 requests per minute (the previous limit was 1 request per minute). During this period, we strongly encourage you to find and remove any code that makes requests to this Event Search API from your applications. Moving forward, you’ll be able to retrieve your events through one of the following Event APIs:
- Retrieve an Event by ID - GET /v3/events/:event_id/
- List Events by Venue - GET /v3/venues/:venue_id/events/
- List Events by Organization - GET /v3/organizations/:organization_id/events/
What happens after February 20, 2020? After February 20, 2020, all requests to the Event Search API will be denied so you’ll need to retrieve your events via one of the above APIs.
We apologize for any inconvenience this change may cause, and thank you for your understanding. For questions, please reply to this email.
Will the plugin be updated to use a non-deprecated API or will the plugin essentially die on February 20?
I also got an email from a client about this, and am wondering what will happen. Following this ticket now...
Thanks for bringing this up. It looks like the search endpoint was already shut down this past Dec 12, after a few months of performance and stability issues. Hm, that would also mean any new users of this plugin without existing active keys would find all search-related functionality broken. And the endpoints they suggest as alternatives don't cover half of what the search endpoint covered (and was supported in this plugin through the query args).
It will come as no surprise that this plugin has not been high priority for continued development, and with the growth of Gutenberg, it was always my hope that this plugin would eventually be replaced by some superior Gutenberg equivalent, down the road. We'll need some internal discussion of how to proceed, and will update this issue.
Internal discussion: p58i-8p5-p2
We've decided we will not be investing in a rewrite of the plugin to mitigate the unsupported endpoints. We've deprecated our own WP.com Eventbrite integrations, and hope to move forward at some point with Gutenberg-based solutions – however, we have no timeline for this. So what are your options?
Note that for those that built on Eventbrite_Query (which includes the default templates and eventbrite_get_events), forcing the display_private arg to true may be the easiest workaround; this makes the plugin call the user-owned events endpoint instead (/v3/users/:user-id/owned_events/), which seems to still be running well. That, combined with some filtering, may be all some users need to get an equivalent experience.
While there doesn't appear to be the equivalent of a list of events, Eventbrite does have their own iframe-based widgets for embedding into websites; another end-user option would be WordPress posts/pages using those widgets for each event.
While I haven't used it myself, Modern Tribe is a respected agency that produces their own (paid) Eventbrite plugin, making that an option for some.
Lastly, if someone in the community wishes to fork this repo and go forward with it, I'd be happy to add notices to this plugin suggesting the newer one. There was a huge PR that apparently fixed some issues; maybe starting from that would be a good idea (or not, depending on whether the changes are related to the now-dead search endpoint).
I'll do my best in the future to update this issue with any public Eventbrite Gutenberg block releases related to Eventbrite.
FYI, I forked this plugin into my own plugin a year or more back when Automattic reported they would abandon it. SInce then I have dealt with removing 'keyring' dependency and solving many deprectaed end issue - but that said my revised library dosen't cover everything the orig API plugin does. And Search endpoint - there is not solution for - EB are just defending their servers and brand from search aggregators - and I see not solution unless EB provide one.
I'm currently working on converting my (limited) public widget solution into a (limited) public gutenberg block solution. It will go on the repo into the existing widget plugin.
Listings still working, but oddly images are no longer pulling through.
Using (below) worked previously.
<?php the_post_thumbnail(); ?>