BuddyPress.org

@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 );`

Do you have this in a url we can check out? Much easier to see what’s going on that way.

You also might want to consider importing the bp-default theme’s stylesheet near the top of your child theme stylesheet, and then only including your custom CSS on the child theme stylesheet. See https://github.com/davidtcarson/frisco/blob/master/style.css for an example.

It sounds like you might have copy/pasted the stylesheet from bp-default into your child theme and that’s probably not a good idea.

`div.item-list-tabs ul {
list-style: none;
}`

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.

@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^

> 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).

@djpaul
@boonebgorges
@karmatosed

FAIL = “Does not run on BuddyPress 1.5. No workaround available.”
MARGINAL = “Plugin works well enough to be used. Workarounds may exist for broken functionality. Or, all plugin features work but the plugin has huge numbers of debug errors indicating it will likely break in the near future unless it is updated.”
PASS = “All plugin functions work on BuddyPress 1.5”
PASS + “Excellent” = “High quality code. In the tester’s opinion, other developers can use this plugin as a working example to study when fixing their own plugins”.

If you think you’ve found a mistake in the list, contact us and we’ll fix it. Probably within a few hours.

Other status levels:

SCRAPING = “BP-Media Team has been sent the URL of a plugin that somebody wants tested.”
QUEUED = “A snapshot of the plugin info and files has been pulled and is waiting in the test queue”
SENDING = “Plugin test package is being sent to a tester via Skype”
TESTING = “Tester has acknowledged receipt of the test package”

Thanks!

^F^

@davidtcarson Another thing: We have two search bars: one in the Buddy Bar up top and one across from the site logo. The one in the Buddy Bar is kinda useless though because it doesn’t allow you to select between Members/Groups/Forums/Posts. So, perhaps a tip in the Readme file for how someone could get rid of that one?

Another thing, I guess: Profile pages are pretty empty to the right of profiles – a looooot of space is wasted, especially when you’re using a small netbook like me. But I suppose, changing it might interfere with other plugins that place things there. Perhaps a setting in Admin where you could alternate the profile to use the space a little more better (per, or to have it like it is right now (so you could use other plugins). (Or, perhaps even a “sidebar” up there so we could stick some widgets/text/etc. in there if we wanted to?)

Also, would be nice if we could have two sidebars, on the left and on the right, to make use of the room even more. (I really want this feature lol)

I just got the latest version a few hours ago. For me, the menu only looks okay if I don’t assign a menu to the theme in Appearance > Menus > Theme Locations. If I do set it, then it looks like it does in my image above.

Also, in the backend, I’m seeing this message:
“You’ll need to activate a BuddyPress-compatible theme to take advantage of all of BuddyPress’s features. We’ve bundled a default theme, but you can always install some other compatible themes or update your existing WordPress theme.”

Also, in your profile > Activity tab > Personal (when viewing another member’s profile) / Mentions / Friends / Groups, there is no spacing above the first activity stream item

That’s all I could find! Good job!

Any luck checking to see if the theme designer released a new version since BP updated? I use premium themes built for BP too, and our designer posted some updates to his theme too.

If there is no black bar and it’s just a list of items then it sounds like a style sheet issue. If you reset to the bp default theme is it working?

Try seeing if your custom theme has a file called bp.css perhaps. I found mine in wp-content/themes/custom_theme/css/

@clairem – perhaps the functions.php file of your custom theme needs to be updated to be compatible with the new Buddypress? I’m merely guessing because that is where you make your edits to bring most WP themes compatible with Buddypress. If it’s a premium theme the designer should be able to help you pretty quickly.

If not maybe try posting a screen shot so we can better understand if this is a css issue or something else (if you don’t want to share the URL).

Create a child theme and you can have your cake and eat it too!
https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/

Hi, I’m the creator of the CubePoints Buddypress Integration plugin. I updated my test site to WP 3.2.1 and BuddyPress 1.5 Beta 2.

I moved the admin menu to be under Cubepoints a few versions back so that still works. The items in the BuddyPress Admin menu are still there but when I go to the cubepoints pages on the front end (profile) I get “Page not found”.

This is what I have for the link

$cubepoint_link = ($bp->displayed_user->id ? $bp->displayed_user->domain : $bp->loggedin_user->domain) . $bp->cubepoint->slug . ‘/’;

Based on this I tried this…

$cubepoint_link = bp_get_root_domain() . ‘/’ . $bp->cubepoint->slug . ‘/’;

This is the result:

My Account > Points = http://test.mysite.net/members/xberserker/logs/

Which is correct URL wise but still shows “Page not found”

If I go to

My Account > Points > My Points (anything in the submenu) = http://test.mysite.net/logs/points/

What do I need to do? Here is my file so far. What I changed is line 131

http://pastebin.com/2vJr4U23

Also on my site site I get redirected to my home page when I tried to navigate to the activity streams for myself or the global one. On how the forums work now. If a group is private/hidden are the forum topics only visible to those in the group?

@davidtcarson Thanks for the update, it’s looking awesome – especially the sidebars! Might wanna style the nav drop downs, though (http://i56.tinypic.com/15q53y9.png)

Hi Amanda,

It’s quite simple to fix from inside the theme editor.
Once you have changed the permalink structure to something other than default…

> Appearance > Editor > Header (header.php)

Find ‘

‘,

Underneath is a bunch of coding for the navigation bar. You need to find:

<a href="//” title=””>

And change it to:

<a href="/index.php//” title=””>

Notice all that has changed is ‘/index.php/’.
Do this for all of the navigation links.

It worked for me!

P.s. Note that if the buddypress developers don’t include this change in their next update, these changes will be wiped out. You would have to create a ‘child theme’ to avoid this changes resetting.

Also note, this does not work for the admin bar links.

Tom

I assume you mean the comments and comment form? If so, I can roughly suggest you use the following code:

` `

This will show a comment form and the comments if you have any. However, it all depends on the theme you are using. Would you be able to provide a link to your theme?

I kind of agree with @djpaul. The average user will (or at least should!) have WP_DEBUG disabled, and will (or should!) have error reporting turned off. In that sense, those plugins are in fact compatible with BP 1.5. (To put that another way, if we go by the strict standards, they were never compatible with any version of BP )

I’m not sure if it’s good to fail a plugin purely because it has PHP warnings revealed with WP_DEBUG. Those warnings, if output to HTML rather than a log, can also cause problems with the rest of the plugin. We’re checking for BP 1.5 compatibility, not whether a plugin meets WordPress’ coding standards. Thoughts?

Install https://wordpress.org/extend/plugins/bp-template-pack/ to make WP theme compatible.
https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

@karmatosed thanks for updating https://codex.buddypress.org/releases/1-5-plugin-compatibility/