[wp-trac] [WordPress Trac] #41935: Dashboard WordPress Events and News showing duplicate Meetup postings

[WordPress Trac]

#41935: Dashboard WordPress Events and News showing duplicate Meetup postings
---------------------------+------------------------------
 Reporter:  kamamarketing  |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Widgets        |     Version:  4.8.2
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+------------------------------

Comment (by subrataemfluence):

 When I inspected the endpoint with location Mumbai
 ([https://api.wordpress.org/events/1.0/?location=mumbai]) I found that two
 Meetup events are returned with same Id (241167323), but surprisingly the
 latitude and longitude values are different! The meetup URL is
 https://www.meetup.com/Mumbai-WordPress-Meetup/events/241167323/.

 Question is how two records with same ID can reside in database unless it
 is not the primary key. And are lat and lon being determined dynamically
 when the records are fetched? Only then they could be a little different
 (not always though). If that information was stored in database upfront,
 they cannot be different.

 Another thing I probably have discovered, not sure if this is an issue as
 well. When I login to my dashboard, I can see meetup announcements in
 Mumbai which is far away from my location (about 2000 Km), but when I run
 the endpoint in browser with my location (Kolkata,
 [https://api.wordpress.org/events/1.0/?location=kolkata]) no result is
 returned.

 If Kolkata (this is the timezone set in my application) does not return
 any result then why `$response = wp_remote_get( $api_url, $request_args
 );` is returning meetup events from Mumbai in dashboard but not when I run
 the endpoint separately in the browser? The only possibility could be if
 the code looks for country wide meetups if none found in supplied
 location. Even then when I run the endpoint, I would expect the same
 behavior.

 I am further inspecting the code and trying to figure this out.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/41935#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform