BuddyPress.org

@henrywright-1
I think on balance I would tend now to favour going the theme compat route, as the process best to follow in all theme/site building respects, we added extended capabilities with the template hierarchy which make it more useful and the templates and styles were updated and improved.

But the other approach is perfectly valid and leaves full templates directly in your control.

Personally I like the the ability, though, of being able to neatly segregate BP templates under one root dir /community/ or /buddypress/

As for the js being the reasoning remember that both approaches essentially use copies of the same file/s so you still get those either way, one thing I’d like to see and may propose is the main js & ajax files being centralized as bp assets that both approaches could access rather than maintained separately in the theme folders – although that is the place they ought to live really.

This whole question of approach taken is one I’ve raised as there are confusing aspects and I want a codex guide that outlines the approaches on offer and brings some clarity to making choices, which we’ll pencil in to the new guides once Codex is straightened out.

If there’s a tutorial on how to convert the default pages into buddypress ones I’d take that too.

@ptvstudios BuddyPress components are in fact inserted into the default pages (page.php) of WordPress themes and have only the basic styles so that the elements of the BP components would take on the styles set up by your theme for a more seamless integration.

If the BP pages are showing as full-width, it could most probably be because the default page of your premium theme is full-width in the first place. To make all BP pages 2 columns, find your theme’s template with a 2-column layout and copy source code over to a new file named buddypress.php, save and then upload buddypress.php to your theme folder in server. If this doesn’t work out for you, please contact the premium theme author to help you set up the buddypress.php file to 2 columns. Good luck!

I created a buddypress.php by copying the code tooked from the page-template-fullwidth.php. It didn’t work

@resistoyen sometimes it doesn’t work right away. To continue, using this page as reference:
https://themes.trac.wordpress.org/browser/oxygen/0.5/page-template-fullwidth.php?rev=24186

a) Remove the following from your buddypress.php file
Line 3: Template Name: Full Width
Line 13-17: <div class="aside"> to closing </div>

b) Change Line 21 from
<div class="content-wrap">
to
<div class="content-wrap bp-full-width">

c) Add this to your theme’s stylesheet

.bp-full-width {
width: 100% !important; 
}

@jtm21
Yes essentially that would be fine, bearing in mind you might lose or have to account for any styles that were in place to deal with js frills.

Generally now you can or should be using BP in theme compat mode as it offers more options now as well as ability to keep templates and assets neatly under /buddypress/ or /community/ adding directories directly to you theme root will invoke the older approach, and although still valid, less of a attraction now the theme compat templates can be customized for components, actions, user_ids etc.

Check the functions.php in the bp-legacy template folders as that will show you the class used for setting up a theme and it’s assets.

No the whole point of the bundled styles is not to lend any particular visual styles over and above basic layout stuff otherwise it would have never been possible to implement BP theme compatibility, these styles have to slot into any theme, themes we have no way of predicting in terms of their own visual style. it is up to you to add whatever additional styles you need for BP to sit with your theme.

Or find a theme that has been pre-built to use BP.

@hugodisasters
– Change to Twenty Twelve theme and check the BP pages if has at least some styles applied.
– View source code of site to check if the files I mentioned above are in source.

If yes to both, then something’s blocking BP from enqueueing BP’s JS and CSS files in your deTube theme. Check theme’s functions.php file if there’s something like add_theme_support(buddypress). If so, remove it.

do you want to edit css or just get rid of it all together? You can add blank files. Adding these files will override bp’s files. If they are blank nothing gets loaded:

yourtheme/css/buddypress.css
yourtheme/js/buddypress.js

Or try and remove hook action:

remove_action(‘bp_enqueue_styles’);
remove_action(‘bp_enqueue_scripts’);

@tengwah If you want to keep the changes that you’re making to the BuddyPress Default theme, I suggest that you create a child theme and make the modifications there.

Simple way to remove the tags, add the following to your child theme’s stylesheet:
#commentform p.form-allowed-tags { display: none; }

@disqusnow the large vertical gap is caused by the style applied to the container of the group avatar and group admin/s avatar. To correct the issue, add the following at the bottom of your theme’s stylesheet:

#buddypress div#item-header {
overflow: visible !important;
}

The easiest way to inherit ‘some’ of the CSS from the default theme is to copy what you need and paste it into your theme’s style.css.

Then add this to your functions.php file

if ( !function_exists( 'bp_dtheme_enqueue_styles' ) ) :
    function bp_dtheme_enqueue_styles() {}
endif;

This will tell BuddyPress not to queue up the default stylesheet.

