BuddyPress.org

@dimensionmedia,

I’m sorry. So, i think that you don’t need add files in /member-theme/ because you can write your plugin without adding files in /member-theme/ for example you can write:

function test_page_settings() {

global $current_user, $bp_settings_updated, $pass_error;

add_action( 'bp_template_title', 'test_page_title' );

add_action( 'bp_template_content', 'test_page_content' );

add_action( 'bp_template_content_header', 'test_page_tabs' );

bp_catch_uri('plugin-template');

}

function test_page_title() {

_e( 'Hello title', 'buddypress' );

}

function test_page_content() {

global $bp, $current_user, $bp_settings_updated, $pass_error; ?>

<p>Hello Content</p>

<?php



function test_page_tabs() {

global $bp, $create_group_step, $completed_to_step;

?>

<ul class="content-header-nav">

<li>Hello Tabs</li>

</ul>

<?php } ?>

With that you don’t need to add page in /member-theme/. I think that users that install a plugins want only add files on mu-plugins/.

Think if i’ve another member-theme that isn’t like the default, and i would like add this plugin..

I hope i explain well now

I think that you don’t need using page to add in your member theme :S look plugin-template.php

There is only an option to turn off the adminbar for logged out users. Yes/No for them. Otherwise it’s Yes for everywhere in mu. The adminbar gets generated at every page load in mu. You could disable it completely by default someplace in code and then in the pages that you want it to appear on, enable it before the wp_head() call that your theme makes in header.php

bp registers its need for attention by the calls:

add_action( ‘wp_footer’, ‘bp_core_admin_bar’ );

add_action( ‘wp_head’, ‘bp_core_add_css’ );

You could un-register these calls someplace like functions.php in your theme to turn off the adminbar globally:

remove_action( ‘wp_footer’, ‘bp_core_admin_bar’ );

remove_action( ‘wp_head’, ‘bp_core_add_css’ );

Then in your theme, on the specific pages you want to show the adminbar register the adminbar again before the call to wp_head():

add_action( ‘wp_footer’, ‘bp_core_admin_bar’ );

add_action( ‘wp_head’, ‘bp_core_add_css’ );

In your theme you’ll have to add some logic in header.php to detect what page is being displayed and make the event registration calls.

So, in functions.php un-register the calls and in header.php before wp_head() re-register them. They’ll get turned off again when functions.php loads the next time and the sequence starts again.

The bp home theme is really just a widget framework. You can install any widget you like in that theme. You can modify the standard ‘activity’ and ‘recent blog posts’ widgets. You can install a plugin that aggregates feeds from specific blogs. Your requirements are pretty specific so you have to decide if you are going to develop custom code or try to utilize some off the shelf plugins.

To answer your question. No there isn’t a mechanism in place that allows you to be selective in the posts that show up using the ‘sitewide activity’ or ‘recent blog posts’ widgets.

Have fun. (but don’t tell anyone we are though)

The bp home theme is really just a widget framework. You can install any widget you like in that theme. You can modify the standard ‘activity’ and ‘recent blog posts’ widgets. You can install a plugin that aggregates feeds from specific blogs. Your requirements are pretty specific so you have to decide if you are going to develop custom code or try to utilize some off the shelf plugins.

To answer your question. No there isn’t a mechanism in place that allows you to be selective in the posts that show up using the ‘sitewide activity’ or ‘recent blog posts’ widgets.

Have fun.

Howdy. You can modify the member theme’s target for successful login in the /member-themes/buddypress-theme/header.php file. Lines 53 and 55. It redirects people to site_url() you can send them where you’d like by replacing that with your destination.

If your user elects to login via the buddybar you can edit the file /mu-plugins/bp-core/bp-core-adminbar.php in the function bp_adminbar_login_menu() at line 33. Another similar line where they get redirected to ‘siteurl’.

zanzoon, dimensionmedia is right in asking what exactly are you referring to? The site linked in your profile looks fine and seems to be operating fine. That error is on what page? What theme are trying to access it on as the 2 default themes seem to be working fine. As well, in your admin the URL to access the xprofile fields is like this:

/wp-admin/wpmu-admin.php?page=xprofile_settings

Are you trying to access the URL directory or something?

David,

“…minimum required to give you the ability to add a new menu item…”

You talking about adding a new menu item to the buddybar ™ or to the user/options bar in the member theme?

what account settings? backend or settings on profile theme?

dimensionmedia

This may not be possible, but it might be nice to include users of Identi.ca (and Laconica servers) plus Openmicroblogger.org servers in this stream. Both use the OpenMicroBlogging protocol enabling users to post to Twitter and subscribe to friends on each platform.

Openmicroblogger.org in particular is heavily tied to WordPress plugins and themes already.

Cheers

Let’s take these things one at a time.

“well no search works not even groups or anything” You are going to have to explain that in more detail please. That’s not enough to even know what the problem is or where it’s located. Try something like “Using the home theme, when I go to the search box labeled ‘find blogs’ and enter in part of a blog title it doesn’t show the blog I’m looking for.”

Start with the problems you are having using search. Give me some details.

Howdy. The plugin-template.php is used when you are running a non-bp home theme. As far as I can see it’s the only time it’s ever used. The plugin-template.php calls get_header(), triggers an action ‘bp_template_content’ and then calls get_footer(). Whatever is triggered by the ‘bp_template_content’ event, renders the stuff in between the header and the footer. The content div with the groups directory stuff inside it in the case you mentioned.

If you are getting two content divs then your theme is starting a content div in it’s header.php file. Gotta be. That should be left to the rest of the theme’s template files.

Am I understanding what you are saying?

Mike, the blogs component is about creating and tracking the blogs that each user creates. If you don’t want your users to create blogs then don’t install the blogs component. All references to blogs should just vanish. From the admin bar, from the home theme and from the member theme.

That and disabling blog creation in the mu back end should take care of it. Am I missing something? Won’t be the first time..

I think I understand the question now. Takes me awhile sometimes.

When you install mu you are installing a multi-user blog community. People register and create their own blogs. As the Site Admin of this vast and wonderful new community, you get to oversee the chaos. Each and every new user in your Infini community is a blog admin and they get to choose the blog theme. The way it looks is up to them. There is a light at the end of the tunnel for you. You control what themes are available for them to choose from. (I know don’t end sentences with a preposition)

Any themes *you* install and enable are there for selection by your new blog admin/owners.

EDIT: Stop here Burt and read the question again. You are going on about something unrelated to what the question is.

So, like I wasn’t saying above, yes you can have all users in your mu community running the bp home theme. I had never considered doing that though. Hmmm. Yep, it’ll work. It can’t think of any negative side effects at the moment. You just need to have the blog owners choose that as a theme.

‘Site Policy #17a’ : Thou shalt run the bp home theme.

YETANOTHEREDIT: (sigh) There’s an easier way you moron. Get a clue Burt.

The default mu theme is the default mu theme for new blogs. That’s why they call it the default.

I remember playing with the ‘default’ directory under /wp-content/themes. I wiped it and put a different theme in there. The only problem I remember having was mu got confused a bit by two themes registering as ‘theme x’. I deleted the copy of the theme that was laying around under /themes and mu seemed happier. It fired up my selection of tarski being the default theme. I didn’t find any toggles or switches to flip in mu, I just stuffed what I wanted into the ‘default’ directory and went on with life.

EDIT AGAIN: Maybe you should refer them to advice from someone who has slept in the past 24hrs.

Is that what you are talking about?

Which ‘toolbar’ are you talking about. We have three that might be the one you are talking about. We have the ‘member adminbar’ which has ‘my account’ ‘my blogs’…, the member and home theme ‘button bar’ which have ‘news’, ‘groups’…

In all cases you have to modify the code or develop a plugin to make additions or modifications.

gpo1, nope. I’ve got too much on my plate right now. I’m not going to be able to do much else except get a site launched by the 1/1/09 deadline.

I talked to Andy about enabling bp to use standard wp widgets in the member theme. Got a couple of ideas but no time at the moment to play with them. The problem is that mu deals with *one* theme per blog. The members theme is sort of this invisible theme that lurks in the background. mu doesn’t even know about it. Only bp knows about it. It *is* bp.

The way I understand that widgets work is:

Register a ‘sidebar’ in mu with a name. 1,2,3 or ‘BP Member Profile’, ‘BP Member Blogs’. The sidebar gets registered to a specific blog id.

register_sidebar(array('name'=>'Main Sidebar',

'before_title' => "<h3 class='widgettitle'>",

'after_title' => "</h3>n",

));

In theme code call mu’s sidebar launcher fn.

<?php if (!function_exists('dynamic_sidebar') || !dynamic_sidebar('Main Sidebar') ) : // begin primary sidebar widgets ?>

I just had some questions that I didn’t have time to investigate. When can I call call register_sidebar()? Any time I want, anywhere I want? I see it done in theme functions.php.

When I access any bp member theme functions do they execute in the blog id 1 environment? I think so.

If I register some bp member theme sidebars in bp code will it show up in the mu backend? I think so.

Seems like only the site admin who owns blog id 1 will be able to add widgets to the member theme. Well that’s a *good* thing. This is a feature.

Lots of questions and unknowns right now and not much time to explore answers. Have at it! Have fun.

Wouldn’t it be as simple as having the plugin in mu-plugins and then just adding the call to your member theme just like any other theme?

#1-#2 Something is amiss. Should be working. Both the alphabet and search work on my installation. Try reinstalling the bp files, including themes. Save your changes beforehand! Do you have other plugins installed that could be interfering?

#3 probably related to above

Sorry I can’t help more…

Are you using your own theme or the buddypress-home theme?

is this for the members theme page?

i hope so!