BuddyPress.org

Firstly I notice that your Avatar cropper javascript is failing on registration. Also looks like bits of your site are missing, and messing with the BuddyBar (sub-sub menus aren’t appearing on hover.)

Otherwise, it’s working the way you have it setup. If what you’re asking is “why doesn’t my home theme look like testbp.org” it’s because you didn’t change your active home theme in WordPress.

Not sure what’s up with your member theme though. Might be missing some files or have some funky CSS or JS somewhere. Haven’t really looked into it for you.

The Northern Smurfs called a certain object a “bottle smurfer”, while the Southern Smurfs called it a “smurf opener”.

Language customization is subtly different from language translation but both share similar localization processes, using the same tools.

( https://codex.wordpress.org/Localizing_WordPress & https://codex.wordpress.org/Translating_WordPress. Google for more)

Of course, as Lance accurately stated, using dedicated software is overkill if your intention is to change a small set of frequently used words site-wide (turning “groups” into “teams”, “members” into “players” and so on).

In which case I’d go for the “slugs” method, as suggested by Andy Peatling, rather than tinker with the language files.

As always, scale matters.

If you are interested in managing one or more custom language versions, or if you find yourself willing to change more stuff as it comes, I strongly advise you to consider the software option.

It’s a personal investment which requires you to do your homework and learn to organize your projects accordingly but the learning curve isn’t that steep, and it will guarantee you less white hair in the long run.

PoEdit is a good choice, giving you the full benefit of a precious asset: translation memory.

Once installed on your PC, it creates and maintains databases for each translation project – its original purpose. A feature that can be put to good use for language customization.

Its rather straightforward user interface lets you focus on the language changes you want to make, with a built in “search” feature to locate words or expressions.

There is no built in “find & replace” feature as software translation is primarily based on strings and not single word occurrences, which can be located in different strings with different contextual meanings.

If you really want to batch-replace words, you can achieve this using a text editor like Notepad++. Proceed with extreme caution, though: unexpected replacements using this method are frequent, that you can’t always undo except by hand, which defeats the purpose of the whole process.

Since language files are usually modified with each new release (added strings, modified strings, different string locations…), you’re also better off handling language file updates that way, keeping the language customization logic independent from the file itself, in PoEdit’s TM (translation memory) safe at home on your PC.

When upgrading BP, it will spare you tedious language files comparison and copy-paste hell in a river of strings, and will do the job with more accuracy.

A single mistake in a modified language file can generate cryptic errors which you don’t want to start tracking and debugging in 3,000 + strings distributed in multiple language files.

PoEdit gives you the ability to manage multiple language files using a single TM database (or as many as you wish).

This is especially useful when you know that the number of language files to be handled gets larger as your platform grows (plugins, themes and templates sometimes have their own – and should).

Using PoEdit will give you the required semantic homogeneity among all language files belonging to the same project, seamlessly.

This is where translators make significant productivity gains. And so can you.

What is more, the software approach scales nicely:

If you want to leverage your community’s knowledge for language customization – Klingon, Smurf, slang, professional jargon, secret dialect, whatever… – you may want to install Pootle

( http://translate.sourceforge.net/wiki/ ), an open source collaborative translation platform that does the same as PoEdit, on your server, and upload the languages files for collective customization – the scenario is yours.

Are you using DeannaS’s blog defaults plugin? It has an options page. The default new theme section box is at the bottom.

@Evvscuba

I know that many others who are using IE7 do not have this issue.

A few suggestions:

1. Are you using a custom theme? If so, switch to the standard, BuddyPress themes and see if this behavior still exists.
2. If you are running your domain under PHP4, try upgrading it to PHP5.
3. Check which version of the GD module your PHP install is running. Internet Explore had some known issues with earlier versions of the GD library.

You have to comment it out, in each file, the avatar appears, in the members loop for example:

filename-members-loop.php in the skeleton member theme line 26. It should look like this after commenting it out:

“><? //php bp_the_site_member_avatar() ?>.

Now you have an empty link, thta points to the profile.

The Css way:

.item-avatar{diplay:none}

visibility:hidden.

Maybe it can cause errors in old Ie Versions, so I would recommend the first solution.

Yep, still works. I assume we\’re talking about the \’buddypress\’ graphic in the top-left of the \’buddybar\’.

In my theme\’s functions.php:

remove_action( \'bp_adminbar_logo\', \'bp_adminbar_logo\' );

And in my CSS:

#wp-admin-bar ul { margin-left: 0 !important; }

If that doesn\’t work before you, it\’s because you\’re putting it in the wrong file. If you\’ve got it in bp-custom.php, then it\’s getting read before the buddybar menu items are created internally – therefore it doesn\’t remove them as it needs to happen afterwards.

Burt Adsit has a suggestion on the Trac for a bp-custom-after.php which would be an appropiate place for this sort of override. In the interim, I suggest you make a file \’z-custom.php\’ in /mu-plugins/ and put the above line in.

Andrea, I am using the blog defaults plugin but I don’t see the option to set a default user theme. Can you point me to a resource? Thanks.

i have upgraded to the latest trunk and still the same. also deactivated pretty permalinks. have not edited anything on theme. this is my last one issue. help please?

Im working on three bbpress themes for original buddypress theme. Sorry my english suck!

Maybe you know how to fix my theme. The adminbar in my theme is showing but only a grey rectangle. So, these link just it\’s a example of my progress. But i\’m not programmer only entusiast!

how about commenting out the avatar functions from the theme file? You may also need to customize the “why not use gravatar…” blah blah message as well.

Check if you have funtions.php in your theme

https://buddypress.org/forums/topic.php?id=2606

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.

Lo.

> Why is it when I add a page to my WordPress site, it doesn’t show up in my BuddyPress navigation?

Because that’s just the way the default home theme is written. The items listed on that menu aren’t ‘Pages’ in the WordPress sense, anyway, so it makes little sense for the default, out-the-box BuddyPress theme to do that.

The bit of code you’d need to change (or to add in your custom/duplicate theme) is in header.php. Where you see:

<ul id="nav">

Add this underneath:

<?php wp_list_pages('title_li=<h2>Pages</h2>' ); ?>

Documentation for that function is at https://codex.wordpress.org/wp_list_pages

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

function bp_show_home_blog() {

......

}

John,

Just checked out delsolownersclub.com. Really like the way all parts of the website are well integrated (including the forum)

The bp home theme is entirely optional. You can use your preferred wp theme for all the usual things and integrate whatever selected features what you want into the theme. Or none at all. The member theme is still available through the top admin bar.

See this in the codex: https://codex.buddypress.org/getting-started/using-the-buddypress-themes/

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

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.

It used to be that wp didn’t consider the member theme a theme at all. It still doesn’t. Andy is temporarily tricking wp by trapping a couple of filter calls that wp uses to find the current theme. Looks like when we are in the member theme wp temporarily thinks it’s the current theme.

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.

Once again the major restriction I’ve found is that the functions.php files in both the member theme and the home theme *must* register the same sidebars. They have to match. The member theme can not independently register a sidebar that doesn’t exist for blog id 1.

I can live with that.

That\’s how I got the member theme to display a sidebar using the plugin-template.php and plugin-sidebar.php templates. You\’ll have to modify the directory templates to display a sidebar if you want them to show up there. All you have to do is include the sidebar div like:

<div id="sidebar">

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('member-sidebar') ) : ?>

<?php endif; ?>

</div>

I stuck that each directory’s index.php template and modified the css to format things properly. Giving the new sidebar some room.

The last time i fooled around with the member theme at the sidebar/widget level I couldn’t use dynamic sidebars. It was just flatly impossible. Seems things have changed. I’ve gotten them running in the member theme but have only been able to select sidebars that are defined in whatever theme I have defined for the wp blog id 1 theme.

Like I say it’s been quite awhile since I looked at this problem and to my surprise it actually works now. Sort of, with restrictions, kinda. Perhaps I’m just doing it the wrong way. I’ll tell you how I got it done.

The problem really is that the member theme isn’t a real registered theme. You only get one theme per blog with wp. That one is the one activated for that particular blog. I currently have the bp home theme registered for blog id 1. It registers 3 sidebars and those are the ones that are available for the theme.

The bp member theme doesn’t register any sidebars by default and doesn’t include the default sidebar template file either. I suggested above that you use the sidebar template from the home theme. That alone was not enough to get widgets into the member theme. I stuck the normal code for using dynamic sidebars into the sidebar template like this:

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar() ) : ?>

<?php endif; ?>

That got me exactly nothing. So I included sidebar registration code in the member theme’s functions.php file where it normally gets put.

register_sidebars( 1,

array(

'name' => 'member-sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h2 class="widgettitle">',

'after_title' => '</h2>'

)

);

I named my new sidebar ‘member-sidebar’ thinking that it would show up in the back end of wp where I could then register some widgets for my ‘member-sidebar’. Nope. The ‘member-sidebar’ doesn’t show up.

I did get the first sidebar to display in the member theme though. Whatever was defined in the wp theme as the first registered sidebar, showed in the member theme. Well this is progress ‘eh? Something is showing in the member theme. I had to mod the member theme css to have it appear though. The #sidebar div isn’t in the base.css for the member theme. I modified the #content div in base.css and included the new #sidebar div.

Still with me? Now I have *a* sidebar with widgets in the member theme. Well I don’t want just any widgets, I want to specify what specific widgets get displayed right? Anyway I finally figured out that I have to register *all* the same sidebars that the wp theme on blog id 1 register. I copied all the function.php sidebar registration calls from the home theme’s function.php and stuffed them into the member theme’s function.php.

Works like a charm. Now in my member theme template file plugin-sidebar.php I can specify which sidebar I want to display.

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('blog-sidebar') ) : ?>

