It’s not a hack just sounds like you haven’t added ‘buddypress’ into the list of tags in the style.css head meta? without buddypress in that tag list the warning is displayed.
If you are referring to the buddypress default theme ( /wp-content/plugins/buddypress/bp-themes/bp-default/ ) it already has the necessary `Tags: buddypress` near the top of the style.css file……
https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#Final
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/
I know there is a hack to remove that warning for “your themes not compatible” I know my theme is because all I did was take the default theme, completely change it to the point where it was a whole new theme and upload it to the default WordPress theme section and select it.
Ideas?
Just got back in. All tickets listed at this time in https://buddypress.trac.wordpress.org/ticket/3241 are either being worked on and many have already been fixed. Kudos to all 
@adamkb.balan
That’s not a plugin, it’s a standard Buddypress widget. Look under “Widgets” in your WordPress backend and you’ll see the one called “Who’s Online Avatars”. Just drag that widget to your sidebar and voilà!
Howdy,
How can I restrict a WordPress user with role = X to be a member/participant in Buddypress?
My objective is that certain member roles do not have a Buddypress profile and do hence not show in the Buddypress member list. These roles could still sign in, and for example access pages and posts restricted to logged in users, but they would not be able to participate in Buddypress (create a group, write in forum, etc.). They could only read Buddypress content and edit their profiles, which are not visible by others.
Example:
* User role = Editor does not get a Buddypress profile, and Editors can therefore not participate in Buddypress Groups, Forums, leave comments, etc. S/he must upgrade to…
* User role = Member has a Buddypress profile and can participate in Buddypress activities
Can this be done? If yes, how?
Thanks!!
@karmatosed @mercime @bowromir @hnla and anyone else interested in contributing to BP-Default 1.3:
Mercime has generously done a wp.org-style theme review of BP-Default. I’ve created tickets on trac. The master ticket is https://buddypress.trac.wordpress.org/ticket/3241
I may add a few more tickets once Mercime has clarified a few details. If you are interested and will commit to resolving one of these, please go into trac and “accept” a ticket so that everyone can see that you have assign it to yourself. If it’s a big visual change, I suggest making a mockup picture and attach it to the ticket so that everyone can give feedback.
If I can be of any help or guidance, I’m on skype as “djpaulgibbs”, on IRC and frequently check my email. Don’t hesitate to get in contact
@hnla I guess I’m not sure what you mean? I have an ftp server that serves http://network.theunsignedsounds.com and I’ve installed wordpress under that domain. I wondered if I added you to the site, would you be able to pinpoint what the problem is? I’m at a complete loss here and have tried uninstalling/reinstalling a few times to no avail.
Hey, I just keep him well fed when he does this. 
@Andrea_r – BP MultiNetwork is awesome news indeed. Thank you and wpmuguru
== move the Activity, Registration and Members folders to TwentyTen theme ==
You don’t “move” the BP folders to your theme, you need to
1. have Twenty Ten theme activated
2. install the BP Template Pack plugin https://wordpress.org/extend/plugins/bp-template-pack/
3. follow the instructions of the BP Compatibility Process https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
If you need some pointers for the whole process, read this – https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/
Whoa and here I was convinced they didn’t even use wordpress. hard to find in the source.
More news here guys:
http://wpmututorials.com/news/new-features/multiple-buddypress-social-networks/
Since Ron is the one behind getting this to work, keeping tabs on our WPmu tutes blog would be the place to ask first.
@ecomonkey – those directives are put in there when you enable the network to start. you remove them to help with multiple network. (that’s the “site” value. each site in the code is, in fact, a network)
heya guys
I followed several guides to make integration with my current theme to buddypress
i’m now stuck on this step:
http://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
I couldnt understand exactly what to do (im not a php coder- if its related to php )
anyhow
those are the two related files, if you can please assist and give me an example i’d be more then happy
big thanks!
org theme template page file: http://www.scribd.com/doc/55880135/Index
the file that needs to be edited: http://www.scribd.com/doc/55880166/Page
@phoenixology – you should go to your frontend Group ADMIN and after you click on it there’s an option DOCs (you can’t see DOCS unless you click on Groups ADMIN , there is a checkbox asking you if you want to have DOCS enabled , if you confirm YES and say minimum role who can create DOCS it will show you DOCS for all other people – registered etc . then you can create your docs , hope it helps . creating docs has nothing to do with WORDPRESS ADMIN DASHBOARD , there when you have created them , you can manage them (I am learning admin dashboard too –
Thanks @djpaul,
Yes, I remember that. Just trying to bring it back as an option to the site admins and allow them to extend it.Going to put a patch later today for that.
Re query: Yes, the query count is still applicable to bp trunk #4396. It is only in the case of multiselect box where the query is done for each item in the list. will look into that and put some patch.
@doctordr, The front end posting capability is coming as part of wordpress upgrade in near future(hopefully). They are making the quickpress available to front end. checkout this ticket for details(It was dropped in 3.1 and let us hope it comes with 3.2)
https://core.trac.wordpress.org/ticket/14966
A huge limitation of BP at the moment (and WordPress in general) is the lack of front-end posting and moderation. I’ve had to hack this into my current site by using conditional user level statements to present a restyled admin screen to users – one which looks identical in terms of header, footer and CSS to the front-end – and unsets or removes redundant menu items. The way around this would be to modularise certain admin functions (posting, comment management) so that theme designers have flexibility in the way they are presented and integrated on the page with other functions. This could be achieved with shortcodes or even widgets. I can see no functional reason why users should be sent to an un-themed back end to post new blogs and I’m sure it’s holding BP back as the choice for many sites.
Unfortunately I can’t offer to help apart from documenting my hack as an interim solution.
In terms of the multiple CSS suggested by @bowromir, I’ve spent the last year working with Zend Scaffold as used within Webligo’s SocialEngine 4 and it was a PITA. Scaffold caches an aggregated version of all stylesheets used in the theme into a single CSS, which sounds logical but makes it very time consuming to debug or alter the base stylesheets since tools such as Firebug cannot tell where styles originate from.
The only reason to split up CSS is to separate layout from design and since BP only has one design I don’t see the purpose and it adds requests. The single most thing that bp.org needs is to drop the activity stream. Push everything into forums and hopefully get some of JJJ’s bbpress into it with more forum features.
This site does need a better look to entice users. Needs a showcase section and How-to’s. I have no problem with bp-default other than the fact that it should not be required to get features into a WordPress theme. This should be the goal, creating a new design does not accomplish that. Focus on the problems not cover it up with fancy design. Base theme should be clean and simple not overly designed. You could even have a few child themes to show what’s capable with simple CSS/ javascript tweaks.
That’s a few things off the top of my head.
@bowromir
CSS
Decoupling the CSS into smaller pieces seems like it would go against the cardinal rule of minimizing HTTP requests to speed up page load times. Having everything turned on would load up 10 separate CSS files, just for the theme itself. They’d naturally be enqueued hierarchically so they cascade correct, so if one of them hangs for some reason, you end up with theme spaghetti.
I’d suggest giving this a shot and comparing the speed differences with BP trunk on your average web host account to see what the real-world impact would be. If it’s negligible or we can minimize the impact, I’m for it. Would be nice to separate it into structure, colors, etc… too.
Shortcodes
check out how the bbPress plugin is incorporating shortcodes, and how it’s theme compatibility works to get a head start on what will get ported into BuddyPress core in the near future (after 1.3) – I’m filtering the_content() and loading template parts in an output buffer, to inject bbPress forums into *any* existing WordPress theme with a page.php template file (with appropriate measures taken to minimize conflicts, etc…)
Supporter
The Supporter idea is neat, but doesn’t sound so much directly related to BuddyPress core. In the past, these kinds of donation based tasks don’t usually raise enough money for the hours of development that are involved in making something happen. Plus, who holds the money in escrow, who handles taxes and payouts, etc… It all gets really complicated, so you have your work cut out for you there.
Without template files to display content, there is no BuddyPress. Having just gone through this with the bbPress plugin, it’s impossible to create custom WordPress components without theme files to back them up.
Are you saying you want to make a non-ajax default theme that is easier to extend?
I just think its wrong that a plugin takes over the entire WordPress theme. When you do that its not WordPress anymore its BuddyPress. It adds an additional layer of complexity that is not necessary. Additionally, keeping the theme inside of BuddyPress makes it too easy to couple the functionality of BP to its theme. This cohesion is what makes it so infuriating that your theme has to be “perfect” or it breaks all of the advanced BP functionality achieved with javascript. Separating the two would force BuddyPress to play nicer with WP.
Hi, I am currently designing a website and would like help with two things relating to buddypress…
The site is http://www.thecubebirmingham.net
1. Once a member enters their info through the sign up page, the submit button is clicked and the page simply refreshes and there is no evidence of the member actually signing up.
2. Is there a way to create your own log in page rather than it taking you to the wordpress login page?
Help would be greatly appreciated.
Thanks!
