BuddyPress.org

The ‘welcome message’ they are talking about is a widget that you can place anywhere in your theme that is widget enabled. Sidebars. You can find it under ‘Widgets’ in the backend. Open it up and you can put whatever text you want in there.

Nicola, what is it you are looking for? A personal blog for each user? I think this is a good idea also. Actually I’d like to extend that concept to group blogs also. Blogs need to be more integrated into the bp framework.

Every member needs a blog and every group needs a blog all integrated into the theme like the wire and forums. My next little project, when I get time, will be to create a ‘Group Blog’ plugin that allows a blog admin to configure their blog as a ‘Group Blog’. This will allow instant author/contributor status to specific Groups.

Then I need to modify the member theme to integrate Blogs into it like the Forums are integrated. Not going to have time til after the 1st of the year though.

Mike: if you are gonna mod the adminbar may I suggest this? A plugin that does the work for you without modifying the admin bar code. Andy made some changes to the adminbar to make it possible to replace menu entries easily and add new menu items between existing menu options. I use a plugin to do this. Used to modify it every time a change came thru SVN and got tired of that.

Here’s what I use:

http://pastie.org/344208

That’s a link to the code for a little plugin I use. What that does is it adds a new top level menu item ‘Community’ with the News, Members and all the other items that are available in the home and member themes as buttons.

You’ll need to modify this for your needs but it’s an example of how to add a new top level menu item and all the drop downs. The function oci_get_community_blog_url() goes out and gets some site options I have installed in my root blog theme. I don’t run the home theme on the mu root blog. I run it on community.ourcommoninterest.org. That menu gives access to the ‘community’ directories and recent activity. All the bp home theme stuff.

More on the adminbar in this ticket: https://trac.buddypress.org/ticket/174

What a great idea. Never thought of that. That message about ‘you have no friends’ (something like that) is kinda bleak. We could have the system send them a ‘friendship request’ from admin. That way they learn a little about the adminbar and the member theme right away. That glaring (1) next to notifications would be hard to resist. Click Me.

Mike, I just looked at your buglenotes.com theme and it looks really good!

I’ll probably be chiming in on this soon enough. I’m working on a messaging issue then I’m planning on moving on to some theme tweaks.

Awesome, Trent…simple and quick! I had wondered about this, as I want more sign-ups for my site and thought this might would work…

I used “/wp-signup.php?redirect_to=” so people would more than likely sign-up.

thanks!

I see what’s happening. The directories (member,group and blog) all have their own css files. When you access a directory it loads your theme css and then it loads the directory css. You’d have to ask Andy for sure but my guess would be that the reason is that the directories can be launched from any theme. Not just the bp themes.

If I’m running the bp home theme on a blog. The bp home theme loads the bp home theme css. If I’m running a normal wp theme on a blog then that theme loads it’s css.

The directories don’t know or care what theme they are running in. They have to be able to run in any theme.

I’d post in trac and ask for a mod that loads the directory css as part of the standard style.css/loader.php sequence. Everything else is getting loaded except that. Then your custom.css stuff will override the directory css.

People that are running a theme other than the bp themes will have to seek a different solution.

Ah!!! I didn’t know there was css in there.

Burt, I can’t speak for Mike, but as for me…

I am skinning buddypress-home and buddypress-member themes, by using the custom.css in each themes’ css folder. Neither of which affect that alphabet.

Thanks

This is the members directory you are talking about? The css for that is in:

/wp-content/mu-plugins/bp-core/css/directory-members.css

Exactly what are you two doing? Creating a new home or member theme skin or skinning the css so that it works within a standard wp theme?

I’m confused. We got 2 themes to work with here. The members theme and the home theme. Both have the ability to be skinned through the use of a custom.css file that overrides all css in bp for that theme. That theme only.

Each theme has a seperate custom.css file. One in the member theme area and one in the home theme area.

Everyone agree on that? This is what we’re working with right? Which theme are you two working on?

Well, you can look at this post for a quick hack to only allow members to see anything on member profiles, groups, etc. That post has a hack that applies to the /wp-content/member-themes/buddypress-member/ theme. The buddypress-home theme in /wp-content/themes/buddypress-home/ doesn’t get the hack

You could apply it to buddypress-home theme in certain places if you don’t even want them to be able to search the blogs, groups, members, etc. but that would be a little harder to follow.

Then, on private blogs, I just use more privacy options so that private and no search engine blogs don’t show in any listings around the site. You can hack the code to actually list them in buddypress if you want, but default pattern is to not show them.

So basically, I would set the privacy for all blogs you don’t want showing and leave the main blog open. It is done with that plugin on a blog by blog basis.

Once Andy puts more of this into the core, it will be much easier, but for now we have to “hack” around a bit

Trent

Any css you put in custom.css overrides *all* css. Unless groups css is being loaded after custom.css and in that case it’s a bug and should be reported in trac. Don’t think it is though.

Example:

ul#group-list li, ul#member-list li, ul#blog-list li, ul#comment-list li, ul.item-list li { background: url(../images/message_thread_back.gif) top left repeat-x;}

That’s in ../member-themes/buddypress-member/css/groups.css. In your custom.css file you can change the ‘message_thread_back.gif’ to something else by overriding it in custom.css

ul#group-list li, ul#member-list li, ul#blog-list li, ul#comment-list li, ul.item-list li { background: url(../images/my_fav_message_thread_back.gif) top left repeat-x;}

This what you need?

now the best way is editing your css and your members-theme. But if you’re good in php and html, you could include bp in your theme

If you’re using the buddypress theme you could add as left-coloumn widget, the activities’ widget. Simpler than that!

I have a similar issue, but I am not using the home theme so it is to be expected.

MU Version 2.7-RC1-10145

BP 1.0b1

Is there anyway to integrate these directories (news/members/groups/blogs) into a custom home theme?

From the member theme, I’d like users to be able to access the directories. But, as of now, clicking on ‘news’ results in 404 and clicking on ‘members/groups/blogs’ shows initial listings without any functionality.

I should probably focus on customizing the BP home theme to look and act more like my custom theme. But if there is a reasonable fix to integrating the directories into my custom theme, I’d be grateful to be pointed in the right direction.

What versions of mu, bp are you using?

Is this from the home theme?

Is this from the member theme?

I prob have mult posts up there. bbpress flaking out this morn.

You seem to have mu configuration problems. None of your subdomains can be reached. It’s best to get mu setup, configured and working properly before installing bp. Test mu blog creation and reachability, create and edit posts, make comments. Get comfortable with mu first.

It will make installing and configuring bp a whole lot easier. I played with mu for a month before I felt comfortable with it.

What type of host are you on? Shared, DV? Looks like you need to do some DNS tweaking for your subdomains to work.