BuddyPress.org

how about a plugin that would allow a user to join group(s) when they signup for their account, rather than after.. Ideally the group selection being an Admin Sponsored Group. That way zillions of groups aren’t shown in the selection list.

Admin Sponsored Groups.

PHP Developer

Buddypress Developer

User createdGroups

PHP California Developers

Blah, blah

Brian

Sorry, I’m done.

I just forgot to upload it. Will do asap.

Ok, uploaded to my server. Codex page here: https://codex.buddypress.org/translations/swedish-svenska-sv_se/

Let me know if there are any errors. I’m sure I missed something.

Unfortunately not, at least right now.

What I consider the main reason for this, among the others, is that WPMU has a specific plugin directory devoted to “instant on” plugins, and BuddyPress relies on that specific ability within WPMU to activate itself and to load up all of the necessary files and functions.

You could, however, install WPMU and BuddyPress together, but then turn off the ability for users to make their own blogs. This will essentially make it operate like a WordPress.org install on the outside, with MU/BP’s sweet creamy insides.

Indeed, you should be reporting it to the plugin author.

Since some time, there as been a change in the structure of $bp: see this topic.

You should edit that line to instead read:

$profile_link = $bp->loggedin_user->domain . $bp->profile->slug . '/';

why couldn’t you just do this: (of course add style <div>’s etc… just hacking this out quickly)

<?php if ( bp_has_friendships() ) : ?>

<?php while ( bp_user_friendships() ) : bp_the_friendship(); ?>
• <?php bp_friend_avatar_thumb() ?>

  <h4><?php bp_friend_link() ?></h4>

  <?php bp_friend_last_content_update() ?>

<?php endwhile; ?>

<?php else: ?>

<div id=”message” class=”info”>

<p><?php bp_word_or_name( __( “You have no friends”, ‘buddypress’ ), __( “%s’s friends list is currently empty”, ‘buddypress’ ) ) ?></p>

</div>

<?php if ( bp_is_home() ) : ?>

<h3><?php _e( ‘Why not make friends with some of these members?’, ‘buddypress’) ?></h3>

<?php bp_friends_random_members() ?>

<?php endif; ?>

<?php endif;?>

Honestly, I think it is time for a new host.

I believe buddypress highly recommends using subdomains for member blogs, for example:

myblog.example.com and if you host doesn’t support that I don’t think it is a solid hosting solution.

If you are trying out buddypress for a small scale deployment, with just a few friends using it and they don’t need blogs you might be ok.

There are already a few posts around here of what people are using for hosting, but I have never heard of a paid solution that wouldn’t allow nonwww domains.

Brad

tufancetin

çevirisini yaptığın dil dosyasını Buddypress-tr_TR.mo ve buddypress-tr_TR.po olarak bb-language klasörünün içine atıcaksın . Birde hangi sürümü kullanıyorsun ? Bb-language klasörünün yolunu göstermen gerekiyor.

Take a look at:.

http://kommune.ngcorp.de

http://bestronghearted.org

It’s a bug in the css. Andy just committed a huge amount of bug fixes. Lemme go check them out to see if this is one of them.

EDIT: Nope, but another forums user has a fix for this. See the ticket for details: https://trac.buddypress.org/ticket/535

I don’t know how Andy would fix it but this works ok for me.

Thanks for the tip. I’m sure others will find it useful.

Oh no, I’m following you out the door and to the grocery store.

They are the same theme, hosted in the same directory. It is only the home.php file that is in the way.

Follow the exact steps above, and delete the home.php file from your new theme. I called mine buddypress-sub, for example. I renamed the theme in style.css, did exactly as I mentioned above, and tada.

Same rules apply as above except keep the BuddyPress Home theme active and deactivate all others.

Keep in mind that widget layout will never follow, meaning that each new blog will need to configure its own widgets.

I recommend copying all of the contents of BuddyPress Home to a new directory, modifying the style.css to a new name, comparing your existing WP header.php/footer.php files to the ones in your new directory, taking out all the WordPress specific PHP function references and replacing them WordPress MU/BuddyPress ones. Tedious, but effective.

I found that the main hurdle when doing this kind of migration (for me) was letting go of my old WordPress ways of doing things. I.E. no longer using the page widget as my main navigation menu, etc… Which you can still do if you want to, there’s nothing stopping you. The functions are still the same, but you’ll still want to use the BuddyPress home theme as your starting point, as it gives you the building blocks towards integrating your existing theme with the new platform.

@johnjamesjacoby The News theme I am referring to is not a separate theme. It is the News/Blog theme that is embedded within BuddyPress that is the default theme for the admin on the News/Blog page.

To be clear: How can I make this theme: http://testbp.org/blog an available theme choice for member blogs?

Haven’t forgotten, just couldn’t find the topic.

https://buddypress.org/forums/topic.php?id=426

This topic is ultimately what helped me. I used his little $burt variable trick to help see if the two platforms were communicating in the back end, and it turned out they weren’t. This sounds like where you’re getting stuck as well.

1. Activate BuddyPress Home theme for main blog.

2. Site Admin -> Themes – Deactivate all themes including BuddyPress Home theme.

3. Site Admin -> Themes – Make sure News theme is enabled.

4. Find and activate the “New Blog Defaults” plug in. (Help ensure new blogs get the default theme you want.)

5. Configure “New Blog Defaults” and set default theme to your News one.

6. Create a new blog yourself, and you’ll be forced to use the only active theme, and cannot change to any other.