Looks promising. :thumbup:
I also experience blank pages frequently at BuddyPress.org although I use many browsers. This post is made because I am a big fan of BuddyPress.
There are already good themes for buddypress. I guess you haven’t searched enough. Core teams should focus on development, not themes. Since 1.1 theme design got much easier than before, so any wordpress theme designers can design.
Yes! That was my idea too, but in one moment it seemed silly.
Since there are lot of hard-coded links without apply_filters(), I can’t see what’s other solution.
I updated to 1.1.1 and still having the same issue. Has anybody else noticed that this site Buddypress.org is not working too? When I log in and go to any of the links in the top admin bar they all re-direct me to the front page.
I don’t understand question 3.
While colour is of course a huge aspect of design and can make the difference between a confusing page and a rational page or a readable page and an unreadable page… I’m not convinced that changing background colors or navigation bar colors does much to improve one’s sense of place on a website. It might actually confuse people. You are assuming they will form the connection that green = profile… blue = members… etc. But it may be just as likely that they will say to themselves “What the… why do the background colours keep changing?”.
Some things people have come to understand and even expect perhaps are left hand navigation bars and breadcrumbs. However, that really only makes sense on a site that’s all about hierarchy. Sites like BuddyPress and Facebook etc. are not organized in that way… they are more about functionality and activity and relationships. There’s no deep hierarchy. Although there could be within your posts and pages (the Blog section).
Anyway, if you’re concerned about them knowing there they are… perhaps just redesign the main navigation bar to stand out more. Also, instead of two side-by-side bars (like on the Profile) a single bar with break-out navigation would be more conventional. All of the above would require (ideally) good design skills, HTML/CSS, maybe a little PHP… and an understanding of usability.
Ya… I’ve been getting blank pages galore on here lately. I’m assuming it’s a server issue.
That’s where you and me and the millions of HTML/CSS coders out there come in. Theme development is the last thing I would want the BuddyPress team wasting their time on. Their limited development resources need to be focused on functionality. As besides that… the default theme is already pretty awesome if you ask me. If you want to see an ugly default theme (that is impossible to redesign in a meaningful way)… look at Elgg. Ick.
I find it all somewhat confusing as well… First Name, Last Name, Nice Name, Username, Email… too many options. I think it’s much better from a usability point of view to sign in using your email address… because users don’t remember usernames. But that has nothing to do with BuddyPress. The way login works is a WordPress thing I presume.
That’s fast! (trying to send this the second time, I’m getting blank pages a lot when posting at the forum)
Hi Simon,
I tried it yesterday, but without success. The cache remains active. Hm, or needs wp sc the url of the link?
Example:
https://buddypress.org/forums/topic/
/forums -> will not cache any files
Thats right?
thx
Markus
Very nice Jeff, very nice and many thanks 
Does having the Buddypress core activated disable WPMU’s auto upgrade feature. Because I have a problem where my WPMU is stuck on an older version and the auto upgrade link at the top doesn’t appear. I would prefer to do an auto upgrade than a manual one.
Did you had to filter lots of hard-coded BP links to append ‘?lang’ ?
Or you are using some stripped down version of BP?
We used jquery to append
Having javascript enabled is essential for our site, so we were okay with that approach. Since our site runs on BP1.1 I am very eager for your update. I did a quick trial and error and see how it would handle BP1.1 out of the box, but it kinda choked for now.
@ chris
it’s better to put such reflections on the trac to ensure a possible correction in next version
I did…
https://trac.buddypress.org/ticket/1179
Complete it if necessary, my english is not the best
@Mariusooms
Thank you for registering.
More activities we get on the demo site, more things we can cover.
I saw topic on wpml.org, it is good that you manage to handle plugin, since wpml on wpmu works as install per blog.
Did you had to filter lots of hard-coded BP links to append ‘?lang’ ?
Or you are using some stripped down version of BP?
@Erich73
Thanks for suggestion, that could be done in near future.
For anyone following this and hoping for an answer, I came across a similar discussion:
https://buddypress.org/forums/topic/surprising-avatar-behavior
Andy said, “The quickest option is to remove the /wp-content/blogs.dir/1/files/avatars/ directory and let BuddyPress rebuild your avatars as people upload again.” Also, Andy recommended that you check your permissions.
I did both of the above. I removed the avatar folder which did remove the mixed-up avatars. However, BP still would not correctly display newly uploaded avatars. It said the file was uploaded correctly, I see the file in the avatar folder (both bpfull.jpg and jpthumb.jpg) but BP is still displaying those files as a broken link.
Still hoping and looking for a fix to this as more and more people are being affected by it.
We have the same problem. I think, it’s a problems with the nice-names in the profil of WordPress MU. If the username (for example:timschmi) and the nice-name are the same, there is no problem. If the nice-name is different (for example:timschmidt) buddypress will link to timschmidt and not to timschmi. You can see it if you roll over the links.
Found a solution.
Added
define ( ‘BP_ROOT_BLOG’, ‘2’ );
To wp-config.php set the blog that should run BP. In this case, blog id=2
Found it at:
https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/
Thank you for the great documentation.
Exactly Andy. That’s my issue. Hacking the parent function.php file is easy. But I don’t want to do that. So I created a function.php file in my child theme but the unregister_sidebar() function doesn’t seem to work 
I suspect this is a WPMU thing… not a BuddyPress thing. Here is the code I added to function.php in my child theme. Should work. Doesn’t. I’m at bit of a loss. I tried adding different priority levels to add_action() and they had no effect.
<?php
function remove_sidebar() {
unregister_sidebar('third-section');
}
add_action( 'admin_init', 'remove_sidebar');
?>
p.s. https://codex.wordpress.org/Function_Reference/unregister_sidebar
4727579Inactive
In your bp-sn-parent theme folder look in functions.php and delete the code in there. Then, in home.php delete the appropriate code. You can re-name them in functions.php as well. Here is one I’ve added as an example (it’s also the code you need to delete from functions.php):
register_sidebars( 1,
array(
'name' => 'groups-page',
'before_widget' => '<div id="%1$s" class="widget %2$s">',
'after_widget' => '</div>',
'before_title' => '<h2 class="widgettitleevents">',
'after_title' => '</h2>'
)
);
This is the code you need to remove from home.php:
<div id="third-section" class="widget-section">
<?php if ( !function_exists('dynamic_sidebar')
|| !dynamic_sidebar('third-section') ) : ?>
<div class="widget-error">
<?php _e( 'Please log in and add widgets to this section.', 'buddypress' ) ?> /wp-admin/widgets.php?s=&show=&sidebar=first-section"><?php _e( 'Add Widgets', 'buddypress' ) ?>
</div>
<?php endif; ?>
This should answer your question. 
I could really benefit from learning how to do custom pages in 1.1 as well. Has anybody figured this out yet?
