BuddyPress.org

Seems like this problem hasn’t gone away on 1.7.1.

I’ve tried the above solution with little joy.

1. My customers setup is a sub-site from their primary site.
2. I tried disabling all the plugins except for BuddyPress. No joy there
3. Tried adding define(‘BP_ENABLE_MULTIBLOG’, true); to wp-config on the sub site and primary site, no joy there either.

Any suggestions??

I use a child theme derived from the default team, only changing the visibility of the menu as explained in //https://buddypress.org/support/topic/resolved-hiding-navigation-links-for-buddypress-pages-for-non-registered-users/
When I use the default theme as such, it still doesn’t work.
I also tried to change the user’s role to author; still no luck…

@designloud What theme are you using? What plugins are activated? First time I’ve seen this issue. Change to BP Default theme and check if issue is resolved. If not, deactivate plugins except BuddyPress and then activate the other plugins by batches to check which is causing the issue.

I like an issue that resolves itself 🙂

Presuming http://themeforest.net/item/onecommunity-buddypress-theme/3713046 is your theme, have you tried upgrading it to the latest version – v1.1.9 ?

If that isn’t the problem and as this is a premium theme I suggest you ask on http://themeforest.net/item/onecommunity-buddypress-theme/discussion/3713046 or http://support.diaboliquedesign.com/ ?

Good luck with geotheme.

Hi, @sarathbabu_k,
I updated the BP Group Documents for BP 1.7.
You can downloaded from lenasterg.wordpress.com/2013/04/30/buddypress-group-documents-for-bp-1-7-and-wp-3-5-1/.

What’s the end of the ‘story’?
I have the same problem:
Android 4.0.3, wp 3.4.1, buddypress 1.7 default theme.

I can just add a piece to the jigsaw… FIrefox for Android on mobile works perfectly…

Lets focus on your site first as each site is different and css / html validation is just a guide due to html5 and css3.

Ultimately the best way is to either save/ print the list and work through each.

You are going to run into some issues where the validator thinks something isn’t valid and it’s a CSS3 technique it doesn’t validate.

Personally, my focus on validation is always on the html validator first and then the CSS validator as a sanity check because so many things won’t pass that are valid just newer CSS.

http://validator.w3.org

Any validator should only be a guide not a rule book.

@Sorensen84 can you confirm you are using the default templates – I think you are from what you say. I’m thinking you are saying that here:

I use the buddypress default template. I got to problems, I hope you can help me solve.

If this is the case then it’s not a custom theme unfortunately @Chouf1.

The next candidate for an issue would be on plugins. Probably good idea if you can to strip back see if that helps by adding one by one.

Since BuddyPress 1.7 you don’t only have to use a BuddyPress theme so you can use any theme from https://wordpress.org/extend/themes/search.php?q=buddypress and also https://wordpress.org/extend/themes/. I’d always say ideally you use a theme that’s designed for a community but either option gets you up and running.

Also worth looks are:
http://infinity.presscrew.com
http://3oneseven.com/buddypress-themes/

As far as buying in theory again every theme that works for WordPress works but BuddyPress specific themes you can get a number of places such as (not exhaustive list):

• BuddyBoss: http://www.buddyboss.com
• Luca’s theme: http://luca.untame.net
• Mojo Themes: http://www.mojo-themes.com
• Press Crew: http://shop.presscrew.com
• Theme loom: http://themeloom.com/themes/pure-theme/
• Theme Forest: http://themeforest.net/category/wordpress/buddypress
• Themekraft: http://themekraft.com
• WPMU DEV: http://premium.wpmudev.org

Please give more details before asking for help !
https://buddypress.org/support/topic/when-asking-for-support-2/

BP use the standart WP process to upload pictures. The default user avatar is set in the WP settings > discussion where you can choose between different avatar services. The default avatar shipped by BP is Mystery Man.

When a custom user avatar is uploaded by a member, the picture goes to wp-content/uploads/avatars/ into a folder named by the user ID. The original image is handled by the process to result in 2 different size, and BP rename each file to something unique with a MD5 name, and a human comprehensive name, such as c3f55cb7f3beaa22f7463132f5e0878d-bpfull.jpg and c3f55cb7f3beaa22f7463132f5e0878d-bpthumb.jpg

Internally BP use 3 default sizes for the user avatar: 50×50(small), 150×150(full) and 450×450 (max original file size).
These sizes can be changed. Read here how: https://buddypress.org/support/topic/avatar-sizes-in-1-7/

Each user can modify his profile and change his avatar so many times he want. The avatar upload process contains also an avatar cropper. The default cropping size is related to the avatar define “full”. By default it’s 150×150 and the original image is fixed to 450, even if it’s bigger on the user side.

Depending the placeholder of a profile avatar, those size are adapted to fit the template part fixed in the theme you use. On activity stream under bp-default theme, the avatar is 20×20, on members directory it’s 150×150, etc

The signup process is conditionned by registering. As long as a new user has not activated his account, he cannot upload or modify something, or even loggin to the site. That’s why there is no option for pics at this stage.

And yes, you can embed a profile pic into a sidebar or any other place. But this is only possible if you’re familiarized with BP and if you have some basic PHP knowledge.

@sorensen84

read this first please:
https://buddypress.org/support/topic/when-asking-for-support-2/

Your problem seems to sit into your custom theme. Read on codex about templates.

BuddyPress Codex

@praisehim,

read here first: https://buddypress.org/support/topic/when-asking-for-support-2/

@flixya4gabby
Unfortunately your going to have to use the process of elimination by activating each plugin individually and testing against it until you narrow it down to find the plugin that is the culprit. Once you find the plugin that is causing the issue the go to the plugin authors support forum and report your findings.