@vdfbelial Strange behavior indeed. What browser are you using? What theme? btw, your link to site leads to dead end.
If you narrow your browser you will see the issue, links set out this way only work in fixed width layouts or at least where the min overall layout width is greater than the links, At min layout width and max width as set the links haven’t enough room, start adding plugins that add links to the main set and the problem gets worse, this adjustment allows a bit of room to breath.
Everything was fine on my end, but I’ve made the changes you mentioned. Everything working OK now?
Last few things just to stop the main links from wrapping and bunching up.
Add these lines:
#header h1 {bottom:30px;}
ul#nav {max-width:80%;}
Although to be honest width is probably better as IE6 doesn’t understand min-* property
@Anton Thanks! If you guys like what we are doing we keep up the hard work… 
Captcha is integrated in the template file and by just adding a small action to bp_signup_validate:
Template:
https://svn.bettercodes.org/bettercodes/trunk/bettercodes/bc-themes/bc-default/registration/register.php (line 186)
Action:
https://svn.bettercodes.org/bettercodes/trunk/bettercodes/bc-core/bc-core.php (line 558)
If you need more help just drop me a PM on bettercodes. ok?
That’s better one thing though: At the moment copying and pasting from this site doesn’t work as characters are being converted, where I set out a series of em dashes it translated those to hyphens I think or vis versa manually edit the comment I made and replace that long line with your own dashes or remove altogether.
are made within the new folder by copying the default files and altering them?
Yes and no. You can approach things in a few ways – first, and as I’ve seen that you have done, is to inherit the original files then you could add further styles after the @import statements as I’ve shown one post above.
you can copy ALL _inc/css/*.css files to your theme and edit them directly then your @import path would be simply (_inc/css/default.css)
This does mean that if the BP default theme is updated and changes made to the themes CSS your theme will not get them.
Lastly use nufink and do it all oneself big job, long time!
Ahh right, I see. I’ve totally misread what it said in the help file.
Thanks for your infinite patience!
Try this which should work:
/*
Theme Name: TSS
Theme URI: http://www.thescratchingshed.com/themes/tss/
Description: TSS custom
Version: 1.0
Author: TSS
Author URI: http://www.thescratchingshed.com/
Template: bp-default
Tags: buddypress, two-column, blue, white
*/
/* Inherit the default theme styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
/* Inherit the default theme adminbar styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );
/* Begin custom styles
*/
/* change primary sidebar width to 300px */
div#content .padder {margin-right:300px;}
div#sidebar {width:300px;margin-left:-301px;}
As I understood the linked post, you create a new theme folder, create style.css (which links to the default theme) and then any changes you wish to make, are made within the new folder by copying the default files and altering them?
@josemy – thanks for the positive feedback!! At the moment the theme files contain many individual sections which will not work on a normal wp installation. It will take some time to remove them and make the theme ready for a initial release. Just give us some time….
BTW there was a typo which wouldn’t have helped matters in my original post where I described an ‘ID’ it should have been a ‘class’; my bad!
Should read:
div#content .padder {margin-right:300px;}
That doesn’t sound correct, if you follow the instructions given on the child theme codex page then you will have a stylesheet that references the original default.css you do not want to create a duplicate of it, you make your changes in the new child theme stylesheet, that’s the one that calls default.css with a line that should look like this:
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
Hmm… think I may be editing the wrong file or something?
I’ve done as you said and created a child theme (which is still activated). I’ve created a new copy of default.css and edited the settings as instructed above, but still no change?
If you are making changes to styling you do NOT have to reinstall BP from scratch, it’s simply not necessary.
You should be making changes to a child theme; are you using a child theme? If not follow these instructions here:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/
If you are making the changes I described earlier then you enter them in the newly created stylesheet file and they act as an override to the default styles that are pulled in to this stylesheet file.
If you follow this procedure you change nothing about the default styling that can’t be reversed by either simply deleting your new ruleset styles from the child stylesheet file or wrapping them in comments to kill them:
/* #content {these styles cease to be read} */
Give things another go but this time if it doesn’t work don’t reverse things leave it up live if you can and I’ll look and see where you have gone wrong.
Hi @hnla and thanks for your reply.
I followed the instructions you gave, but must have done something wrong as the column width didn’t change, but all the widgets it was previously displaying vanished. I had to reinstall BuddyPress from scratch to recover it. Any guesses as to where I went wrong?
PS. I’m not very savvy when it comes to CSS.
No no no, that’s fabulous, many thanks @hnla! I understand the logic of it all now. I’ll get to work on setting all that up now, and see how I go.
When you refer to a child theme it refers to the ability to create a new blank folder within the ‘theme’ folder this would be considered a ‘Child theme’ if it simply had a stylesheet residing in it’s root /top level that stated it was using the files from a particular parent theme, what then happens is having selected this theme – which now would appear in your dashboard themes page, – WP examines the stylesheet information at the top of the file and finds that it instructs WP to look for files in a particular theme as being the main theme files to use; however the clever trick is that WP first knows that it must look in your child theme for necessary files FIRST! and if they are not found THEN look for the necessary file in the stated parent theme, thus you do not have to have any files in your child theme as WP will use the parent files, but you can add new CSS rulesets to the stylesheet living in the child theme and these will be read and acted on (that stylesheet references the parent CSS stylesheet files through the @import rule first and then reads on for any additional rules you have added below the @import calls)
If you do not want to make any changes to BP-Default theme then you simply activate that theme as seen in the theme page in the dashboard. When members create a blog then those blogs should use the twentyten theme or whatever other themes you choose to download and make available (Note that you decide what themes are available to members via the ‘Super Admin >Themes’ page only the themes that you select ‘yes’ to are available to member blogs so to avoid them attempting to use the BP-Default on user blogs you ensure BP themes are not selected)
If you decide that you do need to make changes to BP-Default theme then you would create a folder under ‘Themes’ name it ? ‘my-bp-default’
to the folder you add the requisite stylesheet and now you can move files as required from bp-Default original folder to your new folder and edit them as you wish, or simply create new rulesets to style elements which you place in the new stylesheet file. BP/WP now looks at your new child theme for any files that it must use in preference to the same versions that might reside in the original theme folder.
Apologies if the above covers ground you already understand.
when you say “if you are using a child theme” do you mean do I have cp-twentyten as the current theme in admin/appearance/themes? No, I don’t. I have the current theme BuddyPress Default 1.2.5.2, and I have the child theme uploaded to wp-content/themes/
If you are using a child theme then you do not need to worry about the default theme unless you ned to modify a file. At that point you copy the file to your child theme.
The regular WP twenty ten them will not work with BP out of the box that is why there is a BP version.
Also have the same problem with my local installation.
1) Installed WordPress: Worked
2) Got Buddypress as a plugin.
3) Got a message, that the .htaccess could not be changed due to missing permissions, so changed the permissions, then no error message appears
4) Choosed the Buddypress default theme
5) Choosed the permalink options
= I also get tese 404 error messages (for example /wordpress/activity/)
I did that and the log in dissapear but instead it was replace but the code itself: remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2); hahaha I am using IE 6 by the way and running latest buddypress version and wordpress and also the default theme, I am not at home at this moment.
It was easy. Luckily I was able to figure it out. Plus I could have done most of it in the theme too. The real key was that I needed to figure out how the errors were being passed on the registration page. Then, I figured they had to be in $bp and they were. Here’s the code I used in bp-custom.php
function registtration_screen_message_on_error() {
The message I want to appear for the user.
}
add_action( ‘template_notices’, ‘registtration_screen_message_on_error’ );
To get the errors and only display it if there are errors I used $bp->signup->errors
Just thought I’d share.
@boonebgorges @nuprn1 thanks for posting the instructions. It answered my query. I think it’s odd that topic tags don’t show up in threads in the default theme. Anyway, it works Next thing BP needs to do is provide a forum tag manager tool (unless there’s already one and I didn’t see it) similar to Dashboard > Posts > Post Tags and allow the topic creators to edit tags like they can their Title and Content under Edit Topic. Right now I have to do forum tag management using phpMyAdmin.
I like it, A LOT.
Clean, neat and simple. Congratulations.
Apart from the plugins, maybe U could release the layout as a theme…
