BuddyPress.org

No biggie for the IE6 display:none bug. I changed it per @hnla‘s suggestion.

@djpaul an issue: when creating a menu link thats not a page just a straight url link to say /activity it doesn’t add the class to make the tab look selected.

check it by clicking activity and then another tab http://tempsg.com/

The navigation menu is in the header.php starting here https://trac.buddypress.org/browser/tags/1.2.5.2/bp-themes/bp-default/header.php#L46
You can change the links by creating a Child Theme so your revisions won’t be overwritten when BP is upgraded.
You won’t find the BP menus in the Appearance > Menu unless you revise the links in navigation menu an code navigation menus function in your theme’s functions.php file and add the template tag for that in header.php – https://codex.wordpress.org/Navigation_Menus
You can also try out this plugin – https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/home/

Alright, concrete feedback now that I’ve played with your features.
1) Header image is too small. I would like options to have a larger image. I like 275 px
2) Remove the search from the header. I’d like options to remove that. It’s unneeded for my site.
3) Title. It’s currently behind the gray bar for the buddypress. Move it down?

Now, I’m just learning PHP, been using HTML for years. New to WordPress in last year. Can I make the above changes somehow in the style.php? I hate to make changes and break it.

I like that it uses the custom menus, so much of my information needs to be accessed in it’s categories.

Thanx for the hard work!

@skolbloggense: BP-Slick uses the same BuddyPress translation strings so the theme should just work fine with your Translation. The only thing that is not yet translated is the menu navigation. But that can all be found in one file, which is organized and very easy to edit. I think it will take you about 10 mins to translate it!

I will add po/mo files to the theme pretty soon (to make upgrading easier, so you won’t lose changes) but right now it’s yet added The Theme is now for sale btw.. It can be purchased with 20% discount until the end of the week: http://bp-tricks.com/purchase-bp-slick/.

Here’s the sales page with it’s features: http://bp-tricks.com/pre-order-bp-slick/. And a short video on how to get it running: http://www.youtube.com/watch?v=gMb7tXXV6Rw&feature=player_embedded

I’m going to try and add the steps for the fix again. I didn’t see the note about using backticks for code…

1. Open the index.php, save it to your theme as posts-page.php (or whatever template name you like).
2. Edit the newly created posts-page.php file and place the following at the top to create a page template:

`<?php
/*
Template Name: Posts Page
*/
?> `

3. Now scroll down in the posts-page.php to the beginning of the WordPress loop and just before the line “ add this one line of code “ Note: (5 == the number of post to show you can change this to whatever you want.)
4. Save the posts-page.php file.
5. In your WordPress/BuddyPress admin panel create a new page called “Blog” (or something similar) and select “Posts Page” under Template.
6. Publish page.

You should now be able to go to your Settings -> Reading menu and set a static page and select your Posts Page to show your blog posts.

This site uses a customised version of the current “trunk” code, which adds support to BuddyPress to integrate into WordPress’ pages system/menus properly.

just to add to this discussion, concerning what hook to link it to…this is what works for me. i didnt have luck with bp_setup_nav for some reason. i dont recall where i got this example, but think its bp-xprofile.php itself. this worked in both theme>functions.php and in my own mmc_functions.php which i “require()” in functions.php

just to add a hint of background, we are moving these two items to the ‘settings’ tab from the profile tab. the removing is trivial, the adding is trivial, the getting all the right functions/themes/forms called, not so much. but its done and it works.

here is the code for removing sub-tabs — aka options:

`
//removes in a structural way.. no change to bp-xprofile.php

function mmc_bpsetupnav_removefromprofile(){
global $bp;

if ( $bp->current_component == $bp->profile->slug ) {
bp_core_remove_subnav_item($bp->profile->slug, ‘edit’);
bp_core_remove_subnav_item($bp->profile->slug, ‘change-avatar’);

}//end if
}//end function
add_action( ‘wp’, ‘mmc_bpsetupnav_removefromprofile’, 2 );
`

here is my code for adding them to the settings tab

