So that is out of the question. Lets say if i get a person that is really putting effort into their blog. I Would like have it where when i fill like they are a real asset to our website, i can contact them requesting if they had their own theme they would like to use with their blog and if they do, they can send me the theme and i can add it so it will only be available to their site and no one else?
True there is that background image plugin but the question was “theme like twitter” and so far nothing like that exists for profiles
@tommyhoang– you don’t need step 2. You just need to place the code from step 3 into your header.php file where you want the widgets to show up. This article might help as well: http://digwp.com/2010/02/how-to-widgetize-wordpress-theme/
@sbruner, is that article up to date for the current version of wordpress and buddypress? I created a child theme and made a blank functions.php file and added the codes from step 1 and step 2. now Im a little confused with step 3, where am i suppose to put those codes and am I suppose to rename my functions.php file to page.php?
If you want to uninstall BuddyPress later, you’ll go through this process https://codex.buddypress.org/buddypress-site-administration/deleting-buddypress/
As for BP Template Pack plugin, you’d have to delete the plugin and then delete the BP template folders/files copied over to your active WP theme folder when you went through the BP compatibility process.
WP/BP versions? Could be that you have outdated theme? Change to bp-default theme and check whether mentioned misbehavior is corrected.
aaaa….. IC what’s going on here…. previously on child themes you would include the BP default theme as an @import at the top of your child theme style.css this is no longer neccesary with the way BP 1.5 loads the style. Just removed the reference and everything works great….
For multisite install, only Network Admin can upload and enable themes for activation in different blogs. This is to provide a level of security for the whole network. If you allow users to upload themes, your installation will surely be hacked.
Appreciate the response John, so just to clarify.
All child themes for Buddypress should reference their “style.css” using wp_enqueue_style() rather then the traditional WP style of including the style reference in the header.php file?
I believe you would have to give them some administrative rights. Try one of the role defining plugins that let you dictate EXACTLY what each user role is capable of. Try “Capability Manager”, if i recall it is pretty good.
So the code in my previous post doesn’t show. Since then, this is what I’ve included in my child theme’s functions.php file (and I have NOT done an @import within my style.css file):
http://chopapp.com/#2s3gjzs6
This seems to work. Is the syntax for enqueuing the style.css file correct? Is this the right way to do it? Thanks.
By the way, I see that other folks are able to paste code into the comments/replies. I don’t know how to do that, hence the link. Could someone enlighten me? 
Yes, the multisite where users creates their own blogs.. i would like to allow them to upload themes for their own blog.
Using @import in combination with linked CSS causes CSS load order issues, as the HTTP requests are not completed in sequence.
I would suggest researching and using the WordPress API wp_enqueue_style() to better avoid the fouc.
I’m going to assume you mean under WordPress not BuddyPress specifically and using Multisite? Is that right? If not what do you mean by theme?
@gregfielding: Could you let me know what step I’m missing or applying incorrectly? I have the same issue that you mentioned in your original post. So, after reading all of the recommended material regarding creating a child theme for BP 1.5 Beta 1 thru 3, the styling in my child’s style.css file still won’t be recognized (And I’m still in a slowly clearing fog. Too slow.). Here’s what I did:
1. Created my child theme folder,
2. In that I created a blank functions.php file and then added to it:
`<?php
if ( !function_exists( ‘bp_dtheme_enqueue_styles’ ) ) :
function bp_dtheme_enqueue_styles() {}
endif;
?>`
3. I reloaded my browser, and the default styling isn’t there. Great.
4. Now, to my child’s style.css file, I do what I’ve done before and add the @import code:
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
5. I did Step 4 because I want to load and override the default styling, not start from scratch.
Could you point me in the right direction? Thanks.
oh and you could use theme switcher plugins to change a site wide theme to predefines styles. Create little thumbnails like twitter and when user clicks image it switches to that theme/style.
I’ve got default working now. The WP plugin “Nivo Sider for WordPress” breaks pretty much all interaction just by being activated. I’m guessing it’s 1 or more conflicting .js files. I have the same plugin working fine with BP 1.2.9 but the plugin has a number of issues, definitely don’t mind using a different, more friendly slider plugin.
There isn’t a custom profile plugin at the moment. There exists a group css plugin that could be used as an example in creating your own plugin. https://wordpress.org/extend/plugins/buddypress-group-css
Another option is adding profile fields and then mapping that info to CSS. See this forum topic: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/css-for-member-page
when I get a chance, getting plugins updated first and then fixing the themes.
Not with BP-Default, you could add the functionality to your own theme.
If this is the same Speed theme I’ve seen before, double-check if the theme has been updated to be compatible with BP 1.2.9 and again if it’s the same Speed theme I’ve seen before, you do not need to install the BP Template Pack plugin for this theme because it already contains BP Template files. Therefore errors come up because of outdated theme and installing BP template pack for theme which already has BP template files – outdated those may be.
Had I read the second page, I probably wouldn’t have needed to make this post. 
Should have read ahead I guess. 
