BuddyPress.org

Use the custom menu option if the theme supports it. Otherwise, open up the theme files and hardcode the html in there to the various menu items.

Even the bbPress plugin comes with a small set of fallback template files (as a child theme of twentyten) to display forums.

I didn’t say we’d get rid of bp-default! bp-default can continue to be a parent theme. Even if we backport the simplest changes from bbPress for now like get_template_part() to BP (instead of locate_template() like Bowe mentions above), this will make things very easy to build a plugin to serve BP template files without copying them over to the WP theme (as BP Template Pack does now).

In my unreleased plugin, I created a function similar to bbp_get_template_part(), copied bp-default BP-only template files to my plugin directory and swapped out locate_template() for this new function. The plugin served BP template files. Then, combined with this, all you’d need to is create a header-buddypress.php (or footer-buddypress.php, etc.) in your WP theme to make it gel with BuddyPress.

== Never edit core! ==
Of course you’re right, DJPaul.
*mercime smacks palm on forehead*

re: default-home, default-member, bphome, bpmember, bp-sn-parent, and bp-default themes
Thank you.

re: get_template vs locate_template
A great article on proper usage of get_template_part and locate_template can be found here: http://justintadlock.com/archives/2010/11/17/how-to-load-files-within-wordpress-themes.
locate_template – function searches in the STYLESHEETPATH before TEMPLATEPATH so that themes which inherit from a parent theme can just overload one file https://codex.wordpress.org/Function_Reference/locate_template.

They way JJJ describes it would be the way to go imo.. Looking at the BBPress beta this seems to work well, and it would make things a lot easier (and more fun). I have another question about templating though;

1: Using get_template instead of locate template Is there a reason why locate template is used in BP-Default instead of get_template? Looking at TwentyTen and TwentyEleven they all handle it with get_template.. From what I understand from talking to MrMaz it also allows greater flexibility doing it like this. Because get_template can be filtered/hooked into while locate_template is very inflexible.