`
////////////////////////////////////////////////////////////
////// functions for moving to Settings tab the editprofile/change avatar sub-tabs

function mmc_bpsetupnav_forsettings(){
global $bp;

if ( $bp->current_component == $bp->settings->slug ) {
//define ( ‘BP_XPROFILE_SLUG’, ‘settings’ );//didnt have desirable effects. left her for documentation

//this is essentially a clone of xprofile-settings.php, but with tweaks to change BP_XPROFILE_SLUG references tp BP_SETTINGS_SLUG
//that way didnt change any core files, and moved it out of the upgrade stream
require_once( WP_PLUGIN_DIR.’/mmc_misc/functions_xprof_settings_mmc.php’);

$profile_link = $bp->loggedin_user->domain . $bp->profile->slug . ‘/’;
$settings_link = $bp->loggedin_user->domain . $bp->settings->slug . ‘/’;

//EDIT PROFILE
bp_core_new_subnav_item( array(
‘name’ => __( ‘Edit Profile’, ‘buddypress’ ),
‘slug’ => ‘edit’,
‘parent_url’ => $settings_link,
//’parent_slug’ => $bp->profile->slug, //left for documentation
‘parent_slug’ => $bp->settings->slug,
‘screen_function’ => ‘xprofile_screen_edit_profile_mmc’,
‘position’ => 50, //magic number based on current items already there in SETTINGS tab
‘user_has_access’ => bp_is_my_profile() //ADDED, NOT IN ORIGINAL WHEN IN BP-XPROFILE.PHP
) );

//CHANGE AVATAR
bp_core_new_subnav_item( array(
‘name’ => __( ‘Change Avatar’, ‘buddypress’ ),
‘slug’ => ‘change-avatar’,
‘parent_url’ => $settings_link,
//’parent_slug’ => $bp->profile->slug, //left for documentation
‘parent_slug’ => $bp->settings->slug,
‘screen_function’ => ‘xprofile_screen_change_avatar_mmc’,
‘position’ => 60, //magic number based on current items already there in SETTINGS tab
‘user_has_access’ => bp_is_my_profile() //ADDED, NOT IN ORIGINAL WHEN IN BP-XPROFILE.PHP
) );

}//end if

}//end function
add_action( ‘wp’, ‘mmc_bpsetupnav_forsettings’, 2 );
add_action( ‘admin_menu’, ‘mmc_bpsetupnav_forsettings’, 2 );
`

note the TWO add-actions at the end. also taken from example at bp-xprofile.php. why this and not bp_setup_nav.. i dont know!

ggod luck
mario

https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/

@helverk

You wrote: But what I am ever going to do with it? in reference to your .htaccess file

You don’t do anything with the file the server does. The server must be able to write to the file to make any changes required automatically.

Have you tried going to the permalinks menu in the dashboard and set it to anything other than default, just change to day/month and save and tell us what the screen says , if there are any messages about not being able to write to the file or whether it simply kicks things into life.

I also note that your base is not ‘/’ root but ‘/wordpress/’ which may not help matters I presume you simply installed into the MAMP? web sites directory, it would be worth reading up on how to configure vhost containers and simple host file dev domains so you can run a site as a make believe top level domain.

I found this fix and it appears to be working for me:

1. Open the index.php, save it to your theme as posts-page.php (or whatever template name you like).
2. Edit the newly created posts-page.php file and place the following at the top to create a page template:

`<?php
/*
Template Name: Posts Page
*/
?> `

3. Now scroll down in the posts-page.php to the beginning of the WordPress loop and just before the line “ add this one line of code “ Note: (5 == the number of post to show you can change this to whatever you want.)
4. Save the posts-page.php file.
5. In your WordPress/BuddyPress admin panel create a new page called “Blog” (or something similar) and select “Posts Page” under Template.
6. Publish page.

You should now be able to go to your Settings -> Reading menu and set a static page and select your Posts Page to show your blog posts.

Ok, I found one hint in Buddypress German Forum of WordPress, see http://forum.wordpress-deutschland.org/buddypress/73994-seite-nicht-gefunden-members-usw.html

I post there a solution for the normal menu. The ‘index.php’ file is missing in the permanent structure, maybe there is something different between the WP English and WP German version of 3.0.1. So all of you have the URL http://www.yourdomain.com/groups/. Please change it in your Browser to http://www.yourdomain.com/index.php/groups/ and check if you’ll get a page. Change ‘yourdomain.com’ in your real domain. See my page http://www.unitedcasting.de/index.php/groups/ – it works.

