BuddyPress.org

Hi.
The right way to do this (as i have heard)
https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/
If you use this method you have full control over styling and it works perfect.
@mikepratt gave this tips in this presentation that i think is a awesome. Check it out here

DFW WordPress MeetUp: BuddyPress: Social Networking in Box

@hnla thnxx

@ray thnxx too. the patch works perfect

Just to add to this, if you’re using a custom WP theme and you want to add BuddyPress functionality, then you’ll need to use the BP Template Pack plugin:
https://wordpress.org/extend/plugins/bp-template-pack/

If you’re used to customizing themes, then you’ll feel right at home with BP templates and custom loops. Check out the codex for more info.

What hnla is talking about is if you’re using WP 3.0 and you want to add user blogs, you’ll need to add network functionality. Read this post by Pete Mall for more info:
http://developersmind.com/2010/05/17/enable-multi-site-in-wordpress-3-0/

You need to use a WPMU plugin like New Blog Defaults:
https://wordpress.org/extend/plugins/wpmu-new-blog-defaults/

Put the PHP file (not the folder) in /wp-content/mu-plugins/

Haven’t tested compatibility with WP 3.0, but it should work.

@si you’ve added in a carriage return/line feed after the closing ?> or before it’s opening, anything that represents a character is interpreted as browser output. Ensure you have no whitespace after the closing php tags.

@ray added code to functions in bp default

but getting eeor wen going to login pae, logout link ..

header modification already send some sort error

Buddypress runs as a plugin of a WordPress install, either WP single or WPMU / WP MS(WP 3.0)

If you have your WordPress install up and running then you need to upload or install via dashboard the BP plugin and activate, no further domain issues unless you have decided to run user blogs then you have considerations such as sub domains for the user blogs or sub directories and possible DNS issues if you want to use sub domains.

thnx ray

Ron said:

Folks,

The issue here with 3.0 is that if an existing WP 2.9.2 install with uploaded media upgrades to 3.0 and enables the network the blog option for the upload_path can’t be changed to the blogs.dir folder because the existing media becomes inaccessible.

So my question is: is there a way to get the pre-existing media to show-up? I went from WPMU 2.9.2 to WP 3.0 – and all of my media is gone? It won’t even show up, if I enter the path to the file directly in the address bar? Shouldn’t it at least show an image if I put the exact path in?

I also tried to upload new media – and that doesn’t show up either, so I’m not sure if what Ron posted is my issue?

Thanks!

Ah erm so it does; did say it wasn’t hugely tested. Ok then those that are running on bp-default theme will need to add your function to main functions file, please ignore my well intentioned but erroneous post above. (Last para stands thinking about though, the flood gates will open soon)

Thinking further it makes sense to add fix to main functions or bp-custom[bp-custom.php isn’t a standard included file] so that it does get erased from existence on upgrade – one less thing to remember to adjust for people

@hnla – While your method is well-intentioned, it breaks actual 404 pages. Try typing in example.com/hfklsadjfkasdhf and you’ll see the activity page, instead of the 404 page!

You could just copy my code directly into the bp-default theme’s functions.php so it will be overwritten when the next version of BP comes out.

FYI, the code can also go in wp-content/plugins/bp-custom.php as well and not necessarily in a child theme’s functions.php file.

@r-a-y Thanks r-a-y that does indeed fix things, albeit in a hackish manner

I understand what you’ve done with it, and it occurred to me that there may well be an issue with many who are using bp-default and choosing or at least attempting to choose activity stream as front page, they will not be running a child theme?

I had a play around with the bp-default functions file and specifically the function: ‘bp_dtheme_page_on_front_template’ controlling this aspect, keeping your workaround in mind I simply adjusted the add_filter from:

add_filter( ‘page_template’, ‘bp_dtheme_page_on_front_template’ );

To:

add_filter( ‘404_template’, ‘bp_dtheme_page_on_front_template’ );

This appears to work correctly on one of my clean installs WP 3.0 BP 1.2.4.1 bp-default

Although this is adjusting core file, in the interim/short term until the correct solution is found would this not serve those that I mentioned above and when that correct solution found the hack would simply be overwritten in a point upgrade?

This isn’t a hugely tested solution, it works on the surface on one of my various installs, but there may well be issues I have missed, it’s suggested more as food for thought.

Lastly I can imagine that there are going to be many rushing into upgrading (that ‘upgrade now’ button is like the red ‘Do NOT Press’ button; too much of a temptation ) Although the upgrade is not problematical the few manual steps required might well cause some people issues and the fix discussed here be required so as such it might be worth a sticky post pulling the steps together along with any other fixes one might require, that people can be pointed to?

When could an official fix be expected? Thanks!

You could try GlotPress:
http://trac.glotpress.com

http://blog.glotpress.com – GlotPress blog

It’s not a plugin, but it allows you to translate scripts using a front-end interface.

There’s not much documentation or anything like that since it’s still quite an early script, but if you feel the need to edit language files using a front-end script, GlotPress is an option.

—

[EDIT]
Just found the following WordPress plugin:
https://wordpress.org/extend/plugins/easy-translator/

It’s a little old, but you could give that a shot as well.

Works like a charm for me!

WP 3.0 and Buddypress 1.3 in two steps:

1) Make sure upload_path option is set to wp-content/blogs.dir/1/files
2) in old .htaccess change

RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L] TO

RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

Works!

Read and implement everything listed in Pete Mall’s post:
http://is.gd/cT9kB

and FYI, it’s WordPress 3.0 now

@r-a-y thanks a lot for that. This is a good workaround for now.

@andrea_r – Or you can simply read Pete’s post
http://developersmind.com/2010/06/17/upgrading-wordpress-mu-2-9-2-to-wordpress-3-0/

@allenmcgraw – check out this post:
http://is.gd/cTrBB

Locking this thread.