BuddyPress.org

Hi all,

I am currently in charge of Vietnamese l10n for WordPress, WordPress MU, WordPress.com, Gravatar, and BuddyPress is also maintained by me.

I started working on BuddyPress since its public beta, and I’ve been waiting for an official i18n repository, in the meantime, I uploaded the l10n files to repository of WordPress.

@Wpviet23: You can maintain your version apart, since I prefer keeping all terms in Automattic products synchronous, if you have feedback, please send me an email. Again thank you for your contribution.

open up style.css, you need to modify the header (i.e. this section)

/*

Theme Name: BuddyPress Default Home Theme

Theme URI: http://buddypress.com/

Description: A widget framework theme for the home of a BuddyPress enabled installation. This theme is not required to use BuddyPress.

Version: 1.0

Author: Andy Peatling

Author URI: http://apeatling.wordpress.com

*/

Thanks for the information J J J !

Gaetan

We’ve installed buddypress + wordpressmu on our server. We’ve also installed RPX module foe WordPress. It’s working fine for login and allows user to login without sign up.

But we want to have it on sign up screen and replace the existing signup process with RPX and redirect the user to custom welcome page. Is there any work around for it?

@Kunal17

Is the bp-custom.php file something that I download or create?

You create it yourself, and place it in “/wp-content/plugins”.

What is the ‘mysite’ language translation as defined in the tutorial?

That is a sample definition that I used for the tutorial — you can use whatever you want. Just make it a label that makes sense to you and your site.

Still wondering about the command to convert .po to .mo. How is that run and from where?

Running that command requires that your web server have basic GNU gettext support — if you don’t know if it’s supported, ask your host (it’s pretty standard on most Linux servers).

Running this command also requires command line access to your server via a program like PuTTY (Windows), Terminal.app (Mac), or from inside an FTP program and requires that your server support “msgfmt”. If you do not know how to run commands like this, or don’t have command line access to your server, please see Translating WordPress for other software options for converting language files (like Poedit).

@Craig dean

Also not understanding the conversion of the po. to the mo. using the run command. Is it a ftp app command. Just not sure.

See me answer above. I also updated the Codex page with these notes.

@Mstoppay

my bp-custom.php file wasn’t loading. Once I moved it out of the buddypress folder and into the plugins folder the language change worked… anyone know why that is?

Yes, as of BuddyPress 1.0 the “bp-custom.php” should be placed in the “plugins” folder instead of inside the BuddyPress directory, as noted by Andy in this thread. Thanks for the reminder — I updated the Codex page to note the correct location.

Note also that if you use the “Automatic upgrade” option to update your BuddyPress install, make sure to backup your language files first since they could be removed during the upgrade process (see this thread).

I’m developing a customised buddypress member theme and a directory view special for artists, musicians and multi media interested people.

This is my fun learning project to get deeper into wordpress and buddypress theme design and plugin development.

The hole website is still in beta mode. So don’t aspect it to work 100%

http://rheinrauschen.de (In the moment just firefox ie will come al last)

I will give the theme and plugin’s step by step to the community.

For this I have to wait for some bug fixes, the stable bp-events component. Better forum integration and many more….

Well, a component can be considered a type of plugin similar to any other WordPress plugin, except instead of hooking into WordPress alone, it’s hooking into BuddyPress AND WordPress.

Widgets are accessories, more or less. They aren’t 100% necessary, but most people welcome them as they’re an easy way to include whatever content it is that your plugin is supposed to spit out, on whatever pages that someone has enabled widgets to be displayed on.

A new component is needed when BuddyPress simply doesn’t have the capability that you want or need. The two next components currently in development are status updates (think twitter) and photo albums (think flickr.) Those are functionalities that don’t currently exist in BuddyPress.

Now both of those components may/will have their own widgets also, to do different things. The status update widget may incorporate the ability for the blog author to update their status from their blog, or it might display x amount of recent updates, or both. The photo album widget may include the most recent x photos, recent photo comments, etc…

In the case of BuddyPress, most widgets will come as part of a component. The component will bring in new functionality, and the widgets will allow that function to be displayed without knowing any HTML or PHP.

Bryan868, the short answer is there are some larger changes in the WordPress.org 2.8 and 2.9 pipeline that have been strongly hinted at recently. Those changes won’t make their way into WPMU necessarily at the same time, so we’re mostly safe for now using WPMU.

BuddyPress will continue to get updated as WordPress versions change, however because there are a lot of dependencies there, and lots of distinct differences between a .org install and an MU install, it isn’t just flipping a switch and making it go.

It is going to happen, just not as soon as most people wish unfortunately. Hopefully everyone that’s salivating at the chance to open up their own .org sites to start adding friends and making profiles can understand the dev process and try to be patient.

I know it isn’t exactly what everyone wants to hear, but it’s the straight forward truth of the matter as it stands today. It may change tomorrow, but that’s where it is now.

Why not anytime soon?

Erich73-

Toni is using the P2 theme. You can get it here: https://wordpress.org/extend/themes/p2

Bbn-

Rather than trying some fancy install via packaged tarballs, I’d suggest a plain, simple install from scratch. Even though you went back and, as you state, “tried to do a more careful replacement of the files,” try a clean-slate install.

Delete everything, including your MySQL DB–assuming you don’t have any important data. Then, download and install WordPress Mu 2.7.1 from here. Get it working before attempting to install BuddyPress.

Once it is working, download BuddyPress and follow the readme.txt instructions.

Looks like this is happening to a lot of sites

I understand your frustration. But, when I search Google for “Failed+opening+required+’BP_PLUGIN_DIR”, I can count exactly 6 actual sites with this error and then several comments within blog posts that indicate the same issue.

Combine that with the half a dozen reports in the BP Forums for this issue, and you get maybe 15 people–assuming none of these people have commented in multiple places. That is not “a lot of sites”.

I ran into this same error message this morning. In case it helps, here’s how it happened to me.

I had MU 2.7 installed on a ubuntu server and MU 2.7 also installed on a local dev installation of ubuntu (both 8.10, if that matters). I upgraded the dev MU to 2.7.1, then installed buddypress. worked great. then I tarred up the dev installation, copied it over to the server, and overwrote the old 2.7 MU non-buddypressed install with the dev files. Ran the upgrade (at http://veryhandso.me/wp-admin/wpmu-upgrade-site.php). Tried to preview the buddypress theme and end up with the error mentioned above.

I then backed up and tried to do a more careful replacement of the files as outlined on the upgrading wordpress page (https://codex.wordpress.org/Upgrading_WordPress). Still no love.

Thanks for any help. Grateful newbie.

Ben

Ahhh… The truth, shall set you free…

Any possibility that the Drupal install is mucking this up? I’ve got no experience with that one.

(To explain what’s going on, this isn’t a matter of directory structure, because those directories are virtual; they don’t really exist anywhere. There is no physical folder anywhere in your install called “members” or “users” or anything. The URL is caught by .htaccess and WordPress, and is virtually re-written to match the content it is displaying.)

Does that make more sense? I know it’s hard to understand and have faith in at first, but I promise it’s totally fine.