BuddyPress.org

Just ran a couple sites through the plugin move without any big problems. BP_PLUGIN_DIR and BP_PLUGIN_URL are nice additions.

The only thing I noticed is that the BP Core plugin needed to be activated first. I got some errors at first just clicking activate for the plugins from top to bottom.

Using the default BP Theme, latest WPMU 2.7 and BP Trunk … the FB Connect button is not showing when logged out as expected.

After activating the plugin and creating a fb application for my blog, I don’t see anywhere to enter the API Key or Application Secret. The only option in buddypress is to activate, am I missing something?

On the FB side, are there mandatory settings that need to be inputted other than Connect URL and Base Domain?

you have to put thoses lines in your wp-content/member-themes/buddypress-member/profile/profile.php to make it work like you want

you add this test :

<? global $bp;

if ( ‘is_friend’ == BP_Friends_Friendship::check_is_friend( $bp->loggedin_user->id, $bp->displayed_user->id ) ) {

?>

before thoses line

<?php if ( function_exists(‘bp_send_message_button’) ) : ?>

<?php bp_send_message_button() ?>

<?php endif; ?>

end then close the test

<? } ?>

Thanks for the clarification. I think there are two types of typical WP/WPMU/BuddyPress users: (1) like to run the latest bleeding edge on everything and (2) like to have a stable release that is easy to update.

Depending on the client and site, I fit into both categories.

And yes, “svn switch” is awesome — that’s how I update my normal WordPress.org installs every time a new release is ready (tagged). That workflow (svn switch with tagged releases) is a perfect setup for type 2 above since it’s mostly worry-free.

Again, from now on BuddyPress will ONLY work with WPMU 2.7.1+ so please use the 2.7 branch from the WordPress MU SVN repo. Link: https://trac.mu.wordpress.org/browser/branches/2.7

I’ve been using the 2.7 tagged release for MU, not the branch. Are you saying that going forward BuddyPress requires keeping our MU installs up to date with the 2.7 branch rather than using a tag (2.7.1 doesn’t have tag yet I noticed)?

Using the tagged releases is what I always recommend for normal WordPress installs since it’s usually a nice stable release with a clean cutoff at a version number, and doesn’t get committed to generally. But it looks like MU devs (Donncha) don’t tag as often as WordPress.org devs do, so maybe it’s a bad idea to rely on tags for MU.

I changed Wire to Wall, see my notes at https://buddypress.org/forums/topic.php?id=1877#post-9953.

Some useful ideas can be found here: https://buddypress.org/forums/topic.php?id=1651

http://wWw.iCAMBO.INFO just started few days

Good suggestions, and I think for the time being we’re all waiting for the 1.0 release before we start documenting code. Until then, any of it is subject to change at any point.

Once 1.0 is out there is a benchmark to start documenting from, in my opinion.

I can give you a hint though, check out the /css directories in each plugin, check out the member-theme, the buddypress-home theme, and you can also create a file called “site-wide.css” and put it in your /css directory for your home theme, and put all of your site-wide CSS changes in there.

Please disregard my comment posted in error

Here is the description of the album component thats said to be out in 09 sometime.

“Photo Albums

Members of a BuddyPress installation will be able to create their own photo albums. These albums can be shared with friends and groups.

Each member will be given a certain amount of space, which can be set by the site administrator. Albums and photos can be tagged. It will also be possible to browse public photos via photo tag pages that other members can browse (just as you browse blogs via tags on wordpress.com).

Photos can also be tagged to a group as mentioned previously in the group component overview.

Photos can be uploaded from a members computer, and will be re-sized accordingly using the built in WordPress image manipulation functions.”

Thebigk,

This isn’t a BuddyPress issue as the rich editing options and settings are handled through WordPress MU.

From what I could see on a quick search on https://mu.wordpress.org/forums/, the rich editor options will only affect new blogs (not ones already created). For older ones, you might have to manually update the setting in the database with a tool such as phpMyAdmin.

I’d suggest also digging around more in the MU forums for such terms as “rich editor” or “rich editing” to see if there are more threads on this topic.

@Ninh – Sounds like you are on the right track. One word of caution, though: if you are manually copying files from one place to another it’s very easy to lose hidden files, like .htaccess files. These are very important and can cause problems with your install.

It’s highly recommend to start over with a new download or SVN checkout at the new server location so you are sure to get the correct setup.

@Dace – Same thing… if you upgraded and only copied certain files you can get into problems. If you are going to upgrade, it’s recommended that you replace the entire BuddyPress install (not just pieces).

Like I said before–and you can search the forums–this topic is very common and usually comes down to a few things: GD support, htaccess issues, or file permissions on the directory where the avatar images are uploaded to.

Great — glad to hear it. Sorry to have missed your previous questions.

where do i upload the .po file to??

Anywhere on the server, it doesn’t matter.

what does this command do exactely

It takes your PO file and creates the MO for you.

did you mean.. ”and added the buddypress-spots.mo file there…”

Yes.

i have already set up in wp-config.php will this clash with what you have said to doo..

Hmmm… that I don’t know. I don’t use those configuration settings, myself. I would suggest commenting them out and testing your site. If the language file changes are still working, go ahead and delete those lines from your wp-config file.

Overall the language file is a better long-term solution since you can make changes for other labels there as well if they come up in future versions, whereas those custom definitions are only specific to a few labels.

Hello,

I have installed the trunk version of buddypress.org on my site . I used the link for installation — https://svn.buddypress.org/trunk/. After that i proceeded installing BP-FBConnect Plugin, using the link http://testbp.org/plugins/bp-fbconnect.zip. I downloaded the bp-fbconnect.zip to the /wp-content/plugins/ directory. After that i extracted it. I have not performed any further steps in the installation. However when accessing my site and logging in, the fconnect plugin is not listed at all.

Please advice. is there further steps involved in the installation. Thanks in advance.

Regards,

Gokul.

This topic has been posted before. It’s not for distribution.

https://trac.buddypress.org/browser/trunk/bp-forums/installation-readme.txt

@Dace – I saw your comment in this related thread… but did you try the things that were suggested there: fixing permissions, checking for GD support, .htaccess issues, etc?

Avatars not uploading is a very common issue, so much that it has an an entry on the FAQs page:

Why will avatars not upload on my server? This could be a number of things, but make sure you have the GD image library installed. It might also be permissions, so make sure the web server has correct permissions.

Make sure to check these things (if you don’t know how to check for GD library support, ask your web host) and report any errors in your server logs.

This maybe a good starting point for you

/**

* bp_create_excerpt()

*

* Fakes an excerpt on any content. Will not truncate words.

*

* @package BuddyPress Core

* @param $text str The text to create the excerpt from

* @uses $excerpt_length The maximum length in characters of the excerpt.

* @return str The excerpt text

*/

function bp_create_excerpt( $text, $excerpt_length = 55, $filter_shortcodes = true ) { // Fakes an excerpt if needed

$text = str_replace(‘]]>’, ‘]]>’, $text);

$text = strip_tags($text);

if ( $filter_shortcodes )

$text = preg_replace( ‘|\[(.+?)\](.+?\[/\\1\])?|s’, ”, $text );

$words = explode(‘ ‘, $text, $excerpt_length + 1);

if (count($words) > $excerpt_length) {

array_pop($words);

array_push($words, ‘[…]’);

$text = implode(‘ ‘, $words);

}

return stripslashes($text);

}