BuddyPress.org

Try this yet?
Show Excerpts
Except instead of copying over and editing the site’s main index.php, make sure you find the right file for your theme (in bp-default, that’d be the index.php file in the blogs directory–probably the same for BP Widget Theme, but I haven’t looked at it).

You can try by adding “DirectoryIndex” by way of modifying the HTACCESS file.

The way I did it was I added the line:

DirectoryIndex my-main-landing-page-on-my-home-page.html

this tells your webserver to use that file as the main “index” instead of the “index.php”

it seems to work well as “maintenance page” while keeping all of the functionality of buddypress intact (blogs, members, sign ins, etc) still seem to function.

@chopo87

It was actually me that fixed the template error. Granted I didn’t know why, see below:-

https://wordpress.org/support/topic/plugin-bp-member-filter-cant-get-this-to-work

@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

@pisanojm ‘s suggestion is probably best. And yes, Gravatar.com is owned by Automattic.

Just create a language file and change all the references to group: https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/

Same problem. I get a single blog buddypress installation (no wp 3.0 blogs network activated). I don’t see any option to search in blog posts. I don’t find any plugin too ??? Does anyone know where to search for this ?

Hi !

Your idea is great.
Where do you write all those codes ? into functions.php ?
Moreover, I would like to merge all “personal”, “friends”,”groups” and “mentions” in one ? using your method, would it be possible ?
Thanks to help me.

I’m using wordpress 3.0 , buddypress 1.2.5 , and bp-default theme

Side conversation – it is possible to replace the default avatars with something custom? Not Gravatar but our own folder of images from which to randomly apply avatars?

Wait, I’m confused. You want it to show up in their profile, right? So why not just create a profile group and relevant fields?
Although…hmm….that might get tricky in terms of multiple Living/Deceased. Or you just allow a max number of pets (say, 5 in each category) and create that many profile fields. Anything left blank won’t show up in the profile.
That wouldn’t let you upload photos natively, although I wouldn’t be surprised if we already have a plugin for that.
Then again, you also wouldn’t have anything compiling everybody’s tributes. Is that what you want? Have to admit, I’m not super-clear on what you’re looking for.

Hm.. Not my most helpful reply, sorry.

Another thought: maybe you can mix a form you create with one of the front-end blog post plugins. So whatever interface they’d normally have to post an entry to the blog (your listing of everybody’s tributes) would be heavily locked down to just the info you want. I’m thinking BuddyPress would automatically include a link to the generated tribute post somewhere in their activity feed. (I know you said you don’t want a blog type page, but here I’m assuming you meant that you didn’t want the submission page to be part of a blog, not that you don’t want the submitted tributes to be incorporated in a blog.)

Why not Ping the disqus folks? They might be interested in developing this integration themselves…. it makes sense.

If you didn’t back up your files, check with your host. Some (like GoDaddy) do automatic backups periodically, so you might be able to recover your old files.