BuddyPress.org

Hi David. Works for me in all BP child themes. I presume you cleared cache/cookies and are targetting the correct selector , so

:

1. If there is !important after the background image url in parent theme, add it in your declaration in child theme – none !important

2. an alternative: create blank 1×1.gif file and use that for your background url(images/1×1.gif) to override parent theme

Actually… I just tried that. Doesn’t work.

Riiiiiiiiiiiiight. Why didn’t I think of that. I’ve never thought of using simple “none” as a shortcut. Thanks. Sorry Andy.

#header { background: #f76d16 none; }

where “none” will equate to no background image in the child theme; it overrides

url(../images/default_header.jpg);} in parent theme. Works across all browsers.

Andy… please don’t use CSS shortcuts in the 1.2 default theme. It makes overriding a little more difficult / messy if one chooses to use the 1.2 default theme as a parent. For instance… the 1.2 default theme uses a shortcut for background instead of using background-image:

#header {background: url( ../images/default_header.jpg);}

Say I want my header to have a background color and no image. This override won’t work:

#header {background: #f76d16;}

Nor will this:

header {background-color: #f76d16; background-image: none;}

One is forced instead to use the !important declaration so that using the color shortcut can override the image shortcut:

#header {background: #f76d16 !important;}

This works… but the important declaration makes me a little queazy. LOL.

@Andy, First, I have nothing negative to say about BP. It is allowing me to do things I would NEVER even attempt on my own. Looking back on the programming I’ve done in the past, there was NO separation (mostly pre-CSS, php/mysql where my separation was myriad includes). However, as I look at Justin’s code, I’m learning the elegance (and additional complication) of separating form from function.

Doing everything through functions.php, styles.css and hooks is a challenge for me, but I do see the benefits. If there are sufficient hooks, most things can be accomplished this way. If there is a hook, I can use the new template tag just by modifying functions.php instead of changing the myriad template files that might contain the new tag.

What sucks (for me) in that model is I have to switch back and forth from template to function and then ensure I test everything well. What works is I get to change it once.

Regardless, for template tags and other changes, what’s most important is documentation (which can be a challenge with development cycles). If the changelog tells me what to look for and what functionality has changed (see Peter’s post above), the process is MUCH less painful. I know you know this, but most of us would rather have the features now and struggle without the docs – Catch 22.

Whatever the result, I’m ecstatic that Buddypress exists, that Automattic adopted it and you finally have some additional help.

FWIW, My views on this went into the trac ticket.

Upgrade to 1.0 then to 1.1.3

It would def hav to be one plugin with connect options. ‘Buddypress Connect’

You install plug in and then choose which connects you’d like to use. When user signs up it gives connect options to use. I’ve seen it done on other sites where you input your email and it maps both connects to an email or user id.

Wow guys I think that everyone needs to keep in mind just how far BuddyPress has come over the last year. Yes there have been some hiccups along the way, but 2009 has been an amazing year for BuddyPress! Just remember that we are still 1.x software here folks! I just found my 1.x version of Final Cut Pro the other day and the box alone is 1/5 the size of my current version 7.x of FCP Studio (and it ran on OS9). I tell you all this so to remind you that we are all here at the infancy of what is going to continue to be a fantastic piece of software! Cheers and Happy New Year!

BuddyPress adds new template tags that have changed from version to version.

Is there a list of these changes somewhere?

I’m currently upgrading my custom theme from version 1.0 to 1.1.3, still based on the classic theme, which avoids the worst problems for now…

I like the idea of leveraging services like YouTube and Flickr and integrating them into your website using a plugin / API. You don’t reinvent the wheel and you end up with more online “channels” for your content. But the question is always just how well such generic solutions can integrate with your very specific tool (BuddyPress) and project requirements.

You haven’t been hacked and there’s no backdoor. The problem with open sources and sploggers is they can see the code just as much as we can, so they can figure out ways around it.

There *are* solutions and they *do* work. You just have to find the right combo from current information.

Hi Jeff,

this is a great ticket of what is really needed for BP to move ahead.

Thank you !

This is 100% the wrong way.

Log into wp-admin go to BuddyPress > Component Setup and hit the disable radio button next to the blog tracking component.

Haha, Bowe!

It looks like I was adding more details to my post as you where posting your response.

Mysterious Jeff.. Do we have a saboteur on our hands here? Maybe a NING user who felt the breath of BP breathing down it’s neck? Anyways your suggestion is exactly what we need and kudos for bringing this up 10 months ago

I agree with MrMaz’s assessment above. We should be thinking about extending the BuddyPress framework and not deprecating major components at this time.

The ability to assign more than one type of “friend” was something I proposed 10 months ago but was somehow deleted as a future enhancement by an anonymous person. That may have been an automatic “deletion” as it was around the time that the phrase “future enhancement” was replaced with “future release.” But, I would have thought that the ticket would have simply been switched to that new milestone indicator.

https://trac.buddypress.org/ticket/582

My suggestion in the link above is what jjj refers to in this comment on his Trac ticket linked to in this thread’s OP:

It would solve Jeff Sayre’s user relationship issue too…

The best solution to accomplish my suggestion is to extend the Friends Component and model the data in a one to many relationship. Simply relegating friends to another type of group does not accomplish the goal.

Most important thing for me would be the option to categorize your friends and filter the activity stream based on those categories..Looks like all types of sites could benefit from this, at least I haven’t seen people who were against that feature