BuddyPress.org

You can create a file, bp-custom.php, post in necessary code and upload to your wp-content/plugins directory

Sitgmartyr – This issue has been reported and fixed, but unfortunately there will not be a public, new release under the 1.2 series because attention has shifted to 1.5.

However, you can patch and fix this yourself:
https://buddypress.trac.wordpress.org/changeset/4626

Or download the 1.2 dev branch and overwrite your current “buddypress” folder:
https://buddypress.trac.wordpress.org/browser/branches/1.2 (scroll to the bottom and click on the ZIP download)

Remove all your htaccess code that you’ve added as that isn’t related to this issue.

@foxly Both you and @fanquake are Editors on codex.buddypress.org. (It used to be that everyone on bp.org was, but the synching script broke at some point.) Thanks!

Overall progress for today…

Google Code seems to have all their servers working again and the Fixing plugins for BuddyPress 1.5 wiki is coming together nicely. Over the next few days we’re going to be adding some new failure cases and improving the quality of the existing articles.

@boonebgorges We’d be honored if you linked to us from your blog. Also if there’s anything we missed that you’d like covered, just let me know and we’ll add it to the wiki.

We’ve updated the BuddyPress 1.5 plugins compatibility page. We split it into three different spreadsheets (that all auto-update from the master spreadsheet) as per @karmatosed ‘s request. We created embeddable widgets for each of these so karmatosed can embed them in the BP codex. As per @djpaul ‘s request we removed all non-error related tester comments.

It would be helpful if you could give one of our team members write-access to the codex blog so we can assist karmatosed with getting the embedded plugin spreadsheets working properly.

^F^

I knew you knew @foxly

@boonebgorges

Yes.
I know.
I was tired (18 hours and counting) and pasted the wrong block of code.

We fixed that one and moved on to a bunch of other things

^F^

add_action( ‘bp_setup_globals’, ‘bp_cubepoint_setup_globals’ ); <— is commented out, you should be using that to set global

I’m a bit confused at what this discussion is trying to accomplish

When you set up globals, as in the function excerpted above, you should hook to bp_setup_globals.
When you set up navigation, as with functions like bp_core_new_nav_item(), you should hook to bp_setup_nav.

I sent you a email. Change it to this. Now it’s not even showing up in the admin bar. Sorry for being a pain, just want to get this patched up.

`add_action( ‘bp_setup_nav’, ‘bp_cubepoint_setup_globals’, 2 );
add_action( ‘bp_setup_admin_bar’, ‘bp_cubepoint_setup_globals’, 2 );`

@xberserker

Cool! Now we have a block of code we can use for another example. You need to hook to the ‘bp_setup_admin_bar’ action to get it to reappear.

Fire man an email (CarlRoett [at] gmail [dot] com) and I’ll walk you through it.

^F^

https://codex.wordpress.org/Changing_The_Site_URL
https://codex.wordpress.org/Moving_WordPress

== If I don’t have bp-config.php I just create it inthe buddypress plugin directory, right? ==
The internal Forum installation process will automatically generate the “bb-config.php” at root of your install when you go through the process.

@foxly Thank You. I don’t mind at all. I tried changing what you mentioned and this is what I have now.

Now it’s not even showing up in the buddypress admin bar on the front end but does when looking at the admin area. But it’s still acting the same as before.

