BuddyPress.org

WordPress has always allowed for multiple ways to access a specific post, even if your permalink structure is setup in a specific way.

Categories

http://www.thelifeofjohn.com/rants/

http://www.thelifeofjohn.com/category/rants/

Posts

http://www.thelifeofjohn.com/2009/03/the-web-world-has-gone-unordered-list-crazy/

http://www.thelifeofjohn.com/rants/the-web-world-has-gone-unordered-list-crazy/

More than one way to get to the same link, and both are valid, and both could lead Google down different paths to the same destination. Granted, this is on a non-MU install, but MU suffers the same fate, only with multiple blogs.

Without having /blog or /news or /something there, now you’re opening up the risk of having overlapping post/page slugs. If you write a blog entry named “members” what would you want to happen? Goto the blog post, or BuddyPress’s members page? Multiple that times 100 individual minds blogging outside of your control, and you see how that can be dangerous.

Trust me when I say that I understand what you’re saying, I do, and I can see how this could be something to consider when making the move to use MU and/or BuddyPress, but Google can recover quickly and so can your 5000 posts if they’re important and relevant.

Also, just for fun, lets goto…

http://delsolownersclub.com/blog/2009/02/09/del-sol-mugen-side-steps/

and then…

http://delsolownersclub.com/2009/02/09/del-sol-mugen-side-steps/

Looks like both take you where you need to be?

Not quite ready to mark this one green, but it looks like a correctly installed BuddyPress/MU won’t give you this problem…

Your posts should still be at http://mydomain.com/whatever/post. The url http://mydomain.com uses the home.php template in bp. That overrides index.php that is used if home.php doesn’t exist. If home.php exists in the theme directory the only way to run index.php is to trap something like ‘blog’ and then load that index.php template.

This is normal behavior for any wp theme that uses home.php. bp doesn’t change the permalink structure of your blog.

You can not use home.php if you like by deleting it from the theme directory or renaming it to something like home.php.off

That will get you index.php being used.

I don’t think there is a way around this.

Are you sure? try to remove blog to the url and refresh the page

Never had this problem.. I’ve bp in bp-dev.org and i don’t user /blog

Update us

are you sure you’ve uploaded fine buddypress?

@ sgrunt..good attempt keep up the work.

@nicolagreco, Regarding cbook theme,any update on mine or email reply ?

http://vgfan.net

The only thing that’s finished now is some of the blogs. Would like to customize the theme a little and I still need to figure out how to get the forums working

Why have you written to replace the member-themes directory??

You can change the name of facebuddy theme directory

is that under gpl? <– if yes i’ll add styles for the bpdev-autosuggest plugin

By far my number one plugin would be extending the multi-db to work with buddypress adding in replication as stated earlier. I believe Nicola may be working on this already though.

I would love a blog theme that integrates with the buddypress them so that way blogs don’t feel like they are separated entities.

Thanks,

Sebastian

Thanks for the advice

I translated 80% done. I uploaded on the web but some lines does not translate at all.

I triple check, make sure I translated that line.

What could be a problem?

Thanks for your help.

Thanks for the advice

I translated 80% done. I uploaded on the web but some lines does not translate at all.

I triple check, make sure I translated that line.

What could be a problem?

Thanks for your help.

Origionally, BuddyPress was designed so the user profiles was one of the blogs…. user.domain.tld.

and so that would go to todays equivalent of domain.tld/members/user. since that was the case, the theme for those blogs would be the member theme, and to access that users blog the url would be: user.domain.tld/blog. because of this, the users blog would be incorporated into their profile.

Now, buddypress users profiles are completly unrelated to blogs and reside at a different URL. Therefore, for a user to create a blog, they would make one just like they would on a normal wpmu installation and choose from any installed (and enabled) theme.

if you want the blogs to be incorperated into the theme, maybe you could modify the member theme into a standard blog theme, name the folder default and don’t enable any other blog templates for the site.

this way, when a user creates a new blog, your theme (default) will be set for it. and it will load more seamlessly.

BTW: i don’t think there is a way for u to get the exact theme from the picture and have it work but maybe you can ask someone about that.

Does anyone know what would be the best way to get this level of integration of blogs and buddy press?

https://apeatling.files.wordpress.com/2008/06/blog.jpg

I found that screenshot here: http://apeatling.wordpress.com/2008/06/12/new-buddypress-theme/

Thanks,

Sebastian

I would do this by going into /member-themes/buddypress-member/blogs/create.php and doing…

<?php if ( bp_blog_signup_enabled() ) : ?>

<?php

global $bp;

$blogs = bp_blogs_get_blogs_for_user($bp->loggedin_user->id);

if ($blogs['count'] != 9)

{

bp_show_blog_signup_form();

}

else

{

?>

<div id="message" class="info">

<?php _e( 'Limit nine blogs per member. If you would like another, please contact an Admin for assistance.', 'buddypress' ); ?>



</div>

<?php

}

?>



<?php else: ?>



<div id="message" class="info">

<?php _e( 'Blog registration is currently disabled', 'buddypress' ); ?>



</div>



<?php endif; ?>

Just remember not to overwrite the member theme if you do a BuddyPress update.

Hahah! If by sexy sexy you mean dedicated BuddyPress supporter, then I’m forced to agree.

Thanks for greening this.

Whooops! (Edited original post to avoid confusion also.)

<li><a href="<?php echo $bp->root_domain; ?>/forums/" title="<?php _e( 'Forums', 'buddypress' );?>"><?php _e( 'Forums', 'buddypress' );?></a></li>

Phil,

you’re going to want to do something a little more codey…

<li><a href="<?php echo $bp->root_domain; ?>/forums/" title="<?php _e( 'Forums', 'buddypress' );?>"><?php _e( 'Forums', 'buddypress' );?></a></li>

I haven’t tested it, but I’m pretty confident.

You could go a step further and put this into a hook function, but lets try this for now and see if does what you want.

Sounds like you have tried to edit the POT file in a text editor by doing something like a find and replace.

Or – you haven’t filled in all the headers correctly

Download the latest POT here : https://svn.buddypress.org/trunk/bp-languages/buddypress.pot

Before opening in POEDIT, open it in your fav text editor, lines 8 to 16 (assuming word wrap isn’t on) need to be filled in with your own values. Save and close

Open with POEDIT and make your changes in there and save.

Sounds like there is a lot yet to come from BP

I do think that the BP core should be as solid as possible and then increase features by the use of plugins.

It is sometimes a bit annoying to find really great software thats full of bloat and things that aren’t needed. So provided the core is solid features can be extended with plugins.

That imo creates great software.

Hi all,

I am using Poedit to translate the BuddyPress file. When I save the file, I always get this error message

11:23:10: wampwww8phetwp-contentmu-pluginsbp-languagesbuddypress-vi.po:844: a format specification for argument 1 doesn’t exist in ‘msgstr’

11:23:10: wampwww8phetwp-contentmu-pluginsbp-languagesbuddypress-vi.po:2566: a format specification for argument 1 doesn’t exist in ‘msgstr’

11:23:10: msgfmt: found 2 fatal errors

Some lines work, and some don’t. Can someone help to correct this error?

Thanks