Bug accessing "upcoming" and "past" events

[Dominique]

I found a bug and have confirmed with the "console". Using group_id "644616" and status "upcoming" and an empty page value, I get many results. If I then use the same group but I use a status of "upcoming,past" I get NO upcoming events in the results, just a bunch of past events. I tried with a few different combinations of status and it appears that if I include "past" I get no "upcoming" in the results.

Dominique

[Doug Tangren]

On Mon, Oct 29, 2012 at 1:27 AM, Dominique <salt...@gmail.com> wrote:

I found a bug and have confirmed with the "console". Using group_id "644616" and status "upcoming" and an empty page value, I get many results. If I then use the same group but I use a status of "upcoming,past" I get NO upcoming events in the results, just a bunch of past events. I tried with a few different combinations of status and it appears that if I include "past" I get no "upcoming" in the results.

Sounds like a bug. I'll open a ticket. Thanks for reporting the issue Dominique

[Doug Tangren]

I re-read this post and realized I should have asked if your group had upcoming events. The default for that method is to only return events with an upcoming status which could be an empty set. You can change this by setting status to "past". You can combine a list of status by separating with a comma. It sounds like your group may only have past events. Let me know other wise. I wasn't able to reproduce this issue. 

[*Dominique*]

Hi Doug,

As I said, if I used the status "upcoming" I got many results, so I did have upcoming events. :-)

Dominique

--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

[Doug Tangren]

On Wed, Nov 7, 2012 at 11:40 AM, *Dominique* <salt...@gmail.com> wrote:

Hi Doug,

As I said, if I used the status "upcoming" I got many results, so I did have upcoming events. :-)

Ok I'll have a second look.

[Doug Tangren]

On Wed, Nov 7, 2012 at 4:19 PM, Doug Tangren <do...@meetup.com> wrote:

On Wed, Nov 7, 2012 at 11:40 AM, *Dominique* <salt...@gmail.com> wrote:

Hi Doug,

As I said, if I used the status "upcoming" I got many results, so I did have upcoming events. :-)

Since upcoming,past includes both upcoming and past it's possible you won't see any upcoming events on the first page of results if you have many past events, because the default order is desc = false, ordering by time so you will see older items first. Try setting  desc = true, reversing the default order, and you will get the upcoming events in the first page of results.

www.meetup.com/meetup_api/console/?path=/2/events&only=status,id,name,time&desc=true&group_id=YOUR_GROUP_ID

You can also page through the responses by incrementing the offset param from 1 to 2 to 3 and so on. 

[*Dominique*]

Hi Doug,

When I was performing my tests using the console I cleared the page entry so I should have been getting all events. When I was reproducing this via the API I was not specifying a page value so there too I should have received all the results.

I just tried it again with a couple of different groups and it seems to be working fine so I have no idea what was causing the original problem. My guess is a combination of the time change and full moon resulted in the temporary glitch I experienced.

Thanks for your continued efforts fixing/enhancing and I apologize for your wasted time tracking down non-issues like these. :-)

Dominique

[Doug Tangren]

On Wed, Nov 7, 2012 at 4:59 PM, *Dominique* <salt...@gmail.com> wrote:

Hi Doug,

When I was performing my tests using the console I cleared the page entry so I should have been getting all events. When I was reproducing this via the API I was not specifying a page value so there too I should have received all the results.

I just tried it again with a couple of different groups and it seems to be working fine so I have no idea what was causing the original problem. My guess is a combination of the time change and full moon resulted in the temporary glitch I experienced.

Thanks for your continued efforts fixing/enhancing and I apologize for your wasted time tracking down non-issues like these. :-)

Not a problem.