BuddyPress.org

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^

I think BP Album+ has a language file. Can’t you just change the language file and it will change it everywhere? I should also note that in future versions there planning to add videos and other media. So, that’s probably why they used media instead of photos or something.

sorry @denisjanis, I didn’t see your reply. Look like you figured out overwriting the files with 1.2.41 works.

@Johnjamesjacoby, you’re right, I’m using a child theme. The default buddypress theme works fine.

I have the bp-follower plugin installed and using buddypress 1.25 breaks it. The menu items are still there but any notifications in the top menu bar getting clicked results in the redirect to homepage problem. It doesn’t happen with the default buddypress theme.

with buddypress 1.25 and my child theme, I can view domain.com/members/ no problem but trying anything after that wont, domain.com/members/andy/ wont work or domain.com/members/andy/followers

I tried adding a die(‘some message’) in the child themes /members/single/activity.php file but it didn’t have an effect, I tried in various other files and still couldn’t get it to die with my message showing so maybe it’s a redirect or rewrite rule that has changed in 1.25 that isn’t compatible with a command in the child theme?

I will continue to use 1.241 for now but it would be nice to get to the bottom of it.

– topic tracking – favorite topics – some way to bucket open forum topics or add a topics menu item to my profile page with a listing of all my topics AND make that the default landing not the activity
– self forum activity search, “i remember saying something about XYZ, let me search my own activity” from my profile
– deactivate post update only’s, new group follows, in main activity stream – maybe even remove activity component all together.
– group landing pages should default on the forums not /home with the activity stream.

Edit your theme’s style.css.

And add the following:
#wp-admin-bar .padder, #wp-admin-bar ul li ul {background:red !important;}

This is just to get you started.

Again, I advise you to create a child theme to apply your new style changes. Read this guide to build a child theme from the default BP theme:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

First, you’ll need to know a little bit about CSS to override the color scheme in the default BP theme.

Secondly, you’ll need to create a child theme to apply your new CSS changes. Read this guide to build a child theme from the default BP theme:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

Next version will probably not include drop down menus in the theme, perhaps in BP 1.3 to take advantage of the new WP custom menus. For now, you’ll have to add this yourself by customizing the theme and applying a little jQuery trickery.

There are a ton of tutorials on jQuery drop down menus out there; you should be able to find one that fits your needs.

If you have no experience customizing themes, you might find this a little daunting!

Not sure what to tel you about the theme issues you’re having (I just modified the BP default one), but I get what you mean about the BP groups/forums confusion.

The audience I’m after is used to vbulletin forums, so I actually found some code posted here on BP.org that made groups open onto the group forum by default, and then I put a conditional around the activity stream posting thing on the group activity pages that only allows admins to see/use that. This way, all group activity id funneled into the forums, unless the group admin just feels the need to post something to the activity stream. I also just did away with the ability to post activity stream updates from the sitewide stream page, but you could just modify the ‘post update to’ dropdown menu there to hide and make it post to the user’s profile only.

All in all, I’ve found that Buddypress can be a bit of work if you want to change the way it does certain things, but for most people the features are worth the trade-off of some extra work. I hope you get it all figured out and working the way you’d like

@pjnu it’s a simple edit plus a few additional steps once the menu items have been activated for the dashboard by the config change. If you already have a WPMU setup WP 3.0 detects that and you shouldn’t have to go through the MS setup procedure.

@jon, try this in your child theme’s css:

#wp-admin-bar {
top:inherit;
bottom:0;
}

you still have to change the drop down menu to rise up though. But it is a start….
Cheers
Meini

Mainly to allow BuddyPress pages to be put into custom menus and hierarchies like you can do with regular WordPress pages or posts. The change will be invisibile unless you want to set up your site like this, then it will be easy. This site does not run BuddyPress 1.3, it’s too early for that, though I suppose it is possible the code has been backported.

@apeatling Would you answer this /communities/ URL question once and for all please? Thanks.

Change the URL slugs of BuddyPress components: – https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/
Plus to reflect URL in Menu go change the names of respective navigation list within header.php of bp-default theme

@kankakee
I’ve altered fishbook to get active header tabs to change for static pages. you need to edit the styles.css file like this:

find the nav css. look for the line that says “ul#nav li.selected a {” and change it to “ul#nav li.selected a, ul#nav li.current_page_item a {“

done!

Regards
Ade