BuddyPress.org

please read the documentation !

BuddyPress Codex

If you can’t find who it is @markhahnel, ask on http://lists.automattic.com/mailman/listinfo/wp-polyglots

@Frosty8o It sounds like you have a problem specific to your install, I can upload and crop without issue on a Modded 1.2.6 / 3.0.1 and with quite a few plugins running.

As Paul has asked check that there are no JS errors reported.

Also clarify “avatar upload works” you can upload an image and see it sitting there on screen awaiting cropping and/or saving?

Always check the the docs/codex to see if there are any guides that cover a question:
https://codex.buddypress.org/extending-buddypress/building-a-buddypress-child-theme/

To link your logo to homepage open up a header file bp-default or a wp default header file and have a look at the markup where the logo is set, although isn’t the logo already linked if you’re using the default theme?

For such common questions, please read first here:
https://codex.buddypress.org/home/

For the logo URL, take a look in bp-default/header.php

I don’t know much but I think one nice option would be to comment out or remove the Blog creation details section from the register.php file of your theme.

register.php file residence : yourtheme/registration/register.php

blog creation details section on register.php would be approx : from line no. 169 to line no. 201

or simply comment out line no. 173
or the line with

<?php _e( 'Blog Details', 'buddypress' ) ……

and line no. 175
or the line with

<input type="checkbox" name="signup_with_blog" i …………………….

This may solve your issue with keeping the blog registration open but stopping new people from registering it from the register page of your site.

@nonegiven Please keep your criticism constructive.

Just an updated. After upgrading Buddypress to 1.2.6 all my site-wide things started working again. Thanks for fixing this!

True, but sadly it is as Rich states; so I thought I’d throw a little humor into the fray

There are improvements to the site planned, you can follow them in the ninjas group.

I think the best solution is to have two separate .mo files with the interface translation and set the translation on wp-content/plugins/bp-custom.php (If you havent the file, create one) with the following code
$lang = substr($_SERVER, 0, 2);
switch ($lang){
case ‘en’:
define( ‘BPLANG’, ‘en’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ );
}
break;
case ‘es’:
define( ‘BPLANG’, ‘es’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ );
}
break;
}
Check that the filenames are the same

This code detects automatically the browser language and defines the language.

Follow this article to find more about this
https://codex.buddypress.org/buddypress-site-administration/customizing-labels-messages-and-urls/

24 tabs always open in opera and 17 in FF but I am chocked full of that RUM stuff 8 gils worth

i believe it is something they are trying to work on/fix https://buddypress.org/community/groups/buddypress-org-ninjas/

You are probably best to find a suitable WordPress theme, and then use the BP template pack to make it compatible with BuddyPress.

Have a Google for WordPress Magazine themes

@r-a-y :

p.s. I do agree with you on a number of things here –

yes: new features as theme options (opt-ins, not outs), and yes: it’s probably part of a wider jigsaw – a well developed Codex would have helped, as would a much clearer / better signposted buddypress.org (invitations to test 1.2. and how to, were only obvious to a knowledgable few – which may explain the small uptake).

@r-a-y – sure, we can get rid of them with some additional work on sites in development, but what about the installed sites – who’s going to schedule, manage and pay for their modifications?

As you know, BuddyPress has real world 3rd party implementations – it’s not just in the realm of coders, who only maintain and support their own site.

If the client hits the upgrade button (which the admin system will be encouraging them to do), they will be left with a site that doesn’t look like they want (and in some cases, will have multiple buttons and areas that simply don’t work anymore).

Surely, the whole point about a child theme is the exact opposite – it’s not expecting things to change – it’s expecting the parent to stay working as expected when the core is upgraded – to provide us with a safe consistent level of abstraction.

The client has paid for a site they want, designed the way they want – not to have it change on the arbitrary design whims of a 3rd party they’ve never met.

What will happen when WordPress bring out a new design for their default theme? Will they overwrite 2010 and thereby change the look / behaviour of every child based on it? Of course not, they will they introduce it as a new theme, and 2010 will happily continue to function.

Template Pack needs to be updated… I’m not sure who’s in charge of that plugin as of right now.

Ping @djpaul!

The whole point of having a child theme is inheriting all the cool, new features of the parent theme; I think we shouldn’t be making comments after the fact BP 1.2.6 was released. The core team asked many times for testers to the 1.2 branch; some did test, but many did not.

Like it’s been stated, secondary avatars can be removed by getting rid of the filter. I do agree that blog avatars shouldn’t be used since you can’t even declare a blog avatar yet. However, you can get rid of that quite easily by duplicating the secondary avatar function and removing the “blogs” case.

The following code will work in your theme’s functions.php:

`function ray_secondary_avatar_fix() {
remove_filter( ‘bp_get_activity_action_pre_meta’, ‘bp_dtheme_activity_secondary_avatars’, 10, 2 );

// add the following if you still want secondary avatars, but omitting the blog one
function my_bp_dtheme_activity_secondary_avatars( $action, $activity ) {
switch ( $activity->component ) {
case ‘groups’ :
case ‘friends’ :
// Only insert avatar if one exists
if ( $secondary_avatar = bp_get_activity_secondary_avatar() ) {
$reverse_content = strrev( $action );
$position = strpos( $reverse_content, ‘a<' );
$action = substr_replace( $action, $secondary_avatar, -$position – 2, 0 );
}
break;
}

return $action;
}
add_filter( ‘bp_get_activity_action_pre_meta’, ‘my_bp_dtheme_activity_secondary_avatars’, 10, 2 );
}
add_action( ‘init’, ‘ray_secondary_avatar_fix’, 9 );`

I do agree that there should be a better changelog for changes made to bp-default. Maybe in the codex?
[ EDIT: changelog created here – https://codex.buddypress.org/extending-buddypress/bp-default-theme-changelog/ ]

@paulhastings0 @paulhastings0 @paulhastings0

Test please, you dragged this up