That above just happens to be the one I chose to test that I could have any sidebar I wanted in that template. Works. Well, I didn’t want one of those sidebars at all. I wanted a separate sidebar for my member theme. ‘member-sidebar’. That would not show up until I included the registration function in both the home theme and the member theme. Then I get to change the code above to be ‘member-sidebar’.

Like I said I may be doing this all wrong and hope that someone comes up with a better solution but this is the one that works for me.

1) Add another register sidebar call to the wp theme running on blog id 1. Like this in your blog id 1 functions.php file:

register_sidebars( 1,

array(

'name' => 'member-sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h2 class="widgettitle">',

'after_title' => '</h2>'

)

);

I stuck that under the other 3 calls in the default home theme.

2) Copy *all* the register_sidebars() calls from the home theme functions.php file to the member theme’s functions.php file. They should look the same now when it comes to sidebar registration calls.

3) Copy the sidebar template file that is distributed with the home theme plugin-sidebar.php to the member theme dir.

4) Modify the plugin-template.php file in the member theme to load the new sidebar template also.

<?php get_header() ?>



<div class="content-header">

<?php do_action('bp_template_content_header') ?>

</div>



<div id="content">

<h2><?php do_action('bp_template_title') ?></h2>



<?php do_action('bp_template_content') ?>

</div>

<?php bp_get_plugin_sidebar(); ?>

<?php get_footer() ?>

That’s my plugin-template.php file that lives in my member theme.

5) Modify the plugin-sidebar.php template in the member theme to look like this:

<div id="sidebar">

<?php do_action('bp_template_sidebar') ?>

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('member-sidebar') ) : ?>

<?php endif; ?>

</div>

6) Modify the member theme css to include the new #sidebar div that didn’t exist before. I just did it this way for the content and sidebar divs:

#main #sidebar{

margin-left:70%;

margin-right:20px;

}

#main #content {

float: left;

width: 65%;

position: relative;

padding: 2em 3em;

}

Use whatever is appropriate for your member theme.

7) Fire up the back end of wp and add widgets to the ‘member-sidebar’. Enjoy your new member theme sidebar.