BuddyPress.org

@rickdickinson that first codex page clearly states it’s in regard of the older bp-default setup, this doesn’t mean don’t follow it but you would only do so if you were already working with that themeing approach.

the second link is the one to follow for new install/themes, yes you do need to create a child theme IF you’re working with an existing of the peg theme, if you’re writing your own then you simply overload your files in either /buddypress/css/ or /community/css/ (either labelling works and both folder structures are applicable whether a main theme or child one)

If you overloaded the entire buddypress.css file and your changes didn’t work it’s just possible you hit the 2.1 issue of naming convention, which will be fixed in 2.1.1, so try renaming your file to buddypress.min.css.

Yes you can!

A better question would have been to explain what you are ‘hacking’ and why and how best to achieve this.

buddypress-functions.php is not necessarily a straightforward functions file, if you overload it you then have to be responsible for ensuring any core changes are copied over, or perhaps you just need to extend the theme compat class rather than hack buddypress-functions with your own class?

I was having a similar issue. I had html being displayed at the top of some of my buddypress pages. I finally found the culprit to be this bit of code I was using in the <head> section of my site —>
<meta name=”twitter:title” content=”<?php the_title(); ?>”>

Changing it to the following fixed my problem —>
<meta name=”twitter:title” content=”some static text here instead”>

Now I just need to figure out how to make it work with the PHP code without generating random HTML at the top of my page.

Hope it helps.

It’s actually the Site Tracking in conjunction with Activity Stream which allows for post publishing to be tracked.

I don’t know exactly what you’re trying to do here, but you could first start by increasing the excerpt length to be a little longer. I’m not sure what the default excerpt length is for BuddyPress, however the function below will increase it to 750 characters.

Place the function below into functions.php or bp-custom.php

function px_bp_activity_excerpt_length() {
    return 750;
}
add_filter('bp_activity_excerpt_length', 'px_bp_activity_excerpt_length');

Hi @namrons

This will most likely need a Trac ticket. Feel free to create one here:

https://buddypress.trac.wordpress.org/

i believe that wp_icl_strings is related to a multilingual plugin, like wpml or buddypress-multilingual.

Deactivate it and see what happen.

Comment in bp-messages-loader.php

/**
 * Implementation of BP_Component for the Messages component.
 *
 * @since BuddyPress (1.5.0)
 */
class BP_Messages_Component extends BP_Component {
	/**
	 * If this is true, the Message autocomplete will return friends only, unless
	 * this is set to false, in which any matching users will be returned.
	 *
	 * @since BuddyPress (1.5)
	 * @var bool
	 */
	public $autocomplete_all;

So yes it is implemented since BP 1.5

By default you get only suggestion of your friends names. You can get all user names, by adding this to your bp-cutom.php file

define( 'BP_MESSAGES_AUTOCOMPLETE_ALL', true );

But never use this constant if you have hundreds of user ! (imagine the length of such a list !)

Hum… have you activated pretty permalinks ? This is made by chosing one of the permalink option, except default, in the WP permalink settings.

Does your host allow multisite ?
Have you added the htaccess code after network activation ?

See also this related topic.

Yes it is weird ! And it is not a buddypress issue but a translation issue.

The glotpress po file is uncomplete and contains many errors.
Not sure if it can have an influence on the automatted language upload, but the header is missing the language parameter. (@r-a-y, @boone)

I first tested it “as is” and got same errors as you.
I applied patch #5887… nothing
I used the function mentionned by @r-a-y… nothing
I added the mo into suggested /wp-content/languages/plugins/buddypress/bp-languages/buddypress-es_ES.mo… nothing

So i went back to my original config and used the same settings i usually use for my fr_FR BP version (/wp-content/languages/plugins/buddypress-es_ES.mo)… nothing !

WTF ? 👿 #grumbl…@?/;rrrrr !

So i decided to make a new po by updating the one found on glotpress. (i’m working with poEdit)
This resulted in around 1300 (a little more) new lines and over 100 deprecated lines… and a lot of approximative strings….

In these approx, i found groups, activity and all other strings you mentionned not getting translated. I simply reverted them to valid and bam, the translation worked.

I suggest the following:

• revert back to standard config (no language patch, no language custom functions, no extra language folder) and po/mo in wp-content/languages/buddypress-xx_XX.mo
• download the po from glotpress
• open the file with a text editor and remove the header and replace it with this one:

msgid ""
msgstr ""
"Project-Id-Version: BuddyPress 2.1\n"
"POT-Creation-Date: 2014-09-26 13:34+0100\n"
"PO-Revision-Date: 2014-09-26 14:19+0100\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: es_ES\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;"
"esc_attr__;esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
"X-Textdomain-Support: yes\n"
"X-Poedit-Basepath: .\n"
"X-Generator: Poedit 1.5.7\n"
"X-Poedit-SearchPath-0: ..\n"

• create a folder in BP called bp-languages-ES (or whatever)
• add the po to this folder
• open the file with poEdit
• update the catalog from source

Now you can see all untranslated lines, the one who are approximative and the one who are already translated.

At this stage, the file is translated to 53% and you’ll have to translate around 770 strings (of 2668).

You also have to check each string containing count variables like %s or %1$s (many are old and must be modified). You’ll find also some plural strings. This is particulary true for approximative strings, who may be similar to the english phrase, but aren’t. Needs good eyes and slow checking ! 😉

Once finished, save your work and copy the mo file into the appropriate language folder:

/wp-content/languages/plugins/buddypress-es_ES.mo (if you want to use your custom translation only)
/wp-content/languages/buddypress-es_ES.mo – if you want automagical 👿 glotpress updates (when avaible, complete and without errors of course).

I’m not sure which membership plugins work well with BP as I’ve not used any but I’m sure some of the guys on here will be able to recommend?

As @r-a-y points out in this thread, is_buddypress() is a good catch all for BuddyPress pages. So, you could put something like this in your theme’s functions.php file:

function my_function() {
    if ( is_buddyPress() ) {
        // This is a BuddyPress page you are viewing so do something BuddyPressy.
    } else {
        // This is not a BP page.
    }
}
add_action( 'init', 'my_function' );