David, I guess pasting the JS code would work for the BP member theme (can anyone recommend where file and location to add the code for the default theme that comes with BP?) to track statistics for the community portion of the website.
What would we do to track statistics per user blog?
Of course! A huge thx to Andy as well! He’s any way like Santa! brings us all this lovely stuff which makes us happy 
Jep, added that correctly and the button/tap is shown.
function add_location_to_main_menu() {
$class = (bp_is_page(\'countries\')) ? \' class=\"selected\" \' : \'\';
echo \'<li \' . $class. \'><a href=\"\' . get_option(\'home\') . \'/countries\" title=\"\' . __( \'Countries\', \'buddypress\' ) .\'\">\' . __( \'Countries\', \'buddypress\' ) .\'</a></li>\';
}
add_action(\'bp_nav_items\',\'add_location_to_main_menu\');
My Problem in this case is that it doesn’t load the structure.css from the component when I open the component over this button. It works properly when get to the page over the sub navigation link.
(I’m using a customized home as well as a customized member theme. )
thx 4 ur help!
SQRR
Have you included this code in your bbpress header.php theme?
<div id="search-login-bar">
<?php bp_search_form() ?>
<?php bp_login_bar() ?>
<div class="clear"></div>
</div>
Stephdau-
Are you using a customized theme? If so, have you tried switching to the standard BuddyPress themes to see if the issue goes away?
I’m having trouble identifying why in the skeleton theme the Blog, Group and Member directory pages include both the user and option bar navigation lists with their respective items “selected”… In the default member theme these menus don’t appear on the directory pages as one would expect with them not being actual member pages.
I’m sure I could write some logic around the userbar and optionbar calls but I figure there must be a cleaner approach being utilised in the default member theme… I just couldn’t find it.
In fact, I just figured out the problem.
I just went back and read the history.txt file myself. Well, guess what, this is a change Andy made just before he made v1.2 an official release. Ready?
Removed call to bp_example_add_activity_bullets_css() as will no longer work and is theme specific.
2299491Inactive
I have the bphome theme running, and am experiencing this problem (404 errors on *most* of the menu items).
It seems as though the home theme is working ok, except that it can’t connect to the member theme. I’ve already tried that trick where you switch to the other member theme & switch back — nothing has helped so far.
I dread having to ask our tech support to give us a clean install of WPMU — WP was working fine before (and WP is actually still working fine – it’s just the BP stuff that isn’t working!)
Same problem here, under wpmu 2.7.1, upgrading from bp rc2 to 1.0
Gordon–
Thanks for your help! I figured out what I was doing wrong. I had not replaced the logo image with the new one that I’d created, and so, of course, the old orange one was coming up instead. Isn’t it always the little stuff that trips us up?
All your advice helped me out a great deal. Thank you!
Kit
Phew! that was a lot easier than I thought! 
Modified the bphome theme to suit some custom requirements I had and its working a treat now!
Thanks for the help!
@andy
@burtadsit
could the patch that burt has made here.. https://trac.buddypress.org/ticket/723 change the way that this bit of code works in my post-list.php in my theme.
<?php if ( bp_has_wire_posts( 'item_id=' . bp_wire_item_id() . '&can_post=' . bp_wire_can_post() ) ) : ?>
basically andy you offerd this as a fix but i am just wondering that now that the issues with the slugs in the core files that are fixed on groups wire now effect the way in which the wires post display on the profile side of things..
does tha make sense??
In other words i am try the fix the fact that the wire posts are not displaying on profile pages.
they were working perfectly before burt and i fixed the groups wire??
@KitWit,
That’s all I’ve done too.
I just changed base.css in the two directories, and copied my logo file over as logo.gif to both locations
base.css in
wp-content/bp-themes/bpmember/css
and
wp-content/themes/bphome/css
and logo.gif in
wp-content/bp-themes/bpmember/images
and
wp-content/themes/bphome/images
Then remember to flush the cache in your browser (F5 usually does it)
I also edited both header.php files as I wanted to change the link words from ‘blog’ to ‘News’
as @jfc said, you might need to select a member theme in Admin / BuddyPress / General Settings / Select theme to use for BuddyPress generated pages:
and then save.
Note: Since I was ‘updating’ from RC1 I had to select a different them and then re-save.
Gcs123-
You’re right, switching to the default home theme solves my problem, however is there any modifications I can make to my custom theme to enable it to work?
Without knowing what you changed, and without seeing your files, it would be impossible to tell you what to change.
Your have two choices:
1. Compare your current themes to v1.2 of the Skeleton Theme and locate the differences. Then, change as appropriate.
2. Copy the standard BuddyPress themes, use them as your starting point, customize as desired.
You’re right, switching to the default home theme solves my problem, however is there any modifications I can make to my custom theme to enable it to work?
I have not done much styling to the skeleton theme so working up form this wont be an issue.
Thanks
Gcs123-
As Enlightenmental1 states, try switching to the standard BP themes. If the problem is solved, then the issue is with your themes.
Also, if you are still using v1.1 of the Skeleton Theme, you need to upgrade. There are important changes in v1.2. If your custom theme is based off of v1.1 of the skeleton, then look at v1.2, find the differences and change accordingly.
switch to the default themes, I bet that will fix your problem, telling you the issue is with your theme.. they say 99% of the time it’s your custom theme
Bdegier-
As JFcarter suggests, you should make a backup of your database before beginning this process. Your BuddyPress data should be in the same DB as your WPMU data. You also may have some image files in other locations, so back those up as well. Finally, be carful of what you delete in wp-content. If you have any customized themes, or 3rd-party plugins, you will want to make sure you have a backup just in case.
Now, upgrading WPMU: Unless this issue has been recently fixed, you cannot use the auto update feature to upgrade WPMU 2.7.1-beta1 to the public release version of WPMU 2.7.1. This is because the upgrade script “sees” WPMU 2.7.1 = WPMU 2.7.1, meaning it does not upgrade you from beta1 since it thinks you are already running 2.7.1.
So, you need to do the old manual upgrade of WPMU following these procedures.
Upgrading BuddyPress: follow these instructions.
I make my changes in bp-member.
Only other thing I can think of is that you should go into the admin panel and check under Buddypress (almost at the bottom of the page). In the general area, you can select a theme for members. Select one, submit it and see what happens.
Gordon, JFC–
Thanks for the help. I went into the bpmember folder and changed the base.css to show different colors and the new logo (as on the home page) but still no change. Maybe more files need to be modified? All I’m trying to do is change the logo from the socialnetworking one supplied with the installation, and the colors at the top, and some text colors … same changes that I made to the CSS file base.css for the home page of the site. Any suggestions? (Sorry to be such a NitWit!
This might be the long version, but
1. When I needed to upgrade, I backed up my database and copied all the buddypress files into another file called “bosox” (just make up a name). I think you may need to copy your avatars and other stuff into your new install from the old one, so don’t delete the old Buddypress files for awhile!
2. Then I added the Buddypress files to their new locations and activated it. If you have heavy customization to CSS, you’ll need to re-do the changes (reference your old CSS files).
3. You’ll also need to:
– select and activate themes
– move all your plugins to the new plugin location (it changes in 1.0 from your version)
– copy avatar files into the new location (I had to do this, but not everyone did)
Those are the basics. All the best to you!
@kitwit
I usually update the themes/bphome (for the basic site) and wp-content/bp-themes/bpmember (which controls the member and directory pages). I update them separately because I sometimes want certain customizations with the member profiles and not for the main part of the site.
All the best to you!
@Kitwit
You did follow this:
https://codex.buddypress.org/getting-started/installing-buddypres
and do have the member them in the correct place?
where it says:
6. The plugins are now activated and running, but you will need to move the themes to the correct locations. Move /wp-content/plugins/buddypress/bp-themes/ to /wp-content/bp-themes/
7. You can use any WordPress theme as your root blog theme, but BuddyPress comes bundled with an extra “home†theme that you can optionally use. To install it, move /wp-content/bp-themes/bphome/ to /wp-content/themes/bphome/.
you will then need to edit the member theme to reflect similar changes in the base theme.
Hope that helps.
Gordon
@Kitwit,
You\’ll also need to edit the member-theme css files- these control the look of Members / groups pages etc.
If you\’ve installed it properly then they should be in /wp-content/bp-themes/bpmember/css
as per here: http://mypartyonparty.biz
http://www.w3schools.com/ is a great resource as is http://www.lynda.com and of course the documentation available on this site https://codex.buddypress.org/
@Maythil – If you’re on a Mac… download a copy of CSS Edit:
http://macrabbit.com/cssedit/
This editor makes it ridiculously simple to “reverse engineer” CSS code. In the “x-ray” mode you can click any element on the screen and it tells you what the container is (along with all of it’s parent elements). You can also bring up an “inspector” that will show you all CSS declarations that are affecting that element. And you can even modify the CSS and see the changes as you type the code. I’m not sure if there is anything similar for PC… but there must be.
I actually took a quick look myself using CSS Edit and the difference between profile pages and other pages seems to be that profile pages have two left sidebars with a fixed width of 138px (#optionsbar and #userbar) while the other pages have a single right sidebar (#sidebar) without any width defined (i.e. 100%). Meanwhile, #main is used on all pages and has a min-width of 680px. So unless you change some CSS code… the profile pages will always be at least 956px wide.
How did you change the CSS? One thing to bear in mind is that the default theme is fluid. It has min and max widths set. It sounds like you want a fixed width of 800px all the time (no bigger, no smaller… regardless of window size). So… did you remove the min/max on the body and change it to 800? Did you remove the min-width on #main and change it to… let’s say… 560px (allowing 120px each for those two sidebars in the profile)?
Anyway… as mentioned above… this is not a bug and has nothing to do with BuddyPress development. It’s just CSS 101. But I feel you pain. Hopefully the above is some help.
p.s. Did you look at Elgg during your evaluation? It has some features I need that BP currently lacks… but BP is clearly much superior otherwise.
