BuddyPress.org

I just tagged 0.4 final.

Thank you very much to everyone who helped with the testing, translations, and bug reports.

Not much has changed since the beta.

* Changing the component slug is now officially supported

* Do not show my group links or create link form unless user is a group member

As soon as the repo updates you can upgrade from your dashboard. If you have a ton of links, make sure you let the page load all the way after upgrading since every link needs to be updated to populate a new field.

Only two languages are up to date for 0.4. Those would be FR and NL. If you are interested in updating or adding a translation, you can download the .pot file here…

https://plugins.trac.wordpress.org/export/229924/buddypress-links/tags/0.4/languages/buddypress-links.pot

Enjoy the 0.4 branch!

Thank you both for pointing me in the right direction. But I still got some problems.

I tried the language translation files but it only translates a few parts of the actual content inside BuddyPress and not any of the URLs.

So I tried to follow the steps in the Docs. But I seem to be missing a bp-custom.php file. So I added the definable slugs to my wp-config.php file instead. But no change has been made to my URLs.

What could be wrong?

@roydeanjr – Can you be more specific about the error that you get? This plugin doesn’t really affect group creation at all, since groups are essentially created by the end of step 2 (the screen where you check “Create Group Blog”) and the invitations don’t come until the end of the process. Do you have the same problem with group blogs even with Invite Anyone turned off? Exactly what does the error say?

@hnla – The tab nav string is in in the file invite-anyone/by-email.php, function invite_anyone_setup_nav(), around line 199 where it says ‘name’ => __( ‘Send Invites’, ‘buddypress’ ). I’m noticing that I’m inheriting the BP string translation, since the phrase occurs in BuddyPress core. If it would help, I can change that to the bp-invite-anyone domain, so that you could use a language file to apply the change just in that place.

As for hidden groups: I am using bp_has_groups with the user_id of the logged in user to populate that group list. Thus the Invite New Members screen should only show the groups that the user is a member of. It’s possible that you’re seeing all groups because you’re testing with an admin account. Have you verified your hidden group problem with a non-admin account?

@xspringe – we’re glad you like the plugin. And remember, you can help make BP Album+ even better by contributing feature suggestions, translations, and code!

^F^

@coffeeholic

Re: “….Ps. Let me know if you need this translated to Norwegian. i would be happy to help.”

Welcome to the translation team. We will contact you when the next “stable” is ready to release.

^F^

my .po file does not contain the letters ‘æ’ ‘ø’ and ‘Ã¥’ which are the special danish letters. Those I have translated to for instance ‘æ’ etc.

I have not edited any php files. Only the .po – which is why I am very confused as to why it should cause me trouble.

The example picture which I link to above – the .po looks like this:

#: bp-themes/bp-default/groups/groups-loop.php:57

msgid “There were no groups found.”

msgstr “Der blev ikke fundet nogle grupper.”

#: bp-themes/bp-default/groups/index.php:17

#, php-format

msgid “All Groups (%s)”

msgstr “Alle Grupper (%s)”

Hmmm?

Sorry I missed this. I’ll review that and see if I can contribute any meaningful new pointers to the codex .

I guess I should have started here:

https://buddypress.org/forums/tags/translation

OK, so I found buddypress.pot – can anyone explain how to work with .pot files? Can I just edit this and the changes will magically appear in my theme?

@Mariusooms

This can be added, we will try to include it in next release (before that we’re waiting for some more feedback).

I guess best would be to check if user is coming from some outside URL, if so – to redirect him to preferred language, otherwise let him switch languages as usual.

@Sanny

Thanks for valuable feedback.

BP is not wrapping extra profile fields (title and description) in textdomain – you can’t get it translated (for now). We will try to add support for this – to register extra field’s titles and labels (descriptions), so it can be translated via WPML’s ‘string translation’.

Hi 3sixty

Yes I would need help for the translations as I speak french and my english is not always perfect.

So the prioty things to do are

-Better instructions & translation

-Make ajaxed functions work

-Finishing adapting it for WP3.0 (custom types) – I started this but it isn’t working perfectly yet

-Better layouts, yes.

I made a post here that you can complete : http://dev.benoitgreant.be/bbpress/topic/future-versions-things-to-do-in-priority

@Bowe

1: yes

2: Are you referring to subblogs? BPML since 1.0.0 version is only active on main blog.

3: That is one of features left for future development. Personally, I don’t like auto detecting of languages.

4: WPML has ‘string translation’ API. Theme and plugin strings can be registered there and translated (WPML can scan theme for strings and allows you to translate them directly via WP.

@Mariusooms (Hi Mariusooms!)

That is good point. So you’re suggesting that in BP user’s option should be ‘default language’ setting?

I haven’t thought about this, but I guess there is some workout needed if user actually needs some language switching. And I also think that this can’t be done without using cookies (no matter how much I would like to avoid it).

@Erich73 (Hi Erich!)

I hope you can reach site. (it was down for a short while when I was switching it to new WPMU+BP)

i just saw it now it’s doing the same on the forum! it was supposed to be a word with accent! not those characters