WordPress.org

Making WordPress.org

Opened 7 months ago

Last modified 7 months ago

#3261 new defect

Events API: returning past meetups

Reported by: sippis Owned by:
Milestone: Priority: normal
Component: API Keywords: needs-patch
Cc:

Description

At this moment, API is returning yesterdays meetup when location is [Tampere](https://api.wordpress.org/events/1.0/?location=Tampere)

https://dl.dropboxusercontent.com/content_link/3un8EK1iVO82v29qQHJk9K27b3NjrtCavF3VMpSMaWRdO573HUmdPakUmF1dCYxt/file

Also duplicate appearance after meetup modification is visible here, as reported first time in #3027.

Change History (2)

#1 @iandunn
7 months ago

IIRC, the endpoint intentionally returns events within a 24 hour window because timezones add extra complexity in determining when an event is in the past or not. I don't think we have a data source that maps lat/long coordinates to timezones, but there might be a good open source one out there.

We might be able to rely on the user's timezone that gets passed to the endpoint sometimes, but I don't think we'd be able to always rely on it.

#2 @dd32
7 months ago

IIRC The main issue with timezone support was that Meetup.com's API only returned timestamps in event local-time without any form of timezone specifier - so we'd require a city->TZ mapping on our side.

The Geonames data we're using does have TZ information too though which we could use for converting times

Note: See TracTickets for help on using tickets.