BuddyPress.org

I just glanced at the code for the members, who’s online, groups widgets and see that, yes, they want an arg. No default is specified. What they are looking for is an array argument. As far as I can see none of the widgets are using that args array yet. Try a dummy arg.

$my_dummy_arg = array(‘this is useless’);

bp_core_widget_members($my_dummy_arg);

or

bp_core_widget_members(array(‘nothing to see here move along’));

It’s complaining about a PHP function extract() that the widget uses at the top of the widget function. extract() wants an array. Give it one.

Well, I don’t see any way of modifying the behavior of the widget with args at all. What we’re missing here is a template tag type function that takes the place of just using the widget as a widget. It’s after midnight so maybe I’m just missing it in the code someplace.

I see examples all over the place of widgets like the standard wp ‘archive’ widget that displays a selection of months in a sidebar. There is also the template tag wp_get_archives(‘type=monthly’) that takes the place of a user selecting that widget, configuring it and then loading a page where the widget should display.

Such a thing doesn’t seem to exist for bp and the core widgets yet. Besides that, calling the members widget like that doesn’t include some javascript that the widget depends on.

Looks to me like you’re going to get default behavior with that call. Like I said, maybe I’m missing something. Anybody else got a suggestion?

Well, a good place to start would be the widget code itself.

Let’s take the ‘archives’ widget as an example. I look at the widget code in: /wp-includes/widgets.php for the archive widget function: function wp_widget_archives($args), I see that it extracts the stored widget options and then eventually calls the template function: wp_get_archives(‘param=xxx&param=yyy’). The widget is just a wrapper for the template function that allows blog admins to set the behavior of the template function that does all the work.

We need to pull the guts out of the members widget and create a template tag that does the work by parameters only. Looking at the archive widget again I see some code that sets up defaults, parses the passed args and then turns the args array into vars with extract().

We could also just modify the widget to parse and actually pay attention to passed args.

In any case did I mention that ‘We don’t need no stinking help’. (that was my best Mexican bandito accent). I forgot you are Italian. That was a reference to a Western movie. Never mind. I gotta go play with something else right now but I’ll return to this.

Any luck with limiting the number of members?