1. Which version of WPMU are you running? 2.8.6
2. Did you install WPMU as a directory or subdomain install? directory
3. If a directory install, is it in root or in a subdirectory? subdirectory
4. Did you upgraded from a previous version of WPMU? If so, from which version? Maybe 
5. Was WPMU functioning properly before installing/upgrading BuddyPress? I Assume so
6. Which version of BuddyPress (BP) are you running? latest
7. Did you upgraded from a previous version of BP? If so, from which version? yes, the previous one
8. Do you have any plugins other than BuddyPress installed and activated? nope
9. Are you using the standard BuddyPress themes or customized themes? standard
10. Have you modified the core files in any way? I have installed the italian translation
11. Do you have any custom functions in bp-custom.php? $bb->bb_xmlrpc_allow_user_switching = true; Is it still needed? Plus italian translation
12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in? built-in
1. Rename slugs by defining global constants in /wp-config.php. Eg:
define ( 'BP_GROUPS_SLUG', 'clubs' );
2. Page titles are generated by bp_page_title(), which is defined in bp-core/bp-core-templatetags.php. It looks to me like they are properly localized, though. Maybe there’s a missing translation in the .po/.mo files? What language are you using?
Found the translation bug.
In bp-events.php, line 2831
add_action ( 'plugins_loaded', 'events_load_textdomain', 9 );
should be
add_action ( 'plugins_loaded', 'events_load_textdomain', 1 );
As it was in 9 priority, it was loaded after
add_action( 'plugins_loaded', 'events_setup_globals', 5 );
That’s why the other strings loaded but not this one.
Merci nexia 
c’est sympa !
Of course i can translate directly in the plugin, but i don’t want to do that…
This said, the plugin needs effectively to be rewriten at his locale level. The function who actually do this is a bit…hum… complicated and .. haaaaaaa….weird. (je reste poli tu vois)
gettext is ok, some of the people who use it not so much (or as well)
WPMU 2.8.6 -> and in june WP 3.0
WP 2.9.1 / 3.0 alpha -> and in june WP 3.0
BP 1.2 -> and in june 1.3 ?
There are so many things to update in the next 6 mounth… yeap !
Meanwhile if somebody could clean the WP plugin repository from the very old/obsoletes stuff it contains it would be great too.
hum, tu peux pas ajouter directement la traduction?… des fois je me demande pourquoi ils utilisent cette technique pour les traductions alors qu’il n’existe aucun logiciel VRAIMENT fiable pour gérer le tout… c’est un enfer.
par ailleurs, il y a plusieurs trucs à mettre à jour puisque WPMU est à 2.9, BP est à 1.2… woo tooooo
Nobody use this plugin in another language as english ?
ARGH, forget it… the last trunk corrected it… strangely, there was no “My Blogs” menu in the adminbar…
and the translation is wrong also… looks like i will have to write down a real French international language file… nobody is ever able to read/translate properly… rofl *(Only the creation of an user account is permitted)
i’ll have to check further more to see if it was just a glitch…
By the way, Dan (Chouf1) has added I18N translation functionality to the plug-in so that will be a part of the next version as well.
Nothing like literal translation, love it. I think I get the jist of it.
You mean that my office smells of machine translation, it is true. I have been following this plugin and have always wished that he had worked on a simple wordpress, but the Internet was not the solution, and wordpress mu I do not like, and I think the engine for social networking little weak (but this is only my personal opinion) , but the plugin itself buddypress can work wonders, but only for a simple wordpress. Of course we are not standing still and slightly altered this plug-in, hard to write him a simple wordpress, but some errors were, and blogs all set up on a different principle. truth will automatically create them failed, but still worked, did not work for some reason, some functions of the transfer of messages between users and groups, and something else. And when I heard that Andrew has decided that the problem of course, turned here, as at present a couple of projects are not ready, just because of the absence of such plagina.Etot plugin will be needed not only to me but I’m sure many other users. I have already raised this issue at one of the forums and site for translators buddypress into Russian Vyacheslav, and very glad that the problem is finally solved
I sense the presence of machine translation.
looking forward to run BP in 2 languages. Do not need the language-translation on the fly (like Google Wave) though…..
How to work with both customized and translation .mo files?
1. I’ve uplaoded an id_ID translation (mo) file and using the multilingual plugin, it’s works.
2. I’ve made a bp-custom.php to change ‘wire’ slug into ‘memo’. It’s working on my translation pages, but not with the default english contents (‘memo’ URL’s are fine, but not with menus and ‘wire’ related texts).
<?php
define( 'BP_WIRE_SLUG', 'memo' );
?>
3. I’ve made a customized PO file (english) to fix this and load the MO language file with bp-custom.php. Now the english language is working (URL’s and contents), but those changes made some of my id_ID translation turns back into english (some ‘memo’ related translation) but the rest translation is fine…
<?php
define( 'BP_WIRE_SLUG', 'memo' );
define( 'BPLANG', 'memomu' );
if ( file_exists( BP_PLUGIN_DIR . '/bp-languages/buddypress-' . BPLANG . '.mo' ) ) {
load_textdomain( 'buddypress', BP_PLUGIN_DIR . '/bp-languages/buddypress-' . BPLANG . '.mo' );
}
?>
Did i made any mistake with those steps?
Is it allright using both customized and translation .mo files?
please help, thanks!
I’ve got a plugin that will do this in some places. Search the WP plugin repo for “BP Translate” and you’ll find it in there. I’m actually working on an update to it now, but give it a download on a test environment and see if it does what you want it to.
Achievements coming out this weekend. Just going to see if I can get some translations done first. Mainly a compatibility release with current BuddyPress and a few changes to admin interface. Plan is to get another version out just after BP 1.2 with more changes.
ALT tags and title tags of the images that appear on the home page and sub pages of buddypress sites should be taken into to consideration for an SEO plugin, or future core development. Currently my BP site rank far below other sites when you google for the actual dot com, which is also in the title in big letters with the new default bp theme. Unfortuanelty google sees a majority of my site as
“home” and “group avatar”
there should be a way to change / add title and alt tag to the large site title, and the small title in admin bar. I would also experiment with appending the site tite to some of hte other images.. it would be better for me to have:
my-dot-com-home
my-dot-com-group avatar
my-dot-com-groups
my-dot-com-blogs
etc
right now if type in my dot com into google, another site shows number one result, and that site is completely blank – just an empty dot com folder – that’s my first clue that bpress seo is in need of help –
Svenl77 – even with poor english translation – you are very right about all of that – you have certainly done your seo homework!
I know some of the issue is the text content showing in recent sitewide posts is not helping, but pretty much everything else on the page is gravatar images and others that are not helping the front page to rank for it’s keywords – I could take groups and recent active members off the front page and see the effects.
I would love to know where in the theme or code it is controlling the “home” as title of my site title, and group avatar, and blogs, etc – To those alt and title tags are the second biggest seo mistake with buddypress right now –
I don’t think it is a problem with volunteers. Automattic could just pay people to do the work, or hold an account with a translation company. It is not as though it is a huge piece of work to upkeep. Look e.g. how Mediawiki or PHPBB handles it. It only account for 10s of kb.
(Actually, in my case, Automattic has recently hired bi-lingual Japanese staff and I will be interested to see how they are used).
The problem of language files seems to be a problem that needs addressed at the core of WP, centralized, made much easier to handle and more effective.
Now that Buddypress is part of the stable, I am hoping it is also developed as an international device. I am glad to read that there is awareness of this on the development side ….
what responses about it do you get back from the main developers?
If you’re using a standard installation afaik you don’t have to do anything with the bbpress file. Have a look at the translations page on this website (under Codex) and see what other people have done.
5402929Inactive
Looking forward to help on the language’s. I’ve got buddypress translated to dutch and that works fine. After that I activated bbpress but cannot figure out where the language files for bbpress go ?
bb-config says: * bbPress Localized Language, defaults to English.
*
* Change this to localize bbPress. A corresponding MO file for the chosen
* language must be installed to a directory called “my-languages” in the root
* directory of bbPress. For example, install de.mo to “my-languages” and set
* BB_LANG to ‘de’ to enable German language support.
*/
define( ‘BB_LANG’, ‘nl_NL’ );
Where is the root directory of bbPress when one installed it with the one-click install from within buddypress ? e.g. where does the .mo file go ?
Got it working, hacked bp-core.php and made it a static link (to the .mo file).
In continuation of this, I ran into a fatal error on the buddypress settings page in the admin area.
Fatal error: Call to undefined function bp_core_get_buddypress_themes() in /customers/xevodesign.nl/xevodesign.nl/httpd.www/talkmore/wp-content/plugins/buddypress/bp-core/bp-core-admin.php on line 105
Edit: Nevermind, using “define ( ‘BP_IGNORE_DEPRECATED’, true );” in your wp-config isn’t allowed apparently..
Check your messages, I figured it out.. but it wasn’t easy… I think we should write a new tutorial of how to translate for BP because information about this is quite hard to find and not well documented.. I’ll try to write a quick tutorial for this soon
Just tagged version 0.1.3
* Fixed bug where Comments was not showing up in link list nav bar
* Many l10n fixes, big props to Chouf1
* Added support to control voting behavior with config constants and filters
* Added Spanish translations, props to laloma
* Improved Fotoglif support due to changes to their API
need help to support these, DJPaul ?!… i’m available… and i will provide a translation in the next days for french language too… would be good if you provide a .pot … thanks!
