BuddyPress.org

1) Depends if you’re using the same theme/child theme for both/all blogs. If you are doing so, both should have same styles.
2) https://wordpress.org/extend/plugins/wpmu-new-blog-defaults/ or https://wordpress.org/extend/plugins/yd-wpmu-sitewide-options/
3) see New Bkig Defaults plugin above

Created a group https://buddypress.org/community/groups/bp-default/

@djpaul here’s what I got so far. I think a couple of these styles are redundant or could be redone with less code. I didn’t mess with the original nav css, that code might be able to be integrated into the drop menu’s css.

/* Menu

ul#nav li.selected:hover > a,
ul#nav li.current_page_item:hover > a,
ul#nav li.current_menu_item:hover > a {
background: #333;
color: #fff;
}

#nav ul {
box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
-moz-box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
-webkit-box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
display: none;
position: absolute;
top: 30px;
left: 0;
float: left;
width: 180px;
z-index: 99999;
}

#nav ul li {
min-width: 180px;
position: relative;
}

#nav ul a {
background: #333;
padding: 10px;
width: 160px;
height: auto;
}

#nav ul li a {
-moz-border-radius-topleft: 0px;
-webkit-border-top-left-radius: 0px;
-moz-border-radius-topright: 0px;
-webkit-border-top-right-radius: 0px;
}

#nav ul.sub-menu li a {
background: #333;
color: #fff;
}

#nav li.current_page_item a:hover,
#nav li.current_menu_item a:hover,
#nav ul.sub-menu li a:hover {
background: #222;
}

#nav li:hover > a,
#nav ul ul :hover > a {
background: #333;
color: #fff;
}

#nav li:hover > ul {
display: block;
}

#nav ul ul {
position: absolute;
top: 0;
left: 100%;
width: 100%;
}

@hnla there was something about BP.org UX/UI in Ninjas forum topic and writeboard, but haven’t read one specific re bp-default. Is that in trac and/or discussed in BP IRC? In any case, count me in

well that was my next suggestion. browser fixes should be in it’s own file.

Remove the notice: add “buddypress” to the templatetags in style.css of your theme.

Display:none is an accessibility no no, left:-999em ought to be used, not so much a IE thing.

My concern was more for the inability of IE6 to grok :hover on anything but anchor elements, adminbar covers this aspect so I added / submitted a patch to add sfhover class so any hover styles need to be grouped with the class selector .sfhover so IE6 can function.

tbh it shouldn’t really be a question of whether BP is supporting IE6 although naturally if that’s the descision it wants to make for bp-default then that’s fine, I have on a to do list and promised a while back a IE6 CC stylesheet and will get around to it at some point soon? hopefully

Did raise that a while? back, not sure it inspired much interest, but you would need to define whether one was dealing with general UX /UI or the default theme, from a theming point of view not child theme necessarily , but full on theming some UI / UX is merited along with other issues such as identifying markup that needs removing from core if applicable and aspects such as better handling of activity_action which isn’t fun to deal with from a frontend perspective.

yeah I have a MS install let me try on a single. I have the styles almost worked out. Also back to the IE6 issue. If the rest of BP is not supporting it why should the nav not to mention 2010 doesn’t. The display:none method is easier for customization on the user end

The thread is in reference to 1.3, I think that the styles just need to be worked up and then submitted as a patch. I had issues using trunk on a fairly clean MS install not sure why but lots of odd issues had to install on a plain WP copy in the end.

How about we start a group for designer contributions and duscusions of UI and UX

is this for 1.3? Thought that wasnt arriving until January. Anyhoo I cant seem to get trunk installed to work properly.

@suman – re: https://buddypress.org/community/activity/p/114823/

If index.php does not exist, copy index.php from /buddypress/bp-themes/bp-default/ to your bp-columns theme directory and modify as needed.

@DJPaul what are you after Paul? I think everyone might be a little lost as to what actually needs doing? is it just the styles that need sorting, As for my earlier question regarding changes to nav menus for 3.1 and as much as it may be irrelevant? I managed to track down a ticket correcting the issue of not being able to remove parent ul elements which is helpful but couldn’t spot anything dealing with child pages and nesting thereof

@djpaul – a more informative title on your post might help, rather than the general “theme designers: contribute to core”

What versions of WordPress and BuddyPress are you using? Which theme? What other plugins are installed?

It might be related to your theme and it’s functions.php file or incompatibilities. Try using the BuddyPress Default theme and creating some new users with that, then let us know what happens.

I’m seeing this issue within the Admin Bar on my sub-domains, too. I don’t think it’s that related to the sub-themes. The source for the avatar has changed from ‘/wp-content/uploads/avatars/…’ to ‘/files/avatars/…’. Hopefully it’s a just a bug.

Can anyone with 1.2.6 knowledge comment on this? What is this new path structure? Bug?