BuddyPress.org

Erm.

Since you didn’t provide ANY version numbers; I’m guessing you are trying to run BuddyPress 1.1.3 on WordPress?

@Andy. Yup. It makes sense to me now that I’ve figured it out. After your instructions didn’t work as expected, I went back to basics and read the codex page about “Reading Settings” and under the “Front Page” bullet near the bottom of the page it says “If you would like to create a static home page template file, do not name it home.php”. Ding ding ding! Light bulb. So I put two and two together and finally figured it out.

https://codex.wordpress.org/Settings_Reading_SubPanel

Glad I’m not crazy after all. Sorry. I know my additions to this post were very confusing and probably a little frustrating. And thanks again Andy! Although your instructions didn’t work quite as expected because I had that home.php file, at least I knew I was on the right track! You’re a lifesaver.

To be honest the way it is now is the way every WordPress theme designer is used to. It’s the way WordPress does it natively. Using home.php is actually not the best idea since it overrides all settings – as we found out in the end.

Andy’s instructions didn’t work because I still had a template named home.php for my homepage and it was taking over control of my posts page even when I had manually assigned it to my custom “Blog” page and template.

If anyone cares (LOL)… here’s the solution to having a separate front page and posts page that can both use a full paginated result set from the database.

1. Make a template for your homepage with a filename OTHER than “home.php” or “index.php”. I used “homepage.php”.

2. At the top of this file add <?php /* Template Name: Home */ ?>

3. Make a WordPress Page called “Home” and assign it to the template you just made (i.e. “Home”).

4. Make a WordPress Page called “Blog” and leave it assigned to the default template (which will be index.php).

5. In the Reading Settings switch to static mode and set the Front Page to “Home” and the Posts Page to “Blog”.

Thanks for the help guys. That was a mind bender. Just seemed easier (from a development point of view) when home.php and index.php defaulted to “/” and “/blog/”

Now I think I need a drink. LOL :o)

I used this plugin for a one-time, scary users import operation. Not sure if that’s helpful for your issue.

The WP/WPMU/BP members database is a patchwork designed to be as incompatible as possible with whatever else you might dream of using.

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.