BuddyPress.org

This is how it’s supposed to work. Blogs are just normal WordPress blogs where users can select any WordPress theme you provide.

This is an old thread, it’s waaaaay out of date now, please start a new one. You can use the group extension API to do this. Or you can try this: https://wordpress.org/extend/plugins/bp-member-map/

OK ~ i was able to get the bp 1.2 default running perfectly using a subdirectory install with the current wp trunk I am using multi-site ~ with only one modification –

Make sure your rewrite base for .htaccess is correct in your root and these are also correct.

..and then add this to you wp-config pointing to your subdirectory wp-content

define( 'WP_CONTENT_URL', 'http://127.0.0.1/~david/test/whatever_your_subdirectory_is/wp-content');

@Andy: In previous trunk versions I was able to use both a home.php template (/) and an index.php template (/blog/) but now I get a 404 when I go to /blog/.

Explanation: My theme is set up so home.php uses a custom query to show all posts tagged with the most recently added tag in a custom taxonomy (i.e. taxonomy “issues”, tag “Winter 2010 Issue”) while index.php is a normal WordPress homepage loop returning a paginated result set of all posts by date. This doesn’t work anymore since /blog/ (index.php) returns a 404.

@Everyone: Thank you so much for the replies but I’m not sure the issue is being understood. The issue is the template hierarchy not working as it should. Without changing anything in your reading settings home.php should be used for the homepage and index.php should be used for the /blog/ slug. That no longer works.

@Mike: I was trying to change the slug since /blog/ no longer works. It worked before. / used home.php and /blog/ used index.php and both had functioning loops that returned posts.

@MrMaz: That works to change the homepage but the template hierarchy seems broken (see above). I can set up the homepage to manually use a page with home.php assigned as it’s template and then I can actually link to /blog/ and it WILL use index.php (yay)… but the only posts the loop returns i.e… if ( have_posts() ) : while ( have_posts() ) : the_post(); is the page you’re on since (I’m guessing) /blog/ is not longer considered a home page.

Perhaps I need to have TWO custom queries? That may be the solution. Use my custom query for the homepage (however that is set and using either home.php or index.php… all irrelevant)… and then a custom template assigned to whatever page I want (maybe a page called Archives) that uses a custom query to return all posts from the database (i.e. so the loop results won’t be based on the slug… but on your custom query). Seems like a few hoops to go though. Worked fine before simply by using the WordPress template heirarchy and / and /blog/. As long as I can get it working though… it’s all good.

@foralien: It’s a root install.

PS: Your classifieds-plugin breaks on my install the ajaxed-navigation in BP… hmmm.

Some other strange stuff: The title in the wordpress-repository is wrong “real names”…

I think I wait, until xou think it is more or less stable…

Hope it will work…

Ya that doesn’t work. I get a “bloggyblog” page of course… but it’s just a page using single.php. And if I assign index.php to it as a custom template the loop doesn’t work. Which I don’t quite understand. It’s the standard WordPress loop.

Yah… SSH command line stuff is a dream. LOL. Especially for someone who is a designer first and a coder second :o)

So you mean create a WordPress “Page” called blog (and make sure it’s slug is ‘blog’)? I had tried using my index.php file as a template that I assigned to a page… but the loop didn’t work.

It is weird tho’. In pervious versions of BuddyPress… you could go to /blog/

I think the bP Geo plugin is a farce. I have tried multiple times to contact the dev team there to no avail. They even go so far as to claim to be sponsored by Automattic. Seems doubtful. They are nowhere on this forum and no one has been able to get their plugin to work.Call me suspicious. You are better off trying @jjj’s plugin https://wordpress.org/extend/plugins/bp-member-map/ He is a living, breathing person as opposed to the aforementioned dev team

I’d go with windhamdavid’s method, since I did use the guide that Symm2112 posted before.

On that post’s comments, I list a potential problem with categories and custom taxonomies that you might encounter.

I found that there were a few spots that I needed to change mem limit to import but ok. I used this tutorial to import my install. you have to remember that you’re not importing into Buddypress, you’re importing into wordpress or wordpress MU. Buddypress is just a plugin, not a platform. It ADDS the social features to your wordpress installation.

http://welcome.totheinter.net/2008/10/04/how-to-migrate-from-wordpress-to-wordpress-mu/

an alternative method if you can’t increase your php memory limit is to grab this plugin and then import/export in chunks by date range.

Sorry. I’m frustrated beyond belief at the moment. Deadline tomorrow. Broken site.

Question

Does the change mentioned in this thread remove support from the WordPress template hierarchy for using BOTH a home.php (standard template that’s part of the WordPress hierarchy) and an index.php file? Because I require both.

I need to reopen this thread to ask the group what I need to do when the Buddypress Import feature experiences a php memory failure halfway through the import.

I was just importing the xml file and got to around 90 posts (I have over 500), then it crapped out.

I updated the php.ini file in wp-admin for 128M, but I don’t think changing it to that high a setting on 1and1 helps at all. They state they have a max of 40, but I think they just put that out there and you can actually go over the limit, but I’m not sure.

I know how to dump my mysql file from my WordPress database on my host. I’m just not sure what would happen if I imported the database from a general WordPress install to the database for a BuddyPress install.

Here’s what I’m seeing after trying it twice. I see that it see the posts I’ve already added.

88 Importing attachment http://netmix.com/wordpress/wp-content/uploads/2006/01/jam_markspoon1.jpg... (30 kB)

89 Post Jam & Spoon's Mark Spoon Passes On already exists.

90 Post Larry Heard's "Can You Feel It" vs. Martin Luther King's "I Have A Dream" Speech already exists.



Fatal error: Out of memory (allocated 33554432) (tried to allocate 524297 bytes) in /homepages/7/d106361195/htdocs/netmix_home/wpmu/wp-admin/import/wordpress.php on line 143

Anyone suggest and links that can help?

You installed bbPress in your WordPress plugins directory which shouldn’t be done.

Either let BuddyPress install bbPress for you or install bbPress in it’s own directory.

Ok, this is a serious problem. I’m experiencing essentially the same thing. We’re running BP 1.1.3 and just upgraded form WPMU 2.8.6 to 2.9.1 . But as soon as I finished upgrading the entire site (including all the blogs), I went to the front page and everything is shown exactly 6 hours older than it really is.

See here: http://jibenow.com/

I’ve done some digging around and this is what I’ve found so far: https://mu.wordpress.org/forums/topic/16374

I’ll be giving it a shot and see if I can make a simple hack like they mentioned.

These aren’t BuddyPress questions. Look on the WordPress and WordPress MU websites and forums.

1) BuddyPress 1.2 will be compatible with WordPress and WordPress MU. It will be out soon.

2) Don’t resurrect 9 month old threads

@diesellaws: Are you running WordPress 2.9? The bp-default theme will only be picked up in 2.9+, I’ve just tested and it worked fine for me.

Mostly what I mean by not copying over the stylesheet is that you should just override the bits you need to change (colors in your case)…

So in bp-default’s css you might have:

body {

background: #fff;

color: #000;

padding: 25px;

margin: 0;

}

Instead of copying that entire declaration, all you need to do in your child theme is:

body {

background: #000;

color: #fff;

}

That way you are not duplicating anything, and only overriding and changing what you need.