Unfortunately, that doesn’t seem to address my issue. I’m more than happy to go digging through the code to change the default sorting, if I have to. We use a slightly modified version of your API to feed content to our mobile app (it doesn’t modify your code as it’s registered as a separate endpoint). The problem is that the data appears to be sorted by post_date. So /events?event_type=upcoming&page=1&per_page=10 shows me 10 event instances with the first two in August, the third in October and the fourth in September, because that’s the order I added them. The second page of results might show something completely different. So when our app pulls down that data, it will show 10 events and then when you scroll to get the next page, it adds events above. We’re working around this by pulling all events down at once, but that brings it’s own set of issues.
The schema parameters for orderby for events shows that post_date is the default and nothing else (whereas the same thing for places shows more options). Is there a hidden way to sort by event_startdate? Because that would resolve all of our issues.
Kiran 7 years, 5 months ago.
