BuddyPress.org

I am running WP3 B1 with Buddypress 1.2.3, no 1.3 that I’ve seen yet. Works well besides Avatar issues.

I think I am having the EXACT same issue as ajohnson.

I upload the avatars just fine. I am not using the network enabled code in WP3 and my avatars are not showing to crop. they begin at the custom directory files/avatars/1 … etc.

It was a fresh WP3-b1 install

Fresh Buddypress 1.2.3 install on top of it.

Try putting the code in wp-content/plugins/bp-custom.php.

I should add that this code is kind of a hack until BP adds some functionality to detect WP setups in subdirectories.

Also just wanted to add that this issue could already be fixed in BP 1.3 trunk due to the way BP now uses actual wordpress pages instead of a catch URI check.

If you’re using Thesis as the parent theme, you’ll have to enable BP support for your theme.

Two options:

1) Use the BP Template Pack plugin:

https://wordpress.org/extend/plugins/bp-template-pack/

2) Manually add BP support to your theme.

thekmen has added BP support to a child theme of the Hybrid framework:

https://buddypress.org/forums/topic/testing-new-theme-hybrid-as-a-parent#post-40217

You can check out what he did as a guide.

captcha and math tools do not really help fighting spam.

spammer register manually and then feed your blog automatically remote via xmlrpc.

i am running a wordpress mu + buddypress site and had about 40 spammer-registrations a day with lots of spam. then i deactivated xmlrpc via renaming xmlrpc.php in wp-root, result was only user registrations (without content spam). about four days later spammer registrations were reduced from 40 to about three a day (easy to delete), seems that the spam-apps noticed that the rpc doesn´t work and deleted my site from their targetlists, entering their messages manually is to complicated for them….

Looks like you’re attempting to use a BP 1.1 theme with BP 1.2.

You might have some luck with using the BP Backwards Compatibility plugin:

https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/

But I’m not sure.

If that doesn’t work, you might want to develop a new child theme off the new BP default theme.

FYI – Buddypress Template Pack plugin:

https://wordpress.org/extend/plugins/bp-template-pack/

techguy’s got the right idea.

I havent had a spammer registration since i used the “WMPU block spam by math” plug-in. i was getting 20 a day, and now absolutely zero.

https://wordpress.org/extend/plugins/wpmu-block-spam-by-math/

We’ve just finished converting the WooThemes “Headlines” template, and it is well suited for Buddypress. You can see it at http://LabSecrets.com

We found that this template required us to modify the structure and add some new css. Once we did this, it was easy-enough (though just required the time to copy/paste) to replicate across the rest of the theme.

