BuddyPress.org

In one word: no.

In BP 1.1, themes will work more like regular wordpress themes. I suggest you wait until then or develop your custom theme from a development version.

Closing this thread as gerikg’s taken it off topic.

I miss my nextgen plugin (doesn’t work well with MU)

I think Mark Jaquith recently said that the WP/MU convergence was expected to be completed by 3.0 or 3.1, so, that would be in either 3 or 6 months time.

Not really so very far away, I think.

The situation can be summed up like this:

The BuddyPress 1.0 theme structure made it easy for existing WordPress sites to use BuddyPress out of the box (but only with the default theme which was never ideal). However, it made life very difficult for anyone designing a site from scratch with BuddyPress, and for 3rd party theme designers.

BuddyPress 1.1 makes it harder (but still very possible) for existing WordPress sites and themes to use BuddyPress, but makes it very easy for sites starting fresh and for 3rd party theme designers.

The number of people starting sites fresh using BuddyPress significantly outweighs the number of people trying to use BuddyPress within an existing WordPress setup. It is only logical to make the lives of the majority easier.

There will be more documentation on using BuddyPress with existing WordPress installations and themes once 1.1 is released. Let’s get it out there first.

On a side note – I’d really love to see existing WordPress theme designers coming out with BuddyPress theme extensions for their WordPress themes. This for me is the ideal scenario, let the top theme designers provide support for BuddyPress, rather than the end users trying to force a square peg in a round hole.

I’d like to delve into this more deeply, but for now, even using the child themes there is an additional complication. It’s reasonable to expect someone to be integrating BP with an extant site using an advanced WP theme, and simply setting this theme to be a child of the bp-sn-framework doesn’t suffice. I’m working in one such setup, where a theme uses several include() statements in a functions.php file, and setting this as a child of the BP framework b0rks the whole deal. Now, I know what to do here, at least in the simplest case: just amend the functions.php calls. That won’t necessarily persist as the theme is updated, so maybe, instead, this can be done via a plugin.

The point here is that there are easily found examples where existing WordPress installations aren’t set up to so trivially extend to include BP. This one has a straightforward solution, but some will not. And as WP theme developers continue to do ever-more-amazing things with WordPress, and as you and other developers continue to make WordPress and BuddyPress more powerful, this sort of nonlinear theme infrastructure will likely become the norm. I don’t think these are quite edge cases, either; the theme I’m testing with is a free Woo theme, so not quite off the beaten path.

I don’t want to add to the confusion. Rather, I wonder if I could help flesh out some use cases, which might later get wrapped into the documentation (if it’s helpful). For instance, there is the site that purports only to offer social networking, without long-form blogging intentions. In that case, Using bp-default with customizations is pretty straightforward–well, as straightforward as the styling for the site needs to be.

However, for folks who have an existing WP site to which the BP functionality will be at most equal in priority, their branding and existing structure may be complicated enough that simply setting their existing theme to be a child of the BP framework doesn’t work by itself (styling issues aside–there will always need to be style adjustments; this is about structure and objects). Again, as my example demonstrates, this complexity is closer to the norm than some might expect, especially among the crowd using WPMu and extending it with BP. In this case, there’s more to document.

I don’t intend to suggest, as some have, that BP developers need to rethink or revise BP’s scope and structure. That’ll probably happen anyway, as things start merging more, but it’s not necessary. I only mean that the adaptation of BP to an extant site is a nontrivial use case, and while there is forthcoming documentation as to how best to manage this, maybe the forum users and devs can spec out some general use cases and work on how best to develop their solutions.

catinw12, you shouldn’t need to create any new profiles anywhere. All of the .org sites should provide you a unified login/password combo to use on wordpress.org, bbpress.org, buddypress.org, and all of their respective trac’s.

wordpressfan: That’s nothing directly to do with the subject of this thread, which has been marked completed. Start a new thread.

It sounds like you need to learn a bit about how WordPress child themes are implemented. I had a quick google and found http://op111.net/53.

I’ve also removed the status from this thread as it isn’t a support issue.

Tore, read this and see if that helps.

I would first search the most recent file you modified, making sure that you did not add whitespace before or after the php tags. It appears that that would be new-user.php. If you cannot find the issue in that file, then move on to the the next file you modified, looking for the same issue.

hi dwpers

are you using Limit blogs per user plugin.

This is a known issue with that plugin.let me explain it.

If s user does not selects a blog,he is added as a member of your main site(subscriber or what ever default signup role is,this is a wordpress Mu requirement).So the blog count for user becomes one even if he has not signed up for the blog.

You can manually add the user to new blog.

Please go to wpmu backend->Site Admin->Blogs

In the add blog option,enter the users email address(the email address of existing user and create his blog).he will be automatically assigned the new blog(removed from the main blog) and can do the things as normal.

hope it helps.I am working on the newer version of this plugin which will take into consideration the factor (when user has no self created blog,it should be considered as zero).

Thanks

Brajesh

@wordpressfan

I’m closing this thread as it deals with the exact same issue you posted several hours earlier. You can read my response in that thread.

https://buddypress.org/forums/topic/member-theme-remove-me-and-my-profile-columns

Installed the plug-in, it’s looking good! I’ll post results after I’ve done some testing.

Question: I want to create a widget just like the wordpress calender: http://www.sajidmc.net/wp-content/uploads/2009/04/screenshot-1.png

but than for the events. Any idea’s how I can do this quickly?

I know how to script, but don’t know where to start with this.

You could also try some WP plugins that add additional hidden, input fields to the registration form:

-Invisible Defender – https://wordpress.org/extend/plugins/invisible-defender/

-NoSpamNX – https://wordpress.org/extend/plugins/nospamnx/

Chances are a spam bot will fill these input fields in, and thus these plugins will block these submissions.

—

I’ve been meaning to give this a shot, but I haven’t tried it yet because I don’t need the extra layer of protection (right now anyway)!

Not sure if everyone knew this, but wordpress.org uses BuddyPress now!

Check it out:

https://profiles.wordpress.org/users/

tray this deep integration script instead, this should fix your problem.

if ( !defined( ‘ABSPATH’ ) & !defined( ‘XMLRPC_REQUEST’ )) {

define( ‘WP_USE_THEMES’, false );

include_once( ‘/your/absolute/path/to/wordpress/wp-config.php’ );

$wp->init();

$wp->register_globals();

http://youlookfab.com

WordPress blog since 2006, bbPress forum added in 2008, and now a BuddyPress community. To start with we’re only using extended profiles and private messaging, but will layer in additional features over time.

Very grateful for the powerful platform that Andy and team have created, and for the great support offered by Burt, JJJ, Jeff and all the others on the forum.