BuddyPress.org

@ M:

when will the plugin become available to download ?

Mcmc-

installed via simplescript at bluehost

This may be your issue. You really should not be installing complex software platforms like WPMU by using third-party installers. You should manually install WPMU paying careful, close attention to the readme.txt file that comes with it.

Also, search the forums for “BlueHost” to see the issue other users have when using simplescripts. Here’s one to get you started.

the redirection plugin (checked that already), avatar plugin, wordpress.com stats, akismet, statpressCN, Sociable, Author Avatars List, google analytics

To isolate WPMU and BuddyPress issues, you need to deactivate all plugins. This means that BuddyPress should be the only plugin running period. If your site issues go away, then you activate one plugin at a time, testing with each reactivation, until you get the problem again.

not aware of any relevant errors

The question asks for a listing of any errors in your server’s log files, it does not ask for you to decide whether or not they are relevant.

When providing a listing of errors, you do not need to copy into the thread the entire contents of each error file. A single error can be repeated many times. We just need a single instance of each, unique error. More times than not that is sufficient. If we need more info, we may ask to see the entire contents.

Yah… whichever file has your Home, Blog, Groups, Members etc. navigation. You could maybe just hardcode those links instead of using a buddypress function and then wrap the ones your want hidden with that if statement. Again… I’m just talking off the top of my head. I haven’t actually tried this. I think you might have to do it in a few places though since home uses it’s own theme right? Let us know if you get it working. I’m going to want to do a similar trick (for the time being… until the permissions access component is released).

For those that want to use this solution with a theme like ‘default’ or ‘classic’, I think this is enough to get you going. For me, I find it a bit discontinuous to start from the buddypress theme home page and then bounce into the ‘classic’ theme of some individual user, and still think about it all as being the same site. I completely respect that that is a legitimate model & approach. It’s just not what I have in mind for my particular implementation.

Unfortunately, it’s not quite enough to just make the facebuddy theme default for all users. The ‘thing’ I want to ‘resolve’ is that for any user’s new blog, wordpress basically gives that user their own buddypress front page, that the user then needs to configure with their own widgets and stuff through the wordpress admin.

For my needs, I would like to make something that is more turnkey for new users, such that they only have to register & create the blog & start posting. I don’t want them to have to think about layout. I may offer them the option, but I want their blog home page to look polished off the bat. Furthermore, this ideal default setup would have a unified feel with the entire site so that as you went from user blog to user blog, a visitor feels like all the content look & feel is homogenous across all blogs in the wpressMU install.

Another way to put this idea is … when you go to the user’s specific blog page, there should more emphasis on the fact that it is a user of the main site discussing on some specific site topic, within the context of the site branding, etc …. rather than making the distinction that you are visiting someone else’s blog. Like a newspaper … only the by-line and the article content vary.

I have some ideas on ways I can approach this. If anyone else is interested in this, I’d be happy to share ideas and collaborate on knocking out a solution. Maybe someone has already solved this problem, but if they haven’t, I imagine it could be useful to a few other folks as well.

BuddyPress is just Awesome!

http://kodingen.com

Online Code Editor – powered by Buddypress.

for a screencast of what we’ve done:

http://vimeo.com/4924519

For example: ‘team’ instead of ‘group’

It sounds like you are specifically talking about changing slugs. If that is the case, read this article that Andy wrote.

Trying to accomplish the same objective, I found this article: https://mu.wordpress.org/forums/topic/1463

After following the setup directions, when I created a new user, created a blog, created a post, and then went to view the post, it appeared in the expected theme. As the user, I *did not* need to go to set the theme myself.

Towards the end of the thread, there is the following

~~~~~~~~~~~~~~~~~

As of 2.7 this information:

….

===========================================

Lines 311 and 312 of wp-admin/includes/schema.php in the populate_options function.

add_option(‘template’, ‘yourthemename’);

add_option(‘stylesheet’, ‘yourthemename’);

===========================================

We need more information to provide assistance. Please answer these questions.

please search the forum before posting the same questions posted before. And make sure you read documents.

https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/

You really need to read documents and learn basics of wpmu before using buddypress. Otherwise buddypress forum gets messed up with general wpmu topics, which are not supposed to be posted here.

n/w, Site Admin > Blogs > there you’ll have to set the main blog to access that theme.

This is a basic WordPress question and not a BuddyPress question.

Pages cannot have categories or tags. If you want or need these, then you’ll have to use WP posts instead.

Here’s a link to a WP codex article on pages that will help answer some of your questions.

Now, you could use BuddyPress groups along with Burt Adsit’s BP Content plugin to accomplish your goal.

I have worked with this a bit. Tis true.. when posting using the JSON ajax inline posting.. no activity in sitewide. but comments or posting from the backend is a-ok. sitewide tags picks up the inline posts, but not sitewide activity feed. you can see here – http://cackalaki.com/wp-admin/ user: guest – pass: guest. good luck DJPaul… it might help to know that it does pick up the inline posts from p2 in recent blog post.

We do not have sufficient information to begin helping you. Please answer these questions.

This will be fixed in 1.0.1. There is a patch for this in the trunk.

In the meantime, try adding this to your functions.php file for your theme(s).

// Load the buddypress translation file for current language

function bp_load_buddypress_textdomain() {

$locale = get_locale();

$locale = apply_filters('buddypress_locale', $locale);

$mofile = BP_PLUGIN_DIR . "/bp-languages/buddypress-$locale.mo";

load_textdomain( 'buddypress', $mofile );

}

add_action ( 'plugins_loaded', 'bp_load_buddypress_textdomain', 9);

Would it be possibile for group admins to create own categories for their groups, then add in tags as needed? Or is the site admin gonna have to constantly decide which group fits in where?

I also did all the possible things. But this is not working.

Is there any way to hard code alter certain phrases?

In order to have the buddybar appear, you need to do what is called “deep integration” between the platforms. It means including WordPress and BuddyPress, inside your bbPress process.

See this post.

At that point, the wp_footer() will load the BuddyBar, but you will need to pull off some styling tweaks to make it all play nicely together.

I haven’t looked at this directly, but I suspect this is due to the nature of the AJAX that is making the new post versus it being created in the WordPress admin area. This means that either BuddyPress needs a plugin to hook into whatever P2 is doing, or vice versa.

Has anybody made P2 theme a member theme for BP, that looks like this buddypress site?

I have just run into this (I think) – a post on my blog using P2 doesn’t appear on the main blog in the Sitewide activity; I guess it’s just missing an action call.

This evening when I get in I will fix it and update this thread with the fix.

Great job @Burt!