BuddyPress.org

@energynet BuddyPress is not activated in your site. Have you tried changing to Twenty Twelve theme and activating BuddyPress?

Moved topic as requested.

To add code in Codex, you can either use

<pre><code>
// code here
</code></pre>

for something like https://codex.buddypress.org/developer/members-navigation-menus/

or use

[sourcecode language=""css""]
//code
[/sourcecode]

for something like https://codex.buddypress.org/legacy/theme-dev-template-pack-walkthrough-twenty-twelve/

@bp-help

You would not be associated with my site in any way by doing this – this is just code that would help a lot of BuddyPress users (judging from the many requests for it). I simply suggested showing you my site to give you a clearer idea of what I’m already doing, and how the code I have so far works. If the site of the female human body offends you, you don’t have to look (that’s entirely your choice), but it shouldn’t have any bearing on whether or not you help to provide a much-requested BuddyPress feature.

@hiboy
Easy fix so don’t panic. Go into your server and rename that plugin. I always append it with 2 capital X’s to the beginning of the plugin name which will deactivate the plugin it can be anything it is just a habit for me.
In your example change the folder containing the plugins name from:
buddypress-xprofile-custom-fields-type
TO:
XXbuddypress-xprofile-custom-fields-type
You can then get back into your site and the plugin will be deactivated and you can delete it via the dashboard if you choose.

@hiboy
Doesn’t your theme contain a footer.php? If it does and it is not widgetized then you will have to manually widgetize it. Do a google search, there is lots of instructional info about widgetizing areas in themes.

@asnakea3 No trolling. If you need help, ask for it and we’ll try to help. As I mentioned in your topic, there are plenty of happy BuddyPress campers. Closing this topic.

@faheem123 https://buddypress.org/support/topic/when-asking-for-support-2/

Closing this topic. As noted above, the issue was with the hosting company. Feel free to start a new topic of your own.

@asnakea3 @bphelp a good example of BuddyPress working with a WordPress theme is http://testbp.org It’s using the upcoming Twenty Thirteen theme (availabe in WP 3.6 beta 3).
Other examples of BP-powered sites:
https://wordpress.org/showcase/?s=buddypress
http://www.bpinspire.com/

I do empathize with your frustration, but this is not the way to go about getting help with your installation issues.

@asnakea3 At this stage, I’d recommend deactivating all plugins except BuddyPress and changing to BP Default theme or the Twenty Twelve theme. Clear cache and check registration.

@hiboy
Hi there, If your using bp-default theme then the footer is widgetized in four areas so you should be able to ad adsense code there. If your using a different theme then you will have to check if the footer area is widgetized. If it is not then it is still possible with some coding.

hay @ubernaut
help me dear

@ubernaut
LOL! GOT TROLL? Sounds like someone has watched one two many Conspiracy Theories featuring Jesse Ventura including the reptilian elite! LOL!

@asnakea3
Furthermore BP is not a “broken or sold script” if you have paid for this software then you have been had by unscrupulous people. BP has bugs as any software including premium software has and the Development team does their best to resolve these bugs. Have you even searched the open trac tickets, or opened a new trac ticket if you have found a new bug? If you haven’t then you have given away your right to complain because your not reporting bugs which is highly encouraged by the community and by the Development team. As far as you writing an article trying to slander BuddyPress and convince people it is not legitimate, then I am afraid It just makes you look incompetent because you failed to follow pretty standard practices. @hnla @mercime I think this thread is not conducive to anything constructive at this point unless you would like to chime in of course, I request this topic be locked.

I went back to the original answer found here
http://buddydev.com/support/forums/topic/wp-search-results-page-kills-bp-member-widgets/

At this time, I do have the code working so that a wordpress search doesn’t wipe out buddypress member widgets and all the other functionality works on the members directory page too.

Here was my solution:
In bp-members-template.php, I remarked out lines 305-311 and replaced them with

if ( !is_search()&&isset( $_REQUEST['s'] ) && !empty( $_REQUEST['s'] ) )
        $search_terms = $_REQUEST['s'];

So I’m back to the question/concern of 4 or so hours ago. I don’t feel that modifying core code is ever a good idea. Has anyone come up with a better way to solve this that makes it more durable when plugin updates are applied?

I don’t have to prove anything to you I am trying to assist you. I am not the one complaining because your not using the advice given. I have had many BuddyPress sites ranging from BP 1.2 through 1.7.2 and it works great. The problem is when you have a fresh install of WP and BP then every time you install and activate a new plugin then test it against your registration. I am sorry if this sounds tedious and insensitive but I do not feel sorry for users who use out of date plugins and install 30 to 40 plugins without testing against registration only to find in the thick of it all one of those plugins conflicted with the registration and then they have to back peddle to find what they would have found if they had tested each plugin as they activated it against the registration. That is not very responsible, so do your part because the Development team can only do but so much.

@bp-help

Here’s BuddyPress Follow: https://wordpress.org/extend/plugins/buddypress-followers/

Here’s my new scope code again: https://buddypress.org/support/topic/ive-figured-out-how-to-create-a-facebook-style-wall-but/

I should point out that I need a way to apply the scope selectively, rather than universally i.e. I want both a normal site wide activity stream and a Facebook-style wall.