It’s something that I want to work on, but I haven’t got time. I contribute to BuddyPress and do BP consultancy and plugin development in the evenings and weekends (or at lunch, as you can see from this reply). Something else I really want to do is contribute features and patches directly to the BP core, which I’m trying to do for 1.3.
Split between reading virtually every thread on these forums (helping and/or moderating where I can), attending the fortnightly BP Dev Chats, keeping an eye on tickets in the (bug) tracker, supporting two existing plugins and doing client development work… it’s just crazy. It reminds me of this post, by Jeff Sayre — “I’m BuddyPress-ed for Time”.
So the only way I can possible do this is in a decent time frame is dropping one of the above, or if someone wants to hire me to do build on the search.
It’s something that I want to work on, but I haven’t got time. I contribute to BuddyPress and do BP consultancy and plugin development in the evenings and weekends (or at lunch, as you can see from this reply). Something else I really want to do is contribute features and patches directly to the BP core, which I’m trying to do for 1.3.
Split between reading virtually every thread on these forums (helping and/or moderating where I can), attending the fortnightly BP Dev Chats, keeping an eye on tickets in the (bug) tracker, supporting two existing plugins and doing client development work… it’s just crazy. It reminds me of this post, by Jeff Sayre — “I’m BuddyPress-ed for Time”.
So the only way I can possible do this is in a decent time frame is dropping one of the above, or if someone wants to hire me to do build on the search.
Codex.buddypress.org is only as good as the amount of people who bother to contribute to the documentation. Failing that, reading the code (if you can read code) is always a good way.
The only parameter that bp_group_list_admins() takes is an optional group object; it defaults to the current group object from the bp_groups templatetag loop. You’d need to duplicate (and rename) this function into your plugin / your theme’s functions.php to do what you want to do with it.
For instance Blog Tracking is not happening at all across the site – when every setting suggest this should be happenning automatically. It simply isn’t!
Are the blogs, that aren’t appearing, marked as “private” in their admin? i.e. the “Hide from search engines option”.
Tim, regarding your other post, if you don’t provide the information we’ve requested, it’s really, really tricky to know where to start diagnosing the problem.
EDIT: it looks like your reply was marked as spam automatically by the forum. I’ve just unspammed it.
Um, yeah, I’d avoid /trunk for a production site. /branches/1.2 is a safer bet if you want to keep up to date with bug fixes, etc. One of the big things which will be new in 1.2.x or 1.3 (not sure which now), is that the admin menus are to be re-designed, and you can see the first cut of that in trunk at the moment.
It doesn’t call any BP functions (searched for “bp_” in the files) so this is a bit misleading. I’m not aware of any precedent in plugins claiming to be BuddyPress compatible which aren’t, so will be interesting to see what apeatling has to say.
Viewing 25 replies - 4,276 through 4,300 (of 6,157 total)
