[Plugin: Meetup Widgets] Invalid argument supplied for foreach() in vs_meetup_widgets.php on line 76

I think that you haven’t filled in an event or group ID, and so the plugin doesn’t know what to do.

When you add the single event widget to a widget-area, you can enter the title & event ID – title is optional, but you need the event ID so it knows what to display.

When you add the event listing widget, you can enter title & group ID. Again, title is optional, but the group ID is required.

How to find these IDs.

I have tried to insert the ID, but there is no way, nothing seems to work.
I retrieved my id in the way explained in the FAQ and in the way explained on a meetup forum.
I still have the same error.

Can you tell me the ID of the group you’re trying to list? I’ve tried a few different cases but can’t replicate that error.

I retrieve my id from:

https://www.meetup.com/meetup_api/console/?path=/groups&group_urlname=BusinessBuildingAcademy

so my Id should be 642700.

Thanks a lot.

I don’t see where you’re getting that ID from, but if the group you’re using is “BusinessBuildingAcademy”, you can just use that as the group ID – the widget field understands both group ID and URL name.

Hi ryelle, if I put BusinessBuildingAcademy I get that error.

Hm, unfortunately I can’t replicate the issue you’re having, even using the same group. What kind of server are you on? Would you be comfortable with editing the plugin files to try to debug this issue?

Hello. I’m having exactly this issue on our web site occasionally. I just fixed it by deleting and re-installing the plugin, but it’s very puzzling. Could pages with high numbers of views be hitting limits on the Meetup API, perhaps? This happened just when we announced something on Twitter and got probably hundreds hits in a few minutes.

Looks like the scale of hits we’re getting could easily cause the API to throw an error: https://www.meetup.com/meetup_api/#limits

Probably best to cache the results of those API calls, with a TTL of 30 minutes or something.

Ah, you’re totally right. I’ve been meaning to implement caching for a while now & hadn’t had the time, but if people are running into issues because of it then I’ll make it more of a priority.

I’ve added caching in as v2.0.2, so I’m marking this as resolved.