Probably going to try this next on the “Canvas” theme. This time might try to see if there is a way to do it without changing the id labels or adding extra div-tags (but not likely given the fact that the “container” and “content” div’s are used 2x, thereby necessitating the name changes for the inner (they’re used once by woo and then once again in the bp default template….which makes the css problematic….sigh…)

Here are the structures we modified (using group folder as the example):

TOP OF THE PAGE:

<?php get_header() ?>

<div id=”container2″ class=”col-full”>

<div id=”content2″ class=”col-left”>

BODY OF PAGE….CONTENT HERE… OMITTED….

BOTTOM OF THE PAGE:

</div><!– #content2 –>

<?php do_action( ‘bp_after_directory_groups_content’ ) ?>

<div id=”sidebar” class=”col-right”>

<?php locate_template( array( ‘sidebar.php’ ), true ) ?>

</div><!– #sidebar –>

</div><!– #container2 –>

<?php get_footer() ?>

As r-a-y just pointed out, it is called an external install of bbPress because it is external to BuddyPress. So, there is no secret BP code to make it work. You need to integrate bbPress into WordPress.

Once that is successfully accomplished, you then place a link to your separate, external forums within your BuddyPress site. Now, if you want to make your bbPress site look as if it is part of BP, then you have to theme your bbPress to look like the BuddyPress theme you are using.

That is all that was done on the BP.org site–an external install of bbPress with a theme that matches that of the current site theme so that the two appear integrated. In reality, bbPress is not integrated with BuddyPress at all. The bbPress theme does need a function call or two to make the BP menus work within bbPress, but that is covered in a number of other threads.

Have you seen this thread? Perhaps this will provide more insight on how to integrate bbPress into WordPress: http://www.wpmods.com/integrate-wordpress-bbpress

It’s not a code thing, Dainismichel.

If it was a code thing I would have posted it.

I’ve said this before and I’ll say it again… an external install of bbPress (which is what you want) has absolutely nothing to do with the BuddyPress admin area. It’s between WordPress and bbPress.

Numerous others (me included) have given you the correct procedural steps to integrate an external install of bbPress. Furthermore, lots of people have come into these forums and have successfully integrated an external bbPress install properly. You’re basically looking at the instructions and interpreting them differently.

Granted, as we’re not all technical writers like you are, our instructions might not be as clear as you want them to be, however we are trying our best!

Without hand-holding, we can’t physically do this for you.

I have the same problem but a different setup. The site is hosted by hostmonster.com, so I can edit the .htaccess file (or create one if necessary)–if I could learn what the .htaccess file should say. In my root directory is an installation of WordPress MU. The domain does not yet point to hostmonster.com’s name servers so I must access the WP installation and the wp-admin files via the IP address. This works fine and I don’t want to mess what I have there. In a subdirectory off the root, I did an installation of BuddyPress. http://[ipaddress]/~username/subdir shows me the front page of Buddypress the default theme. But all of the links result in 404 errors. They are looking for http://[ipaddress]/~username/subdir/activity or http://[ipaddress]/~username/subdir/members, etc. and those directories don’t exist. What am I doing wrong? TIA!

Wow, cool. I didn’t know this API existed. https://wordpress.org/extend/plugins/bp-breadcrumbs/

I’m trying to figure it out now, but JJJ provided no documentation so far, unless it’s in the plugin file itself.

I tried this but it didn’t do anything:

bp_breadcrumbs_add('testcrumb', 'google.com');

and

echo bp_breadcrumbs_add('mycrumb', 'yahoo.com');

maybe it has to be an internal url, like /activity.

I’ll open the plugin file now.

Download this plugin and check out the code: https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/ It will show you the basic method I used to modify specific xprofile fields. Short version: you can filter the output of xprofile fields in general, and then you use a conditional to detect the name of the profile field that you want. Not enormously elegant, but hopefully that code will get you part of the way there.

the api eh? (a large percentage of shared hosts are poor quality, we’ll never be able to fix that) my take is that at it’s core, it’s “the missing extended user profile framework for WordPress”. It would, in my feeble opinion act primarily as a framework api for extending those profiles. Some of the issues and limitations are really presented by wordpress and mu.. not Buddypress and in much the same way that bp extended the wordpress user profiles/functions we should tackle those head on as had been done with the improvements in the BP1.2 registration. There are infinite ways to build on those relational database fields. Focus exclusively on bp_xprofile _fields, and _data. It’s not that I’m anti-activity stream and the terms social network, life stream or whatever just seem to incorporate user profiles into some sort of relational scheme, be it friends, followers, ‘like’-ing, sharing or chronological micro blogging. Extending the stability, functionality, and interactivity of each component is the goal, but I’d prefer to see no dependency among core elements with one another. It’s fairly simple to build out a “social network” in other popular content management systems by extending the user database fields and in my day to day practice, I typically use only about 20% of the Buddypress core components for a WordPress project. Even though the hype is in the activity stream and the extensions for it (more facebook or twitter like), I side with @stwc in that “It also means that the platform has to have a robust set of tools for the administrator and moderators of the community “. A community (or ‘social network’) is just a set of users and to me, key items are a small footprint on the database and tight the integration with the existing wordpress user roles, permissions, registration and management. The api should ideally be flexible enough to accommodate any possible relational data between user profiles that a plugin author may dream of. I think the core integration between user profiles and the activity/blogs/groups/forums/friends illustrate the foundation of the api and should be as unified, consistent, and simple as possible with very little dependency or overlap in functionality. This would be impetus for creating a more standardized way to interact with the xprofile and be a good foundation for a solid api. lastly, thanks @mrmaz for starting the thread, being pro-active, getting the trac and api.buddypress and generally illustrating the potential of a solid api in regards to how well your links plugin and others can interact with the core.

ps.. death to PHP4 and fsck backwards compat

@cocomozlo – If you just want static content in the footer – site information, credits, privacy notice, etc – your best bet is to copy the HTML produced by BuddyPress, put it into its own file, and then require it in your subdomains with a normal PHP require statement.

If you want dynamic information (latest posts, activity, etc) it’s going to be trickier. Those widgets are populated dynamically by WordPress, and so require WordPress to be loaded. The easiest way to make it work would be to load WP/BP in the background of your subdomains and then use the footer PHP provided by BP. You can start WP by requiring wp-load.php in the root of your WP directory.

Requiring WP on every page load is pretty intensive, though, especially if you’re running another CMS altogether on other subdomains. It’d be good to avoid it. A possible method: Write a BP function that writes the footer to a static file and refreshes it periodically, then include that html page in your subdomains. See http://blog.slaven.net.au/archives/2007/02/01/timing-is-everything-scheduling-in-wordpress/ for more on scheduling events (like a cache) in WP; check out a plugin like https://wordpress.org/extend/plugins/wp-cache/ for an example of WP caching in action.