BuddyPress.org

@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.

this is the same on RC2,

also not working here on buddypress.org

yes ther is problem with the slugs and certain bit of code that means that wire is broken on the groups page

burt helped me get this to work..

https://trac.buddypress.org/ticket/723

the problem i have now is that when i went through this i managed to break the displaying of the profile wire.. the post submit ok but the display of them has conked??

can any one think what it could be… they were working well before..

one thing i did do is define change ( ‘BP_GROUPS_DB_VERSION’, ‘1300’ ); to 1301 and this may have broken it i changed it back now.. could it have…

where is the display wire for profile part

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.

Okay, since we’ve had a few people make this mistake I need to ask this just in case. Everyone in this thread who is having 404 issues is running BuddyPress with WPMU and not the single-user version of WordPress, correct?

This means downloading WordPress from here: https://mu.wordpress.org/download/

Specifically @Sgoetz-

Running WPMU, ran automatic upgrade to 2.7.1 prior to installing BP

Were you running WPMu 2.7.1-beta1 before upgrading?

If so, you cannot upgrade from beta1 to public 2.7.1 using the automatic upgrade feature. 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 must manually upgrade WPMU following these instructions: https://codex.wordpress.org/Upgrading_WPMU

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.

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!

Philip-

We are working on a proper privacy component for BuddyPress that will allow for a given member to decide how much of their personal data they want to expose to the world. This not only includes their profile data, but also a member’s data contained in the other BuddyPress components.

As far as group-specific privacy control, that is also an area we are discussing.

@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

Philip-

You can install my Featured Members Widget for BuddyPress: https://wordpress.org/extend/plugins/buddypress-featured-members-widget/

@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

Jeff, could you get this working in v1.2 and then I can modify my component accordingly?

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/

Nada. Has anyone gotten this to successfully work with the skeleton component on their server?

@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.

K,

Remember that I’m a newbie…

But I would not touch the Buddypress plugin with “Plugin Commander”. If you wish to activate Buddypress across your site do so in the WPMU plugin section and activate site wide.

R