BuddyPress.org

i’m trying to install buddypress and i get this error on the bottom of my screen during step 3: “Fatal error: Call to undefined function bp_core_is_multisite() in /home2/ihearta1/public_html/wp-content/plugins/bp-template-pack/bp-template-pack.php on line 188” Please help!

Silly question, but you do have BuddyPress activated on your site right? This is one of the first things that is fired when you have BP activated.

*Edit – Paul, you’re one step ahead of me!

Is the main BuddyPress plugin active? Which version are you using?

@johnjamesjacoby We probably need to update Template Pack to check it works ok with the current point release, but as far as I know it still should work.

Anyone?

Hi Simon
No, that’s about as specific (and mysterious) as you’re going to get. If you aren’t using the BP-Default theme (unedited), switch back to it. Does the problem go away?

If it does, have a look at your actual theme’s functions.php, or post a link to it from pastebin.com

It could be a problem with your server. However, this most likely means you have a broken link on your site.
Check your theme for broken images, stylesheets, etc.

If you have access to the server error log, you can find out specifically which file is the culprit.

What do you have listed in your first profile group?

And yes, Paul is correct, you can modify the registration template in your child theme — /registration/register.php — to add additional groups. You just have to modify two lines in that template for this to work.

Or, you can make the appropriate changes to the bp-default/registration/register.php template file in your (child) theme. Let us know if you need a pointer for that.

@elizawhat – You need to finish your upgrade from WPMU to WP 3.0 properly.

Read and implement everything listed here:
http://developersmind.com/2010/06/17/upgrading-wordpress-mu-2-9-2-to-wordpress-3-0/

theme activity/post-form.php

The reference in the two posts above yours is saying that the simplest approach is to edit the file entry.php in the /activity folder of the theme; this would be preferably done as a child theme i.e a copy of the files in a new theme directory you would then be looking for lines such as:

<a href=”<?php bp_activity_comment_link() ?>” class=”acomment-reply” id=”acomment-comment-<?php bp_activity_id() ?>”><?php _e( ‘Reply’, ‘buddypress’ ) ?> (<span><?php bp_activity_comment_count() ?></span>)</a>

and removing them or placing some form of conditional statement around them – I removed all links for a copy of entry.php which I pulled onto a custom frontpage but allowed the links for the activity stream as a directory view.
It’s a little long winded but straightforward

Child child themes aren’t supported in Buddypress

You mean that the secondary sites’ themes must contain do_action( ‘wp_footer’) ? Where?

The article is pretty clearly written really.

It says look at the bp-core-adminbar.php file as a point of reference, here is where the menus are constructed and clue you in to how they are added to the actual pages via the action hooks.

If you simply wanted to remove an action as the page describes you would simply add an opposite action i.e:

remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6);

Further it explains that you can now create a new function based on the existing one and is where examining the original file is useful, you can simply copy the whole function bp_adminbar_blogs_menu() paste it into a child themes function.php file rename the function slightly bp_my_adminbar_blogs_menu() make whatever modifications you want within the function then add itback into the mix via a new add_action so you remove original:

remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6);

## create new function ##
function bp_my_adminbar_blogs_menu() {

}
## add new function to admin menubar ##
add_action(‘bp_adminbar_menus’, ‘bp_my_adminbar_blogs_menu’, 6);

You add mods such as this to functions.php file as this way you ensure that you do not have to continually re-write them in a core file, core files should never be changed as each new BP version will replace the files and any adjustments will be lost, working in a child theme ensures these changes are preserved and continue to work after version upgrades.

& I’m with @gregfielding here, we absolutely need a custom background for group pages. Why don’t you use the perfect add_custom_background(); for wp 3.0, just translate it to work from the frontend?

What’s the latest development here @rustybroomhandle?

If you’re using BP 1.2, try:
bp_is_my_profile()

This doesn’t exist in the BP 1.1 series (which I’m guessing you’re still using), so here’s the complete function that you can plop into your theme’s functions.php:
http://pastebin.com/nfm8WFVf

This issue is addressed in the newer releases of BP.
Please use the latest release and report back.

Doesn’t necessarily work like that, some rulesets are within a block of generic table styles, some within other sections, you won’t find a specific block of styles to easily lift out. Really your best approach if you are building as a child theme is to call in the default.css and then overwrite it with your styles in styles.css or custom.css, as you do that you can, if necessary, remove default styles as you identify them.

Using Firebug doesn’t force you to rebuild anything if you follow the general approach that is intended when using a custom.css, you still use default.css then use Firebug to identify the ruleset styling an element and copy the selectors to custom.css and style to your requirements, remove the original default rulesets if you want to or simply leave them in place.

+2
wp3.0 – mutisite enabled – no plugins (except buddypress 1.2.5) – Buddypress default theme