BuddyPress.org

Sounds like you’re using an older version of WordPress.

Deactivate BuddyPress and upgrade WordPress:
https://codex.wordpress.org/Upgrading_WordPress_Extended

This is because the BP Template Pack plugin needs to be updated, particularly the JS variables.

Read this for a temporary solution:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/buddypress-template-pack-and-buddypress-1-2-6-things-break-but-i-have-a-solution

See:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/12-6-upgrade-date-offset/

It’s already been filed as a bug here:
https://trac.buddypress.org/ticket/2779

No need to hack BP.

Put the following in your theme’s functions.php:

`
function ray_bp_get_send_public_message_link() {
global $bp;

return wp_nonce_url( $bp->loggedin_user->domain . $bp->activity->slug . ‘/?r=’ . $bp->displayed_user->userdata->user_login );
}
add_filter( ‘bp_get_send_public_message_link’, ‘ray_bp_get_send_public_message_link’ );

function ray_bp_get_send_private_message_link() {
global $bp;

return wp_nonce_url( $bp->loggedin_user->domain . $bp->messages->slug . ‘/compose/?r=’ . $bp->displayed_user->userdata->user_login );
}
add_filter( ‘bp_get_send_private_message_link’, ‘ray_bp_get_send_private_message_link’ );`

I believe this is fixed in trunk.
https://trac.buddypress.org/changeset/3591

@driz

BuddyPress is already a theme. Look at bp-default. That is a full WP theme that for some reason was bundled with the plugin. There is a huge mess of code devoted to making this setup work. It is nearly impossible to freely modify the templates, even if you roll your own BuddyPress theme, because the javascript is so tightly bound to the ids and classes in the markup.

I don’t think its reasonable anymore to call BP a plugin, since it does not enhance a WP site in the purest sense. It completely takes it over and defines an entirely new set of rules for how to customize the look of your site. That sounds like a theme to me.

If you think about BP as a theme, then the only acceptable ways to solve the issue and stay true to WP is pages or custom post types. This only doesn’t make sense though because BP is made up of many components that should be making their OWN decisions about how they get displayed.

So back to my original point. BP is defining too many rules, and forcing components to adhere to the default theme itself, instead of a theme prototype (which is how WP works). If BP was doing it the “right” way, then this whole issue would be moot, because each component would be deciding how its URL was determined, and the end user could decide if they liked it or not.

I think this is in the scope of the topic because it gets into defining the problem that needs to be solved, which is important before working on a solution.

If you really want to take this where the root of the issue is, the underlying problem is that BuddyPress is actually a theme that has been jammed into the plugin directory and then tightly coupled to what should be multiple plugins (aka components) in one massive package.

I am starting to feel like the only way to restore any kind of reasonable extensiblity of the BP interface it to split it into a theme, and the components into plugins which all adhere to a very strict API defined by the THEME, not a “core” plugin.

Of course this would break every existing install. It would have to be an internal fork that was deemed to be the new way forward.

Well, don’t blast something for being exactly what it’s suppose to be. Since BP is a WordPress plugin and the dummies books are for absolute beginners then it makes sense to spend a great deal on the core. Is there room for more documentation? Yes!

Read the documentation on this site: http://codex.buddypress.org
Visit these:
http://etivite.com
http://bp-tricks.com
http://wpmu.org/category/buddypress

I’m sure there are more resources out there. Just search or ask.

Lol, yes, I am a troll.
I am old and smell funny and live in a cave.

Look, in today’s economic climate, the job market is pretty much empty, even in Australia. Even if you do get a job with a company, then you’re hard pressed to pay rent and bills, and you can never think of buying a house.

The only option left is web-development and small business. I’m sorry I got upset about it yesterday, but it’s really frustrating when you get to a golden package like Buddypress and you find that they documentation is really sparse. Then you find that there’s a book out there specifically about the package, and all that’s in it are the installation instructions and how to use the admin panel.

For the record, there’s a second book called ‘WordPress for Dummies’, so that’s why I thought it wasn’t right that her first half of the book is about WordPress.

@xevo
It doesn’t have to be GPL if theme’s not *distributed* like e.g. custom theme for a client site. But if theme’s going to be sold or distributed in the wilds for free, it has to GPL.
Remember that thingamagig with the Thesis theme?
http://ma.tt/2010/07/theme-are-gpl-too/

Syn-thesis 1 and Chris Pearson

=== have issue as buddy press link are coming at the bottoms. ===

Looks to me like a regular default BuddyPress installation. What bottoms are you referring to?

Interesting points. Working recently with trunk prompted the same thoughts vis-a-vis disabling BP and being left with a heap of odd pages, but then I simply removed or unpublished those pages.

It would be interesting to hear the comments of the core devs who are :

@jjj
@djpaul
@boonebgorges