[@johnjamesjacoby Keymaster 17 years, 6 months ago]

I actually linked to the function reference in my post above yours.

That function is a WordPress function to check and see if the user browsing the site is logged in or not. It will return true if yes, false if no.

if (if_user_logged_in())) {

[..your custom menu item code...]

}

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Use the normal WordPress function is_user_logged_in().

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Oh I think I see what you’re saying. You want to commit your changes to the SVN yourself?

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

You want to hide the entire BuddyBar when they’re not logged in, or only the items you’ve added in bp-custom.php?

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

It’s not really a core hack. Functions.php is meant to be edited.

The BP Home theme is just a mask over WPMU’s eyes. It uses functions.php to play some tricks on WPMU to allow it to hijack some urls. All that you’re doing is hardcoding it yourself.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

The POT file should be in bp-languages.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Remember also, that the navigation in header.php has NOTHING to do with WordPress pages. They are hard coded to the BuddyPress predetermined hi-jacked URLs.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Inside your functions.php for your home theme, comment out:

function bp_show_home_blog() {

......

}

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Hardcoding them into the sidebar is the only way to have them not be editable for a user.

Andrea_r is also correct from page 1 about the user blog edits. I’ve had that exact setup over at http://delsolownersclub.com working for about 3 months now smoothly and seamlessly (doing some cross posting in two topics now.)

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Like Andy said, the “Home” theme is really intended only for the “Home Blog” or the main blog that your website is responsible for. It’s intent is similar to a “portal” page for those of you familiar with phpNuke, vBulletin, etc…

Think of wordpress.com…

There’s a page there that shows all sorts of SITE WIDE content. Then you can drill down into users blogs, and see their specific blogs and themes. Exact same idea with the home theme.

Using the Home theme as a user blog will result in errors, because the “Members” and “Groups” and “Blogs” links don\’t exist under sub domains/directories.

For a “seamless” type of interaction, you will want to make a duplicate of your “Home” theme, call it “User”, edit the style.css to give it a new name, delete home.php, and edit the header.php file to use$bp->root_domain in place of get_option('home')

This is what I did for http://delsolownersclub.com. You’ll notice that the user blogs look just like the home blog.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Alrighty…

Create 3 pages in your main blog. Name them “Root” “Blog” and “Home” (you can name them what you want, but this way they have distinct purposes.)

Set “Root” to be your static homepage.

Set “Blog” to be your blog page.

Rename “home.php” to “homepage.php” and at the top if it put

<?php

/*

Template Name: Home Page

*/

?>

Edit the “Home” page, and in the “Page Template” area, select “Home Page”

Viola? Hopefully.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

This makes sense, because like you said above, the Member Themes aren’t real WordPress themes; BuddyPress just muscles itself in and takes over the place. And as long as the member theme functions.php registers a sidebar with the same name, WP doesn’t know the difference and loads it up.

It’s posts like this, Burt, that lead me to believe that there’s a whole lot of progress that will be made in modifying the Member Theme area.

Good post, A+ for the day.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

If you don’t want to believe me, that’s okay, but that doesn’t make me any less right.

Download

bbPress .9 may integrate with BuddyPress 1.0, but it isn’t the recommended version and it will be more difficult to make them work nicely together.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

I’m going to close this up since you opened another topic about your next issue.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Should be using bbPress 1.0 alpha 6.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Right now only individuals can edit their own profiles. Admin’s cannot edit others’ information through BuddyPress.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Kitwit, I think you’re a little confused… It’s working exactly like it should.

The directory pages are the pages that show the A-Z options on the top. The profiles are just profiles. They reside in members/username, but viewing a profile isn’t the same as viewing a directory of many users.

When you turn on Extended Profiles, it will totally ignore any of the admin area WordPress profile fields, and wait for you to create your own profile groups and fields. Extended Profile information can then be edited through BuddyPress on the front end of your profile area, exactly like you can do here.

When you turn off Extended Profiles, BuddyPress will fall back on the WordPressMU user information found in the admin area (if you have the BuddyPress setting turned on for it to do so.)

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Dantes, if you view the forum via the groups page, then yes it will show up integrated into the BuddyPress group area. Otherwise, bbPress is its own application with its own plugins and theme files. You would need to create a theme to mimic the style of the rest of your website.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

When you say “public profile” are you talking about the “member directory?”

Extended Profiles allows you to create whatever kind and type and name of field that you want. That information, when filled in, will then appear when viewing each members personal profile.

You are free to customize the directory template files to accommodate your needs.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

That’s pretty odd. I’ve two live setups and one local one and cannot reproduce this.

Are there any additional plugins installed at all?

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

The extended profile plugin does exactly what it sounds like you’re looking for, so why do you have it disabled?

I guess I don’t understand exactly what you’re trying to do.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Well, you turn off the static front page for starters.

If what you’re saying is that you want your home page to be static, and have /blog be your blog, you can just customize home.php in your theme directory and have that be your home page?

Otherwise, you’ll need to rename or remove home.php, set your static front page, and create a page called “Blog” and set it to be your blog.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Thanks for the heads up!

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Hmm…

Can you check with your web host and ensure that they have XML RPC enabled on your PHP install?

Otherwise you can make yourself a <?php php_info(); ?> file and check for yourself.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Easiest way is to edit the header.php files of your Home and Member themes.