BuddyPress.org

The home theme controls the front page, and any blog pages in the root blog. It’s essentially just a blog theme with a front page that is emtpy, ready for widgets. Everything else is controlled by the BuddyPress member theme.

Make sure you have re-selected the member theme in “BuddyPress > General Settings” and hit the save button, even if it is already selected.

I’d like to make something similar for people, I just don’t want clones of this site popping up and confusing everyone.

As lot of people said in this forum, making a theme like that is really simple if you use the skeleton theme, it’s just css.

Integrate this theme as andy did is more difficult

i’ve the same issue: only the home page is displayed, but members, groups, profile pages…everything leads to a 404. I’m testing it locally with XAMPP.

I’ve made a manual upgrade, and i’m using default themes both for home and profiles.

this is the path of the theme i’m using: wp-content bp-themes bpmember

note: i’ve tried the solutions posted here: https://buddypress.org/forums/topic.php?id=2457 with no success

note: i’m running the wpmu 2.71 zip (downloaded 1 hour ago)

BeLogical-

I thought that was the case! I just wanted to make sure and also to ensure that others reading this recognize that there is a big difference between the two skeletons.

Yes. converting to v1.2 will be necessary. There are a lot of changes and some bug fixes.

Good luck!

Yeah Jeff, I understand. I\’m trying to figure out why my component is showing up on the home page but not on the same exact theme, but under a users sub-domain. I guess the only thing I can do is convert it to v1.2.

BeLogical-

I am on skeleton component v1.1 and not v1.2.

Just to make sure, you do realize that we are talking about themes and not plugins here?

You are talking about the Skeleton Component for developing a custom plugin, not designing a custom theme. For a custom theme, you would want to use the Skeleton Theme.

Assuming that we are on the same page, then yes, there are significant differences between version 1.1 and version 1.2 of the Skeleton Component. You need to use the newest version. See the changes here: https://codex.buddypress.org/how-to-guides/creating-a-custom-buddypress-component/

http://buddydress.com

There’s two.

And there’s a skeleton member theme here to start your own theme from.

” so we’re left with two choices: 1) Switch to WPMU/BP or 2) Install WPMU/BP in a subdirectory.

My first question is this: Am I right about our two choices above?”

Yes.

Switching the whole thing over to WPMU is actually not so bad. The biggest worry there is plugins. Depending on what ones they are, and which ones are a dealbreaker, you will need to test them somewhere ahead of time before even deciding which option to pick.

posts, comments, users, the theme itself and ad placement – ALL those can be *exactly* the same in WPMU.

“The only drawback we have with installing WPMU/BP in a subdirectory is that we’d lose the ability to pull in BP features onto the homepage of our current site such as recent blog activity, avatars, etc. Is that correct or is there some way for the two to communicate even if on separate installs?”

Actually, you can do that. We did it here on http://wanderlustandlipstick.com, a client site. Note it’s not a BP site, but the main site is a single WP install and the WPMU part is under /blogs/. With some lightweight custom code, we pulled in avatars & recent posts to the front of the main blog.

Overall, your choices are pretty much 50/50. The big kicker here is how you want your URLs to be formed in the end.

If you want or don’t care about an extra folder name in the URL where WPMU will live, then it may be “easier” to have it as an add-on, and share databases to share users.

Personally, I’d lean towards moving the whole site to WPMU. Do the move in a dev environment, then in a low-traffic time planned ahead with full notice, make the switch to the new WPMU site (at the same URL basically).

Exactly

I have the same kind of problem with the ‘Members’, ‘Groups’ and ‘Blogs’ page. Its like these pages are not hooked up with the CSS. I only have this problem when using the latest Skeleton member theme thou. If I use the standard bpmember theme there\’s no problem. Why is that? Problems with the latest Skeleton theme on BP 1.0? :>

Yeah, it may need some further tweaking to grab the right URL.

Yes, of course. You can do anything you want. Suggest you read https://buddypress.org/forums/topic.php?id=1632

Andrea_r, this works really well to start off with. Two things I have noticed off the bat. #1) my custom component doesn\’t show up under this theme for some reason. I am on skeleton component v1.1 and not v1.2. Could that be the cause? #2) The links at the top (Blog, Members, Groups, Blogs) don\’t work properly. They are all formatted as username.domain.com/members instead of domain.com/members etc…

For #2, is my beta site messed up? Is it supposed to rewrite those to the proper URL or is that behaving normally? If that is the case, I will need to redo those links, correct?

just remove them in your theme if you don’t like them. Or – you could use the author’s avatar instead.

As per Andy’s comment, http://www.beerandblog.com/wp-content/bp-themes/bpmember/css/loader.php is returning 404. Usually if it’s a permission on the file system, you get a different error code sometimes.

Does that file exist in that path when you look in your FTP?

which user and which groups have permissions ?

permissions should be 755 and the users should be no root