BuddyPress.org

Did you try it?

Assuming you’re only using the home theme for your home blog, you shouldn’t have any problem doing a normal query and getting main blog data in the_loop.

I have a question about the loader.php in the css directory.

I followed all steps of the instruction:

https://codex.buddypress.org/getting-started/installing-buddypress/upgrading-from-rc-1/

However my directories were messed up. The styles weren’t applied. I figured out that it has something to do with the loader.php in the css directory.

My question is if it is possible to just copy the RC2 /css/loader.php in my customn theme /css/ folder? I’m afraid, cuz the new loader.php is much smaller with significant less file imports (where are the imports for e.g. grups.css / blogs.css /friends.css / wire.css)?

This will pretty much allow for unlimited access to any BuddyPress data from any other part of your site in a very straight forward and easy way.

Outstanding work and great write-ups too!

I’m having the same problem. I just installed BuddyPress 1.0rc2 today, and it’s the first WPMU install for me, and obviously the first BP install as well. I’ve been running WP for over 2 years though, on the same server (different domain), with complete success.

The install seemed to go fine, and I followed the instructions to also use the BP-home theme for the WPMU home page as well (it fails with any of the 4 choices of home page themes).

The site comes up correctly in IE7. In Firefox (3.0.10) and Chrome (2.0.174.0), no CSS gets loaded.

I’m running this on CentOS 5.2, using NginX 0.7.53. WP runs perfectly.

It’s not an “access” problem. Firebug shows that the CSS file is read correctly (and I can see all of the lines in there, so NginX is serving up the CSS). But, for whatever reason, FF and Chrome both decide that it’s not CSS, and just ignore the styles completely (Firebug says that there are no style elements on the page).

Looking at the NginX debug logs, IE takes the css file with an “Accept: */*” and FF takes it with an “Accept: text/css”. Otherwise, I don’t see any obvious differences.

If I code up my own html file, and use the exact same syntax for the css <link> line that BP generates, FF will _correctly_ parse the css file.

The only thing that seems strange in the BP generated code is that the HTML fails the W3C validator for including an “id=_wpnonce” in the hidden search form field _two times_. But, if I remove one of those lines, FF still fails to parse the css.

Here are the links (the site has zero in it at the moment):

http://songsandjingles.com/wordpress-mu/

Here is a link to my “test” html file, which loads the same css file (where I added yellow as the background color in custom.css):

http://songsandjingles.com/wordpress-mu/testme.html

Just to show that the css file is accessible:

http://songsandjingles.com/wordpress-mu/wp-content/themes/buddypress-home/style.css

Any help would be greatly appreciated, thanks in advance!

P.S. The most obvious difference between my tiny HTML file and the generated one is that I have no DOCTYPE or “profile=” in mine…

Is there a Shortcut available to reference to the Template/Theme directory?

I tried something like this, but unfortunately there is no BP_TEMPLATE_URL available:

‘echo ‘root_domain . ‘”><img id=”admin-bar-logo” src=”‘ . apply_filters( ‘bp_admin_bar_logo_src’, BP_TEMPLATE_URL . ‘/images/admin_bar_logo.gif’ ) . ‘” alt=”‘ . apply_filters( ‘bp_admin_bar_logo_alt_text’, __( ‘BuddyPress’, ‘buddypress’ ) ) . ‘” />‘;

?>’

Does anyone knows the correct Tag for this? I also want to move the admin_bar_logo.gif into my theme directory.

alunsina, if you allow others to post to the main blog then then their posts will show up using the standard index.php template. When you select ‘blog’ from the home theme it runs a template called index.php. By default all posts in chronological order are displayed without any filtering by author. Whatever posts are most recent get displayed first. It doesn’t care who is the author.

This really isn’t something that bp controls. It’s just normal blog behavior. You can change what index.php displays when it is run by modifying the index.php template. Or you can not allow other users to post to the main blog.

Theme designers should be able to customize the output as well as look and feel of their themes with this loop documentation. It’ll be nice to see what people come up with.

If I’m understanding you correctly, you want member blogs to use the same theme that you use for your home theme. If this is correct, here’s how you can accomplish that.

In wp-content >> themes, rename the default folder. Something like old-default works well so you remember what it is.

Then, rename the folder of the theme that you want to be set as default.

i.e. rename buddypress-home to default

Have you made ANY changes to your themes? i.e. Changed div’s by adding or removing any of them? Changed anything in the stylesheets? One wrong letter or character can break everything. (believe me I know lol)

I may be mistaken but I’m pretty sure the home theme runs for everything except what you see when at http://yoursite.com/members/”whatever&#8221;

If you could either set up a test user for us or even just set the admin bar to show for logged out users, that’d be helpful.

Hi Matt,

very nice theme !

Does BP not have its own event-calendar build into it ?

Hi Andy,

is there a chance to have an “events-calendar per Group” ?

Many thanks,

Erich

The Skeleton Theme has a bug in header.php. In the top menu (the UL with id=”nav”) there are references for MEMBERS_SLUG, these should be BP_MEMBERS_SLUG of course.

Great work!

my default themes are the ones with rc2, but can’t reply. I’m certain because I had hard time fixing my css as I mistakenly deleted everything when I updated to rc2 official release.

Maythil-

I hope you don’t think I was being snooty to you. Your issue was simply not clear to me.

Anyway, I now understand that you want the entire screen to be constrained to exactly 800 pixels in width, that you do not want the Buddy bar to be resized upon screen resizing.

There are a few ways to accomplish this. But, the best way is to create a CSS selector that will override the selector in the core file.

If you go to the admin-bar-logo.css file and look at the #wp-admin-bar selector, you’ll see that it has a width property set to 100%. This needs to be changed to your desired fixed width. But, do not change it within this file because it will be lost upon the next BuddyPress upgrade.

Instead, you place your custom CSS in the site-wide-sample.css file found in the BuddyPress-home/css directory. You must rename that file to site-wide.css. Now, your custom CSS selector will override the core BP CSS. Here’s what you’ll place in that file:

#wp-admin-bar { width: 800px !important; }

By the way, do you use Firebug with Firefox? If you don’t, it is a great tool. It not only allows you to find out within which files certain CSS selectors are located, but also to temporarily change them and see what impact they have on the design.

I hope this helps!

my admin bar is totally fucked since i am working with

wpmu 2.7.1

and buddypress rc2

the admin bar is as a menu at the footer of the theme

i am using everything standard with no plugin

<link rel="stylesheet" href="<?php echo bloginfo('template_url') . '/css/yourfile.css' ?>" type="text/css" media="screen" />