@mahdiar Add this to your theme’s stylesheet
#buddypress ul.item-list li div.action {
left: 0 !important;
}

@rkcorp The theme looks great.

While awaiting theme review (up to 4 weeks), please make sure that your theme meets the WordPress Theme Review guidelines. Scanned source code at themes trac and there are issues which need to be be addressed. e.g. scripts and styles in <head> for one.

The following information should be of assistance in getting your theme to meet all the criteria:
* Theme Review – https://codex.wordpress.org/Theme_Review
* Theme Unit Checklist – https://codex.wordpress.org/Theme_Unit_Test
* Theme Development – https://codex.wordpress.org/Theme_Development
* Theme-Check Plugin – https://wordpress.org/extend/plugins/theme-check/
* Debogger Plugin – https://wordpress.org/extend/plugins/debogger/

After you’ve updated your theme to meet WP Theme Review guidelines, you’ll just need to upload a new version of the theme. You’ll still retain your place in the theme review queue.

@dowy Add the following to your theme’s stylesheet:

#buddypress table tr.alt td {
background: none transparent !important;
}

#buddypress table tr td.label {
border-right: none !important;
}

.label {
background-color: transparent !important;
}

Are all styles overloading or just some? If just some it could be forcing styles through.
Are you also using BuddyPress 1.7.2 (or 1.7.x)?

However, if it’s all then can you check if the theme has this line in it:

add_theme_support( 'buddypress' );

If no, then can you try with another theme just to see if it’s Avenue that’s being grumpy? Maybe something like the default WordPress Twenty-Twelve would be a nice test theme.

Your theme imposes rather generic styles on li elements in the content areas under a parent class of ‘shortcodes’ This is conflicting with the BP object nav li elements forcing them  to 100% width.

In your themes stylesheet you’ll need to try adding something like:

<code>

#buddypress div.item-list-tabs ul li {
    width: auto;

}

</code>

Other than that it’s a case of using that top level id #buddypress to further style BP elements in what ever stylesheet is applicable using tools such as firebug to identify the rulesets and their selectors that BP has already set.

Trying to make sense of what your process has been here as you shouldn’t be having issues.
Going back up two posts if as you say you built originally for template pack or using template pack then when you tried to switch to 1.7 theme compat you should not have tried to move the existing folders/files into the theme compat folder structure, that will not work older bp-default templates and newer legacy ones are not the same new templates do not have head/footer elements.
I think you need to continue on with BP as a child theme but probably with the add_theme_suport line added and then handle enqueueing / including the styles/js yourself.

There is documentation! it’s in the documentation section of the site.
https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/

However as Paul says or:

Copy over the stylesheet from /bp-templates/bp-legacy/css/buddypress.css to your theme /css/ that will override the original copy, either add to that sheet or start from scratch but for simple changes do as Paul says and work in styles.css

@epatrick
Just to illustrate why it’s NOT a BP issue.

You are missing a series of styles that are getting generated and injected into the head of each page (not a good approach but hey ho)
e.g. .skinset-menu{}

Now quite why these styles are not getting added to actual single groups although they are to the parent directory is a question only the theme authors can answer.

it’s their theme and their approach to applying their styles and functions, as to why their approach doesn’t work on the group single views is only something that can be understood by de-constructing the theme as we and BP have no knowledge of that it’s next to impossible to help, thus it IS their duty to help or guide you, perhaps a setting you’ve missed in the backend?

I don’t mean this to sound unhelpful on our part but just trying to point out the issues from our perspective.

hi @talitaco,

BP 1.7 introduce a new template era.
So for child theme, you don’t have to add the import comments to styles.css

You also need to read and read and read, untill you get it, the Codex:
https://codex.buddypress.org/theme-compatibility/add-buddypress-styles-to-a-theme/
https://codex.buddypress.org/developer-and-designer-information/

@bandtobuy 1. BuddyPress should be activated before child theme of bp-default theme is recognized in themes. or 2. Did you add the stylesheet header in your new style.css file? you didn’t say.
/*
Theme Name: My Child theme
Theme URI: – optional –
Author: Your Name
Author URI: – optional –
Description: – optional –
Version: – optional, but better to add version –
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Tags: buddypress
Theme: bp-default
*/

Tried in
yourdomain.com/your wordpress installation directory/wp-content/plugins/buddypress/bp-themes/bp-default/styles.css – still not showing.

Also tired
yourdomain.com/your wordpress installation directory/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/default.css

line 1658 .standard-form input[type=text] { press enter and add
to new Line 1659 color: #000 important

Still no registration button?

Any help much appreciated