BuddyPress.org

i know i’m a bit late on that topic but i do agree that it should almost be a core feature to be able to switch language file.

I’m not talking about having the content translation feature, but the front/back end stuff, basically anything showing on the localization file.

So a user can decide his default language (among the available ones) for the site.

It only makes sense: MU for WordPress MU, for BuddyPress/WordPress MU, for MUlti users, for MUlti blogs and for MUlti language.

I’ve done some research and could not find a black/white solution. it’s seems to be in the grey zone at the moment.

Has anybody been able to achieve this yet?

cheers

Here’s your chance to vote for OpenSocial support in BuddyPress.

Look at page three (Core), item number 5. Learn more about Open Stack here.

Indeed, thanks John!

Remember, BuddyPress is just one, big plugin–a very sophisticated plugin at that. If they have zero experiencing coding WordPress plugins, then here are some key links:

• https://codex.wordpress.org/Writing_a_Plugin
• From the above link, specifically: https://codex.wordpress.org/Plugin_Resources
• https://codex.wordpress.org/WordPress_Coding_Standards
• https://codex.wordpress.org/Inline_Documentation
• http://www.slideshare.net/markjaquith/secure-coding-with-wordpress-barcamp-orlando-2009

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/

Cce-

Several of initial questions:

1. Have you tried switching back to the standard BuddyPress home theme? If not, do so and see if the problem still exists.

2. Have you tried deactivating all 3rd-party plugins to see what happens? If the problem goes away, you should then reactivate the 3rd-party plugins one at a time, testing after each reactivation to see if the problem has returned.

2. Are there any errors in your log files? If so, what are they?

Burt-

Good stuff.

Dbascent94-

Are you still having issues? A week ago you posted this:

I tried using the default themes and the same problem persists. I could really use a pointer on where to even begin looking for a fix for this

But you failed to tell us which version of BuddyPress you are running. Two weeks prior, you stated that:

I downgraded to RC1. I am going to wait for 1.0 and then try again.

Does your problem exist when using the public release version 1.0?

We don’t have sufficient information to beginning helping either of you. Please read this and post accordingly: https://buddypress.org/forums/topic.php?id=2674

Log into WPMU backend as site admin. Go to Appearances > Plugins. The version of all your plugins, including BuddyPress, is displayed there.

Here’s the versioning info you should see with regards to the BuddyPress plugin:

For BP public release version 1.0 –> 1.0

For BP RC2 –> 1.0-RC2

For BP RC1 –> each individual BP component will show up as it’s own plugin.

As of r1303, which is where RC2 started I believe, BuddyPress was turned into one, big plugin suite.

in the bp-core.php if i’m not wrong, at the top of the file the version is displayed another way is wp-admin ->site admin -> buddypress, look at the bottom of the page, it should be displayed

If you’re still having this issue, you need to remove as many variables as possible. Since you are using a custom theme and a number of 3rd-party plugins, this is where you should focus your efforts.

Before starting this process, make a backup of your MySQL DB just in case. Also, it is advisable that you back up all your custom themes and 3rd-party plugin files just in case you make some major mistake.

Now, switch to the standard themes that come with BuddyPress. Try creating a group again. If the problem appears to be resolved, switch back to your custom themes and try creating a group again. If the problem returns, contact the theme designer.

Next, assuming the problem still exists with the standard BuddyPress themes, you should deactivate your 3rd-party plugins one at a time. Deactivate just one, try creating a group again. If the problem still exists, then deactivate another 3rd-party plugin. Keep doing this until either the problem goes away, or all 3rd-party plugins are deactivated. You can also go about this the other way: deactivate all plugins except BP and then reactivate one at a time, checking to see if the issue occurs again with each new reactivation.

If you find that the problem goes away after a particular 3rd-party plugin is deactivated, then you may have found the culprit. Contact the developer of that plugin and ask for advice.

Please report the results back in this thread.

@Scotm, Am interested in that also integrating P2 theme with this twitter plugin.

& tweet from wire!

This is actually a WPMU question, but I think you should find an answer here: https://buddypress.org/forums/topic.php?id=2042

I installed 1.0 from the download link.

Changed the slugs: BP_GROUPS_SLUG, BP_MEMBERS_SLUG, BP_FRIENDS_SLUG, BP_WIRE_SLUG

Applied wire_patch_three.patch

Works for me. I logged in to your site and noticed that this line wasn’t changed which is the problem:

Line 368, in bp-wire/bp-wire-templatetags.php

return apply_filters( 'bp_get_wire_delete_link',

'<a href="' . wp_nonce_url( site_url( $bp->groups->slug . '/' . $uri . '/' .

$bp->wire->slug . '/delete/' . $wire_posts_template->wire_post->id ),

'bp_wire_delete_link' ) . '">[' . __('Delete', 'buddypress') . ']</a>' );

Your install still says ‘wire’ in the delete url instead of ‘pinnwand’. Looks like the patch wasn’t fully installed? This is on: http://sven-lehnert.de/

Change line 368 to be $bp->wire->slug instead of $bp->{$bp->current_component}->slug and it’ll work. See the difference in the two lines here: https://trac.buddypress.org/attachment/ticket/723/wire_patch_three.patch

i like the caching mechanism inclusion, better will be if it will be cached with the built in system wp_cache_set & family

Shakera-

If I understand your issue, you are having problems localizing BuddyPress into Cyrillic.

Please check this BuddyPress codex page first as there is a translation of BP for Bulgarian.

If you are making your own translation, then you should read the Translating WordPress codex page.

Kunal17,

Is there anything else in your “bp-custom” file? Also make sure there are no spaces before and after the opening and closing <?php> tags.

Could you post the entire contents of the “bp-custom” file to http://buddypress.pastebin.com/ so we can look at it?

sounds awesome! will this be integrated into the buddpress status updates that will be incorporated soon?

The core Buddypress files do not live in /mu-plugins/ anymore. They should be in /plugins/ instead. If the location of BuddyPress is hardcoded into the Toksta chat plugin, then that is the problem.

Contact the Toksta chat developers and ask them to update their plugin to the proper path–and not via a hardcoded path.

I’m excited about this, its almost exactly what i was looking for…

I would however really like to see tweet by wire integration (perhaps a small check box that says tweet this)