`function bp_cubepoint_setup_globals() {
global $bp, $wpdb;

$bp->cubepoint->id = ‘cubepoint’;
//$bp->cubepoint->table_name = $wpdb->base_prefix . ‘cubepoints’;
$bp->cubepoint->table_name = $wpdb->prefix . ‘cubepoints’;

// custom SLUG
//$bp->cubepoint->slug = ‘cubepoints’;
$bg_cp_custom_slug = get_option( ‘bp_slug_cp_bp’ );
$bp->cubepoint->slug = $bg_cp_custom_slug;

$bp->cubepoint->points_slug = ‘points’;
$bp->cubepoint->table_slug = ‘table’;
$bp->cubepoint->earnpoints_slug = ‘earnpoints’;
$bp->cubepoint->awards_slug = ‘awards’;
$bp->cubepoint->bp_cubepoint_per_page = get_option(‘bp_points_logs_per_page_cp_bp’);

// Notifications
//$bp->cubepoint->format_notification_function = ‘bp_cp_awards_format_notifications’;

/* Register this in the active components array */
$bp->active_components[$bp->cubepoint->slug] = $bp->cubepoint->id;

if ( $bp->current_component == $bp->cubepoint->slug && $bp->cubepoint->table_slug != $bp->current_action ){
bp_cubepoint_query_points();
}
if ( $bp->current_component == $bp->cubepoint->slug && $bp->cubepoint->table_slug == $bp->current_action ){
bp_cubepoint_query_points(‘uid=’);
}
}

/***
* In versions of BuddyPress 1.2.2 and newer you will be able to use:
* add_action( ‘bp_setup_globals’, ‘bp_cubepoint_setup_globals’ );
*/
// Pre-BuddyPress 1.5 Beta
// add_action( ‘wp’, ‘bp_cubepoint_setup_globals’, 2 );
add_action( ‘bp_setup_nav’, ‘bp_cubepoint_setup_globals’, 2 );
add_action( ‘admin_menu’, ‘bp_cubepoint_setup_globals’, 2 );`

Thanks for posting that tutorial, @foxly. The ‘wp’/’admin_menu’ hook is a very old technique that has nonetheless continued to work. I’ve got that on my list of things to write about on bpdevel.wordpress.com. Maybe I’ll do so later today, and link to your very helpful wiki page.

Same issue here with BuddyPress 1.2.9 & WP 3.2.1

The problem seems to come from this file :
/buddypress/bp-groups.php
which calls
do_action( 'groups_promoted_member', $user_id, $bp->groups->current_group->id );

before the file below is included
/buddypress/bp-groups/bp-groups-notifications.php
that should add the action to add the notification:
add_action( 'groups_promoted_member', 'groups_notification_promoted_member', 10, 2 );

Quick fix:

function addGroupNotificationFile($user_id, $group_id)
{
require_once ( BP_PLUGIN_DIR . '/bp-groups/bp-groups-notifications.php' );
}
add_action('groups_promoted_member', 'addGroupNotificationFile', 100, 2);


What versions of WP and BP are you using, @esploded? What errors do you get in your web server’s error logs? I bet this is to do with https://bbpress.trac.wordpress.org/ticket/1486

BuddyPress doesn’t use any custom post types or taxonomies. We don’t know what type of thing you want to achieve, or where you want it, but; have you checked out any of the major forms plugins?

@xberserker

Hi Tosh. We’ve created a wiki page covering the problem your plugin was experiencing, and detailing how to fix it.

We used the code you sent us as the example to make it easier for you to fix the actual plugin. If you’re not comfortable with your code being up on the wiki page, let me know and we’ll create a new example from scratch.

Note that Google is updating the servers our wiki is hosted on today. If any of the wiki pages look a bit “odd”, just hit refresh a few times.

Thanks!

^F^

@djpaul

We just thought it would be helpful to other developers, as many people learn best by studying other developer’s code. As requested, the “Excellent” note has been removed from the spreadsheet.

^F^

Wait wait wait – why are you deleting buddypress? I dont’ understand.

Either way if you follow the instructions to create a new forum then you are able to see your forums and click Post New Topic then you’re doing it right so far.

If you’re getting that bug there is a fix that seems to work for me, I found it on the site:

You have to go to group admin settings where you turn on/off forums for that group.

You need to check/un-check the box a few times to ‘massage’ the form into actually tuning it on. Yes I know it sounds retarded but it’s true. You click and unclick that selection box about 4 times and then save. You should be good to go.

> Will get that sorted trying to get the spreadsheet to work in the page to save time currently but will get it marked as not fail because of those.

If this is done, I’d argue that the “Excellent” ratings should just be a “pass”. The “excellent” rating, compared to the others, is subjective and is dependant on who tested the plugin (and their knowledge of PHP, WordPress and BuddyPress APIs, etc).