[@burtadsit Participant 17 years, 10 months ago]

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)

[@burtadsit Participant 17 years, 10 months ago]

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.

[@burtadsit Participant 17 years, 10 months ago]

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

[@burtadsit Participant 17 years, 10 months ago]

Oooh Nicola. It’s not good to push ‘send’ without thinking. There are always consequences for our actions. We’ll just have to come up with an appropriate punishment for your thoughtless behavior.

In the meantime I moved it.

[@burtadsit Participant 17 years, 10 months ago]

It’s good enough if it meets your needs and you trust running beta software on a production server. Good enough can only be defined by you.

[@burtadsit Participant 17 years, 10 months ago]

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?

[@burtadsit Participant 17 years, 10 months ago]

Me again. If you are using the latest SVN then there is a bug in blog search. I reported it in Trac. Wait a couple of revs for that particular thing to filter down.

So what else can we work on?

[@burtadsit Participant 17 years, 10 months ago]

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.

[@burtadsit Participant 17 years, 10 months ago]

Let me see if I have this straight. You installed a normal wp widget called ‘user list’ that lists the users on a blog and it’s supposed to show the wp profile for a user when clicked.

The widget knows nothing about bp. The bp profile is part of bp. The widget would have to be created specifically for bp to view bp member profiles.

[@burtadsit Participant 17 years, 10 months ago]

You have to put basic profile info into your members for search to work. It doesn’t use the ‘login name’. Try plugging in some Full Names. Same for letter lookup.

[@burtadsit Participant 17 years, 10 months ago]

Howdy.

$bp['loggedin_userid']

Or something else from here : /mu-plugins/bp-core.php

Never leave home without your globals. Don’t forget to declare your intentions inside of a function:

function myhandydandyfunction () {

global $bp; (Andy reminded us of that recently)

[@burtadsit Participant 17 years, 10 months ago]

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?

[@burtadsit Participant 17 years, 10 months ago]

Hey Trent. Ya, I found this plugin a while a go and loved it too. When I found it, I was using 2.6.2 and the backend was miserable. Took 10 min go get where I needed to go. Vipers admin bar helped. I was running the 2.6 backend using Vipers bar and the front was the bp bar.

Now the backend of mu is better in 2.7 and I see little reason to use the Viper bar there. The Viper bar is now part of mu. Just a switch flip away from any site admin on the planet. You and I both know what that means. Site admins are gonna want to be able to have the functionality of both on the front end as options to their bp community members.

When mu 2.7 gets out of trunk, bp site admins are going to see stock mu sites running the Viper bar.

(aside) I don’t know who Viper007Bond actually is but he’s gonna be famous for his ‘Viper Bar’. We can make that happen ya know. Just keep calling it the VIPER BAR! Everywhere. Kinda catchy isn’t it? I just can’t stay out of trouble.

What was I saying? Oh, I agree that the utility of the VIPER BAR! is what I was looking for when I talked about integration. I want the same goodies to be available in the bp bar.

(here we go again.. aside) We gotta think of a better term than ‘the bp adminbar’ for the bp adminbar. Speaking as a sometime, solely out of desperation, marketing weasel, ‘bp adminbar’ sucks. buddybar. I kinda like buddybar. ‘Course I haven’t slept in 26hrs. That may be why I like it. No I haven’t been drinking.

I want the blogging goodies as well as the social goodies.

[@burtadsit Participant 17 years, 10 months ago]

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

[@burtadsit Participant 17 years, 10 months ago]

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?

[@burtadsit Participant 17 years, 10 months ago]

@danielfelice

If you are running the beta then ‘news’ works. It’s probably an mu or apache config problem like chinian had.

[@burtadsit Participant 17 years, 10 months ago]

@rwallen

lol! Ya, really (sigh).

[@burtadsit Participant 17 years, 10 months ago]

These are your programming problems or your mu configuration problems not related to bp. Try the mu forums.

https://mu.wordpress.org/forums/

Posting massive error logs to a forum doesn’t help. It just annoys the people who might have helped.

If you had started out giving an overview of your problem and how it relates to bp, you may get better results next time.

[@burtadsit Participant 17 years, 10 months ago]

pinark I don’t see any problems with long posts on your site wide activity (you don’t have it turned on) and recent posts works like advertised. It gives the excerpt of the first post and then titles to the rest.

What’s the problem?

[@burtadsit Participant 17 years, 10 months ago]

You do not have mu setup and configured correctly. Until you do nobody will be paying any attention to your other problems. They are probably all related to the fact that mu is not working. Get mu working and then install bp. Please see the mu forums for help installing, configuring mu.

https://mu.wordpress.org/forums/

[@burtadsit Participant 17 years, 10 months ago]

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.

[@burtadsit Participant 17 years, 10 months ago]

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.

[@burtadsit Participant 17 years, 10 months ago]

There currently isn’t a way to change group avatars once created. That feature is set for the 1.0 release of bp. You’ll have to wait until then , edit the path directly with phpmyadmin or delete the groups and re-create them.

Sorry.

[@burtadsit Participant 17 years, 10 months ago]

I’ve posted a fix in trac. If you feel comfortable changing core code until the fix comes through SVN or the next beta then you can modify this file:

/mu-plugins/bp-groups.php in function groups_get_avatar_hrefs() line number 1152 now reads:

$src = $bp;

change it to:

$src = trailingslashit($bp);

Fixes the upload group avatar when logging into a subdomain problem.

[@burtadsit Participant 17 years, 10 months ago]

You have a directory called ‘blogs’ under your document root. It gets priority when apache goes out looking for stuff. Rename it and see what happens.