BuddyPress.org

Ya, John’s right. That’s the symptoms of just putting bpmember in /wp-content instead of /wp-content/bp-themes/bpmember during an upgrade. You then have to vist BuddyPress > General Settings and say Save.

It’s due to the directory ‘bug’ in wpmu 2.7.1.

No, you only need one installation of WPMU/BuddyPress to have a multi-language website.

When you install additional PO’s and MO’s in your wp-includes\languages folder, magically in your Site Admin and Blog Admin settings will be language selection options, to determine the default language of both the site and the blog. The mu_locale function will take control of it and over-ride the WPLANG settings as necessary.

There is no user language settings as of yet, but I’m working on an implementation of qTranslate to allow for this. This won’t work until BuddyPress 1.0.1 as there’s a few specific things that need to be altered for everything to work in the order they need to.

Good job Burt!

Do you have a theme named “bpmember” in your wp-contents\bp-themes\ directory?

If so, have you navigated to your BuddyPress settings and activated that theme as your members theme?

Right now the slug changing isn’t working 100% correctly. A bug-fixed, security swept, attribute_escaped BuddyPress 1.0.1 is on the assembly line as we speak.

Check which plugins are activated on that specific blog and turn them off one by one. Sounds like something is interfering with something else. More than likely some kind of date re-writing or hi-jacking situation.

bp-core.php Line 912

Otherwise, there’s only a few places this function gets calls inside BuddyPress, so it would take some tracing back of those functions to see what’s conflicting or what’s causing it to happen.

\buddypress\bp-core.php (5 hits)

Line 275: return apply_filters( 'bp_activity_insert_time_since', @sprintf( $content, @sprintf( __( '  %s ago', 'buddypress' ), bp_core_time_since( strtotime( $date ) ) ) ) );

Line 896: function bp_core_time_since( $older_date, $newer_date = false ) {

Line 998: $last_active = bp_core_time_since( strtotime( $last_activity_date ) );

Line 1000: $last_active = bp_core_time_since( $last_activity_date );

\buddypress\bp-friends\bp-friends-templatetags.php (1 hits)

Line 251: return apply_filters( 'bp_friend_time_since_requested', sprintf( __( 'requested %s ago', 'buddypress' ), bp_core_time_since( strtotime( $friends_template->friendship->date_created ) ) ) );

\buddypress\bp-groups\bp-groups-templatetags.php (2 hits)

Line 752: return apply_filters( 'bp_get_group_last_active', bp_core_time_since( $last_active ) );

Line 2346: echo apply_filters( 'bp_group_request_time_since_requested', sprintf( __( 'requested %s ago', 'buddypress' ), bp_core_time_since( strtotime( $requests_template->request->date_modified ) ) ) );

\buddypress\bp-xprofile\bp-xprofile-templatetags.php (1 hits)

Line 368: return apply_filters( 'bp_get_profile_last_updated', sprintf( __('Profile updated %s ago', 'buddypress'), bp_core_time_since( strtotime( $last_updated ) ) ) );

So far from what I can see of the second release candidate of bbPress 1.0, it looks like integration has gotten better for BuddyPress and WordPress MU, but don’t expect a simple turn-key installation. There are simply too many configurations to not have to dip into the wp-config.php or bb-config.php files a little bit.

Integration of bbPress1.0 RC2 is essentially the same as the Alpha’s, other than there being a spot to enter the ID of the main WPMU blog. There’s also an extra variable to add to the config files to force the integration method, but I suspect that to be only temporary.

Once everything becomes 1.0, things will probably make more sense and come more into alignment.

You can edit the tags from viewing the post itself. Anyone can add or remove tags at any point.

If you’re talking about the link on the front page to take you to the BuddyPress Trac, that should be working just fine. Where is this link that’s 404’ing?

Hi Erwin Gerrits,

bp-events is great. I’m playing around with it, having a lot of fun!

Now I have one problem with the wire.

May you can help me to fix it. I use customizable slugs, and I think this breaks the wire in your plugin.

This ticket has a batch for buddypress.

https://trac.buddypress.org/ticket/723

do I need 2 installations of BuddyPress in order to run a website in 2 languages ?

Please let me know.

Many thanks,

Erich

oci-contents.php line 292 there is var_dump() call that is causing the problems above.

Rebootnow-

Since I had only one radio button field, which was located in my first field group, I did the following:

• I added a new radio button field to my second field group and tested. No issue.
• Then, thinking it could be an issue if two or more radio button field sets were in the same field group, I added a second radio button field set to the same group. No issue between all three radio button field sets.
• Then I created a new field group and added a fourth radio button field set. No issue. Each change I made showed up and remained properly set, whether just changing a single radio button field, or changing all four radio button fields.
• Finally, thinking maybe this could be an issue only within the first field group, I added a second radio button field to the first field group. I now had 5 radio button field sets. No issue. All five worked as expected. No issues within filed groups or between field groups.
• Since the first radio button field set in the first field group was set to “Required”, I reset it to “Not Required” to see if that would make a difference. No issue.
• I then set both radio button field sets in the first field group to “Required”. No issue.

So, I have tried numerous combinations and cannot recreate your problem.

A few questions:

1. Do you have any plugins other than BuddyPress installed and activated? If so, try disabling .
2. Are you using the standard BuddyPress themes or customized themes? If customized themes, try switching to the default BP themes.
3. Are there any errors in your server’s log files?

Received this error when posting a new tag to a group as admin:

<br />

string(60) "http://modestobuzz.com/groups/modesto-area-disk-golfers/edit"<br />

Warning: Cannot modify header information - headers already sent by (output started at /home/chedstone/webapps/modbuzz/wp-content/plugins/oci-contents/oci-contents.php:292) in /home/chedstone/webapps/modbuzz/wp-includes/pluggable.php on line 856<br />

Blank page with the above text on it. The tag was still added though.

Running BP 1.0 and WPMU 2.7.1

@DJPaul:

I’m not getting any error. Just a blank screen. Very frustrating…

Pinggu-

Starting a new support request within a thread marked resolved will not get you anywhere. It will be ignored. Please read this thread: https://buddypress.org/forums/topic.php?id=2543

Subster-

First, you should not edit the core files–this includes the widget files. Instead, make copies of the widget files that you want to modify, give them a unique name, and then work on those copies. You can then install and activate your new widget in WPMU’s backend like any other widget.

Second, before modifying any widget, you should remove it from any BuddyPress theme column in which it is installed. This is just a wise precaution.

Third, I’d suggest copying back to their original locations, unaltered versions of the widget files that you modified.

Making a backup copy of your DB is always a good idea before any modification that can impact the data. But, as far as what you’ve done with your actual data in you DB, I cannot advise.

These two error messages indicate that you do not have a a complete install of the standard member theme.

You state that you are using the standard BuddyPress themes and it seems like you are able to access the member theme to get to the links to change the avatars, but the files to alow you to do so are missing.

For the change-avatar.php file, look in /wp-contents/bp-themes/bpmember/profile.

For the group-avatar.php file, look in /wp-contents/bp-themes/bpmember/groups/admin.

If you do not see either of the files in those locations, then your installation is flawed. Reinstall the member theme, reselect it in WPMU admin, and try again.