BuddyPress.org

OK, I’m really new to this.

When I change the headder info on style.css does it overwrite style.css or create a new theme called Buddy Dusk?

What exactly do you mean by members stuff?

And are you editing theme files (like header.php) or just wanting to link from within, say, a WordPress page or blog post?

You can definitely adjust the first one of those without being a CSS or PHP wizard, just by editing header.php. I suggest you create a Child Theme first.

There are also some good SEO plugins out there, although I don’t know what works with BuddyPress. Hopefully somebody else’ll chime in here.

Use the unified search here on BuddyPress.org, and you’ll find some good discussions, including this one which sends you to BuddyDev. With a bit of elbow grease and tweaking, you should be good to go. (Whether it’s the “best” way is up for discussion, of course.)

How about a theme focused on…
-Groups
-Forums
-Blogs
-etc

Basically, make the theme really expose certain BP functions. Like in my case, I’ve modified it to be VERY Group centric.

Why not just use a child theme and modify the index.php to show whatever you want the page to be? You could also make it show one thing for logged in and one thing for not logged in. You probably could even look at referring page or set a cookie or something to know if it’s the first time they’ve been or not.

this would solve so much for me. thanks ray.

Yep I’ve added it to a ever growing to do list, not sure when I’ll be able to get round to it but definitely will at some point as it’s a shame that bp-default doesn’t render well on IE >= 7

That would be sweet if you could do that, hnla!

‘Attempts’ being the operative word.

it’s a shame as all that’s really required is a little knowledge and experience, IE issues are not really that hard to cope with, the use of combinator selectors that IE6 doesn’t understand is just plain wrong and unnecessary, and generally only used where rulesets were desired to be hidden from IE or where the ruleset simply added fluff and wasn’t vital for layout purposes.

Someone!? – yes probably end up being me – will need to produce a Conditional Comment stylesheet [if lte IE 7] to provide support for bp-default and our old ailing fiend IE6/7 that can be packaged with the BP install.

The bp-default theme does not look cosmetically good in IE6. Some CSS rules are using newer ones that IE6 just doesn’t support.
Also, the BP admin bar will be displayed in the footer instead of being fixed at the top.

However, most of the functionality should work.

You could try installing IE7-JS:
http://code.google.com/p/ie7-js/

It attempts to fix many of the HTML and CSS issues that IE6 has.

You’d have to turn your WordPress 3.0 install into a network and create a secondary blog.

Then you could activate the BP-default theme on this new blog.

Follow these instructions:
https://codex.buddypress.org/how-to-guides/install-buddypress-on-a-secondary-blog/

@amahesh –

In your theme’s functions.php, make sure your code looks something like this:
http://pastebin.com/Pn1jFXG5

Read the comments in the code.

Then In your duplicate of bp-activity-group-feed.php, you need to change:

if ( bp_has_activities( 'object=' . $bp->groups->id . '&primary_id=' . $bp->groups->current_group->id . '&max=50&display_comments=threaded' ) ) :

to

if ( bp_has_activities( 'object=' . $bp->groups->id . '&primary_id=' . $bp->groups->current_group->id . '&secondary_item_id=' . $bp->groups->current_group->creator_id . 'max=50&display_comments=threaded' ) ) :

This will filter the group activity feed so only updates from the creator of the group will be listed. If you have multiple admins, you’ll have to find a way to append their IDs (comma-delimited) to the end of the “secondary_item_id” parameter.

No it’s not hard to believe, many organizations still use IE6 and can’t change as they have proprietary in house apps written for it. I’m afraid the truth is that too many younger coders and not so younger are are happy to assume that IE6/7 is dead and they don’t need to code with correct and proper cross browser checks or probably know how to do that. The approach now with IE8 is out should be to ensure that there is at the least a presentable layout that functions at a basic level albeit without the bells and whistles, sadly this appears to be not the case and work will have to be done in addition . There are few themes around for BP personally I don’t have experience of many to any great degree, and there are a few from a certain premium outfit that I was non too impressed by. You might find better themes at http://buddydev.com/ but if you take any specifically ask whether they are checked to work in IE6

Try this yet?
Show Excerpts
Except instead of copying over and editing the site’s main index.php, make sure you find the right file for your theme (in bp-default, that’d be the index.php file in the blogs directory–probably the same for BP Widget Theme, but I haven’t looked at it).

Older version of IE? which specifically? IE6? If so I’m afraid you’ll be out of luck or at least search long and hard to find themes that work with IE6 they should! but most won’t have taken this older browser into account bp-default hasn’t – by the look of things – done any or much testing in IE6.

There may be a few of the better ‘Premium’ themes around that have done their duty by browsers, but be prepared that if you really want layouts working in IE6 you might have to get someone to do that for you specifically.

@hnla

Wow, you really took this little project to heart, didn’t you? Thanks for investing so much time on it!

1. Didn’t realize the ul elements could cause problems but it works just fine without them (tested successfully on bp-default and child theme).

2. By wrapping wp_list_pages in ul elements, all pages aggregate under a top-level “Pages” nav item, with actual WP pages as subnav items and child pages as sub-subnavs as example below:

“Pages”
– Page 1 – – Page 1 child 1 – – Page 1 grandchild 1
– – – – – – – – – – – – – – – – – – – – – Page 1 grandchild 2
– – – – – – – – Page 1 child 2
– Page 2

By removing the “Pages” li element and wrapping the call to wp_list_pages in li elements, WP pages appear as top level, with child pages as subnavs. Creating a new page adds it to the nav as a top-level item, unless excluded (either entering the page ID manually in the code, or with “Exclude Pages” plugin). I prefer it this way, but the modified code could be included as an option in the plugin for those who prefer having all pages listed under a common heading, with instructions on where to change the heading label.

3. I get no errors with the new WP3.0 checks in place. I couldn’t figure out how to do that, but I see it was a rather simple if !function_exists call. Huh…

4. I left the top link name “Pages” in the wp_nav_menu calls for now. I have not tested this code on WP3.0 so don’t know if the menus will behave as in 2.9.2

I ran the code with modifications, both yours and mine, and it works brilliantly. Collaboration is a wonderful thing

Here’s my revision: http://pastebin.com/4U85PWrt

No word yet from WP about my plugin submission… still waiting. Got to get to work now, thanks again!

That plugin is a quick fix. You will have to add styles to your themes CSS file to make it look right. Each theme has it’s own id’s and classes so there would be know way to make it look right for every theme out of the box.

My suggestion is get firebug firefox add on and get to crackin’!