BuddyPress.org

1. BP trunk already supports 2.9.1, and 1.2 will as well.

2. BP trunk works very well on WordPress 2.9.1 (not MU)

3. Don’t expect WP3.0 until at least June, if not later. The WordPress dev cycle is aiming for new versions every six months.

r-a-y’s been paying attention.

I would recommend staying away from the trunk version of WordPress (single) at the moment. The WPMU trunk currently contains the most up to date WPMU 2.9.1 version, it just hasn’t been officially released yet.

The easiest way would be to create a WordPress page with the slug “subblogs”, applying a page template with the code you listed above.

Tutorial on creating WordPress page templates (if you need it):

https://codex.wordpress.org/Pages#Creating_Your_Own_Page_Templates

I’m almost certain that the problem has to do with items being tagged with timestamps from the future. The function bp_core_time_since() in bp-core.php returns the message [Use GMT Timezone] when the timestamp on an item is greater than the value returned by the core PHP function time().

The timestamp for blog comment and for blog entrie activity comes from the timestamp attached to those items in the databases corresponding to the individual blogs. That means that the timestamps on blog entries in at least some wp_x_posts and wp_x_comments blogs are incorrect by at least a few hours. I don’t know how this would happen. You can set timezones on a blog-by-blog basis, but I assume that WP ignores timezone settings when stamping new entries and looks only at GMT unix time.

I’m not sure what to recommend. Go into the database and look at the timestamps on some of those rogue comments and entries. Verify that they are indeed incorrect. If they are, then you’re looking at a WordPress problem. Try making sure that those blogs are set to the correct time zone (Dashboard > General, I think) and see if the problem persists.

You can’t; this is a result of the blog IDs being set by an auto-increment primary key integer in the MySQL database. You could do something like export the database, drop the table (wp_sites, or something), create the table again and re-import your data.

However I am not sure of the consequence on WordPress of this being done so not recommended unless you have time to check all the tables and update references where needed.

@wordpressfan Are you looking for an events plugin thad adds not only events and a calendar but lets people rsvp and “attend” events? If so, You can use Erwin’s http://www.erwingerrits.com/?page_id=799 or head on over to the wpmu.org crew and throw down money for theirs (not an endorsement since the make you pay without even a test drive, not my game)

I got exactly the same problem, it doesn’t matter whether it’s set up with sub domains or directories, it still won’t work

My install is wordpress mu 2.8.6 with buddypress 1.1.3

Everything worked fine before I added buddypress, as far as I know of.

I didn’t upgrade from previous versions, it was a complete fresh install

I haven’t activated any other plugins or themes or changed any core files

All links apart from the Home link is reporting 404 error

My host is names.co.uk

No problem with your post, I just don’t think anyone has gotten around to answer yet

I think this capability is something important that is missing in bp groups. The concept of group and its integration with bbpress are certainly expanding the users interaction within bp groups; yet the privacy of groups discussion is not assured.

Firstly, is there a quick fix to autohide all bp groups forum from bbpress forum? I have not enabled group forum support because of this issue; and currently only using a separate install of bbpress integrated with wordpress as a place for general forum discussion. Hiding the whole forum is certainly not a totally acceptable solution especially when there are thousands of existing topics that are already there and not associated with any groups.

Secondly, what is the code to check if the logged user is a member of a group with forum id that can be done from bbpress with deep integration; this could be added in bbpress to limit access to group topics where the logged in user is not a member.

rgds

I also use the email login plugin, but generate a username from the fullname using Javascript (link is for blogname from blog title, but the principle is the same). I think that’s a cleaner solution that avoids a lot of the issues you ran into.

As for your other question, here are a few places to start:

1) Make a Gender field and a Enter the Competition field in Dashboard > BuddyPress > Profile Fields. Make sure they’re required on registration.

2) If by “top nav menu” you mean the thing that floats across the top of the screen, you can add to it by creating a button inside of a php function, then using add_action to attach the function to the bp_adminbar_menus hook. See buddypress/bp-core/bp-core-adminbar.php to see how it works in the core code.

3) Use a plugin like JJJ’s https://wordpress.org/extend/plugins/bp-member-filter/ to create the filters that will populate the pages that the “Men” and “Women” dropdowns will point to.

https://wordpress.org/extend/plugins/bp-member-filter/

The first way is for users that may have been registered before BuddyPress was installed. They can still login, post comments, and use the forums, but if they never edited their profile and set their display name(fullname), BuddyPress won’t find them.

The second is if a user edits their profile from the WordPress side (firstname, lastname, nickname) without changing their BuddyPress display name. At that point the two will be out of sync.

It’s possible to hook into the save profile action of WordPress and change the BuddyPress display name when the user changes their WordPress nickname, but some sites may want a combo of the firstname/lastname while others may want to use the nickname, and others still may not really even care or use either. From that perspective it makes sense to not have BuddyPress try to interfere too deeply with syncing profile fields that might not have a direct 1 to 1 relationship with each other.

Please, don’t cram BP full of this type of features! Leave them to third parties; basic free plugins, sophisticated paid plugins, external apps with a plugin interface, etc.

There are already so many WordPress plugins available. Why not start with adapting and extending those, instead of reinventing the wheel within BP.

Please core developers, concentrate on the core! Make sure it’s clean, solid and secure. Concentrate on APIs that make it easier for third parties to hook into BP.

Photo albums may be core to some, but not for everybody. I can think of dozens of other applications that could be core to someone; event management, mailing lists, groupware, file sharing, paid membership levels, video galleries, group video editing, chat rooms, video conferencing, shopping cart, credit card payment bridge, mobile apps, geolocation … etc.

https://wordpress.org/extend/plugins/buddypress/download/

First is a WordPress thing, latter is BuddyPress.

For the first, check out some of the suggestions at the bottom of the https://codex.wordpress.org/Nofollow page

http://www.interconnectit.com/719/migrating-a-wordpresswpmubuddypress-website/

Good luck

This is great, thanks for spreading the word about mojofiti, anyone wanting to know more, work with us, get our code, or collaborate in any way, please reach out.

haloid – I wrote a plugin for group invitations that uses the same autocomplete code as the messaging system to allow group mods to invite any member to a group: https://wordpress.org/extend/plugins/invite-anyone/. So it’s definitely possible to extend BP to do what you’re asking. I haven’t looked at the code for messaging, but if it’s anything like the invite code, it’d be pretty easy to do. A quick glance at bp-messages.php makes it look like you could probably alter BP to do what you want it to do by finding the function messages_ajax_autocomplete_results in bp-messages.php, commenting out the code that populates $friends, and replacing it with a list of all site members (you could use exactly the code I use in the Invite Anyone plugin).

Better still would be to build it into a plugin. Wouldn’t be too hard. If I get a chance in the next few weeks, I might take a look at it.