But now I’ve to search for the links under ‘MyAccount’ and ‘Notifications’. Maybe someone knows where the file is safed. Thanks.

@hnla

Wow, you really took this little project to heart, didn’t you? Thanks for investing so much time on it!

1. Didn’t realize the ul elements could cause problems but it works just fine without them (tested successfully on bp-default and child theme).

2. By wrapping wp_list_pages in ul elements, all pages aggregate under a top-level “Pages” nav item, with actual WP pages as subnav items and child pages as sub-subnavs as example below:

“Pages”
– Page 1 – – Page 1 child 1 – – Page 1 grandchild 1
– – – – – – – – – – – – – – – – – – – – – Page 1 grandchild 2
– – – – – – – – Page 1 child 2
– Page 2

By removing the “Pages” li element and wrapping the call to wp_list_pages in li elements, WP pages appear as top level, with child pages as subnavs. Creating a new page adds it to the nav as a top-level item, unless excluded (either entering the page ID manually in the code, or with “Exclude Pages” plugin). I prefer it this way, but the modified code could be included as an option in the plugin for those who prefer having all pages listed under a common heading, with instructions on where to change the heading label.

3. I get no errors with the new WP3.0 checks in place. I couldn’t figure out how to do that, but I see it was a rather simple if !function_exists call. Huh…

4. I left the top link name “Pages” in the wp_nav_menu calls for now. I have not tested this code on WP3.0 so don’t know if the menus will behave as in 2.9.2

I ran the code with modifications, both yours and mine, and it works brilliantly. Collaboration is a wonderful thing

Here’s my revision: http://pastebin.com/4U85PWrt

No word yet from WP about my plugin submission… still waiting. Got to get to work now, thanks again!

@pcwriter

I’ve had to do a fairly extensive rewrite on the function for a number of reasons:

1/ There was a significant degree of malfomed ul child nesting which prevents drop down aspects working correctly primarily I’ve removed the opening and closing UL elements as they are not required and cause issues.

2/ Not sure how the wp_list_pages was intended to work but with the parameter ‘title_li’ declared as empty you correctly remove the wrapping elements but would need to add UL elements manually wrapping the function call for the dropdown to function correctly.

3/ Added back in the wp_nav_menu function calls but wrapped them in a check to see if WP 3.0 is running i.e are the new menu available if not hide altogether.

Also added a reverse check to remove the wp_list_pages function if using the new menus as there is little point in both and the new menu system serves better.

4/ Changed region and menu top link names to ‘pages’ but this area is a fundamental issue as it cant be known what the user sets as menu names, ideally one shouldn’t hard code values but retrieve them from the admin menu area, but this proves far too hard to work out (asked a question on WP support but haven’t had a reply and I don’t expect one – sadly there is little codex documentation of any depth on the new menus.)

This issue applies to the wp_list_pages as well as you can’t really pass any values for ‘include’ and ‘exclude’ as these values can’t be known so you ought to remove those values you have hardcoded (I have left them in).

If I can get some guidance on how to fetch values from the menu backend view such as menu names then it will be possible to make the menus far more effective but have spent quite a while trawling through the core WP files for nav-menu and it’s not obvious and too time consuming.

I have copied the revised code to this pastebin page, give it a check over, but don’t assume I have things all correct, run it as plugin copy 2

http://pastebin.com/trUDaPEP

@justbishop Are you saying it might be possible to write something like

a href= members/bp_displayed_user_username()/profile/change-avatar

edit/ tooo slow

This will tell you how to change url slugs
https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/

Menu items/text can be changed by adjusting the link in header.php _e( ‘Groups’, ‘buddypress’ ) preferably via a copy of the file in a child theme.

BP-Default does work with WP 3.0; what exactly are you referring to, custom menu support? The theme will not see any significant changes until BuddyPress 1.3, which won’t be out for a while yet. The theme lives in /plugins/buddypress/bp-themes/bp-default/.

For version 0.1.9 nightly builds, the option is located in BP Album -> Plugin Settings -> Page Slugs -> Base Slug

Change it. Click save. Done.

Thanks!

^F^