2: <get_template_part: This seems to be the way forward for new themes. It allows you to load specific template parts in your theme so you can reuse them. (https://codex.wordpress.org/Function_Reference/get_template_part)

I think both of these things could make the theme more flexible and easier to work with.

still at a loss as to why you asked or what you asked in the first place but as long as you’ve found what you need alls well

Hi @All,

I’m writing for themekraft.com, we are a young startup, making our lives with WordPress and 80% BuddyPress related development.
Buddypress has changed our lives and we want to count us in.
We have read the thread from bowe at bp-tricks.com and this thread here, and we want to help, too. It’s like bowe and this thread is bringing our thoughts to the public, and we feel it’s time to come together.

We are 3 people, and we can give 2 hour every week to help out. That makes 6 hours – let’s say one day a week.
We are two developers and 1 theme designer.
There are many small and bigger problems we found in our daily work, we like to have changed. And we would immediately start helping.

For example: bp-default:

We have developed a theme for BuddyPress. And in the theme you can change sidebars, also for BuddyPress components .
But it’s very difficult for us to provide a left sidebar only, because buddypress comes with a right sidebar in the default theme and the sidebar is included in the pages instead of in the header and the footer.

Every component that extends BuddyPress, comes up with the right sidebar in the template files.

That means for us (and all theme devs with theme options like sidebars), we have to rework every template file from every plugin to support having just a left sidebar.

This is just one theme example, we would like to share all experiences to improve theme development with BuddyPress.
We know, there must be at least some templates files for buddypress to work. But they should integrate in different way as now.
We have read this thread, and there are quite a lot of people willing to get their hands on the bp-default.

Wouldn’t it be a great thing to have the bp-default in github, so we can create a team to work together the git way?
There is also an issue tracker in github, and I feel it’s much easier as the trac…

This way integration in a new bp-default team would be very easy.

Patches and all the BuddyPress stuff.

We have done some funny things with custom post types and groups, because it is so difficult to filter groups in a certain way.
Also if we use the custom post type api, we get a lot of benefits like revision backups and so on.

To be honest, we believe that BuddyPress could handle groups more powerful, and we would like to work on this, too.

I have seen the conversation from the BuddyPress ninjas in the early days of 1.2 where JJJ started to think of groups in a API way.
Everything is a group. Like a group of people and so on. I really liked the idea and we would like to see groups become something more powerful.

I will stop writing now, hoping we will just start working, as I guess everything has been discussed before.

Thanks for all, we love BuddyPress and see it us a powerful tool to build great websites, often without the need of a direct social network, using it to realize our customers needs.

We look forward to start helping. We always had the feeling before, that it’s not so easy to become a working part.
So just let us know where we can start, or what you need to be done

Thanks,
svenl77, konradS and mahype

"? Do you mean what has been discussed in the posts in this thread?"

Either, it’s relevant.

"Have a read of the WP codex, look at functions such as register_style, enqueue_style, enqueue_scripts and associated functions"

Nah, just found this helpful How to disable scripts and styles.

Thanks @hnla

? Do you mean what has been discussed in the posts in this thread?

Have a read of the WP codex, look at functions such as register_style, enqueue_style, enqueue_scripts and associated functions

How do I eliminate CSSs and JavaScripts so I can control what I want only one CSS and JavaScript?

I don’t believe it should be the job of the core devs to maintain a blogging theme. BP should only worry about the templating aspects of BP only and should support any WP theme thrown at it.

Exactly and as has been mentioned many times over, it cuts to the core issue of trying to develop themes which is still simply too difficult. Core needs to concentrate on templating and then handing over to themes to do the frontend rendering. Dying to see what JJJ has done with bbPress as it’s starting to sound quite interesting but haven’t had a moment to test it

Hmm slightly frustrated to find this enqueue change as had been unaware and working to what I thought was a relatively current bleeding edge on the test install for a theme.
Have had to try and work out how things are now pulling together and get rid of the styles as they crashed my layout.

remove_action doesn’t work and I had to track down the means of deregistering enqueued styles (please correct me if remove_action does work?)

This will de-register the styles (adminbar works differently and checks for a file in theme folder so can be overridden if you place copy of file in _inc/css/ in your child theme.

`
add_action( ‘wp_print_styles’, ‘deregister_bp_dtheme_styles’, 100 );
function deregister_bp_dtheme_styles() {
wp_deregister_style( ‘bp-default-reset’, ‘bp-default-main’);
}
`

It feels a little confusing BP’s approach to these style file enqueing and adminbar, not sure it’s 100% right?

Apply a filter to “bp_get_group_description_excerpt” (located in bp-groups/bp-groups-templatetags.php).

The default is 20 words.

Try something like this in your theme’s functions.php:

function my_group_excerpt() {
global $groups_template;

$group = $groups_template->group;
return bp_create_excerpt( $group->description, 40 ); // change 40 to anything you want
}
add_filter( 'bp_get_group_description_excerpt', 'my_group_excerpt' );

Code hasn’t been tested.

A little late to this thread, anyway, I’m in total agreement with MrMaz; while there’s some nice work going on in bp-default to make it blog and theme-review compatible, I don’t believe it should be the job of the core devs to maintain a blogging theme. BP should only worry about the templating aspects of BP only and should support any WP theme thrown at it.

With that being said, JJJ has done some awesome, awesome work on this same issue with the bbPress plugin. I’d like to help and see this backported to BuddyPress as soon as possible, but I’m not sure if that is considered too big a change for v1.3. (I did write a similar plugin that attempted to add BP functionality to any WP theme, but I didn’t release it.)

Never edit core!

If you want to totally stop bp-default parent loading its default.css etc, use this in your child’s functions.php:

`
remove_action( ‘wp_print_styles’, ‘bp_dtheme_enqueue_styles’, 11 );
`

In the meantime, as of BP 1.3 trunk-4414

1. open up https://buddypress.trac.wordpress.org/browser/trunk/bp-themes/bp-default/functions.php

2. comment out line # 163 and lines #170 to #175

3. add to your child theme’s stylesheet
`@ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/reset.css );
@ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
@ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );`
delete space between `@` and `import`

You won’t find anything it’s not a BP or author style it’s a header cell so has default browser styles applied ‘font-weight: bolder; text-align: center;’ if you don’t want those then you will need to override them in your author styles.

It’s not a hack just sounds like you haven’t added ‘buddypress’ into the list of tags in the style.css head meta? without buddypress in that tag list the warning is displayed.

If you are referring to the buddypress default theme ( /wp-content/plugins/buddypress/bp-themes/bp-default/ ) it already has the necessary `Tags: buddypress` near the top of the style.css file……

https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#Final

https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

@kshengelia

You shouldn’t really be using ‘valign’ it’s a deprecated attribute, presentation is handled by CSS.

The reason that valign isn’t working for you is precisely because CSS has been used to apply a vertical-align: middle; to that cell.

You need to use a debugging tool such as Firebug for FireFox to allow you to examine the applied style/ rulesets for elements then you would be able to see what was affecting what.

BP default.css states that all table cells should be vertical-align: middle, you will need to adjust that specifically for that cell either by adding a class to style on or using descendant selectors.