BuddyPress.org

Home theme, where the root of my blog is located, in fact the admin bar(drop down list [log out]) is also affected.

I got this result for both the log out links for the home theme and the admin bar:

You don’t have permission to access /blog/wp-login.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

I attempted to replace the code for the admin bar and got the same result as how mdsports had. It didn’t redirect to my home blog page.

I downloaded the latest WordPressMU and BuddyPress(I used the beta link that was given)

Here’s the admin bar code which I identified:

// **** “Log In” and “Sign Up” links (Visible when not logged in) ********

function bp_adminbar_login_menu() {

if ( !is_user_logged_in() ) {

echo ‘<li class=”bp-login no-arrow”>‘ . __( ‘Log In’, ‘buddypress’ ) . ‘‘;

// Show “Sign Up” link if registrations are allowed

if ( get_site_option( ‘registration’ ) != ‘none’ ) {

echo ‘<li class=”bp-signup no-arrow”>‘ . __( ‘Sign Up’, ‘buddypress’ ) . ‘‘;

The Home theme header logout link(the one to the right) is also similar but I have no idea how PHP really works and I spent a few hours figuring out what the problem was but I’m interested to learn how these stuff works and I hope you guys can enlighten me.

Here is the problem, when I look a the HTMl source rendered to the browser I see the path

<link rel=”stylesheet” href=”/wp-content/mu-plugins/bpdev-flickr/css/style.css” type=”text/css” media=”screen” />

<link rel=”stylesheet” href=”/wp-content/mu-plugins/bpdev-youtube/css/style.css” type=”text/css” media=”screen” />

whereas the rest of the buddypress and wordpress links have the whole domain associated with them not just the /wp-content… they have http://domain.com/wp-content

So, the function <script type=”text/javascript” src=”<?php echo $bp; ?>js/lightbox.js”></script>

needs to really get the WP domain prepended?

Best bet is create a ticket for this in https://trac.buddypress.org/ with the login credentials from this forum so that Andy knows he is breaking something again

There must be someone who is running subfolders on their buddypress that should be able to answer this one! Hopefully someone will chime in for you.

I believe someone is working on this over at http://buddypressdev.org right now

These are great issues to bring up on the buddypress mailing list and I encourage you to do it. I do not develop WPMU or Buddypress and these are just my opinions. This is just background information as well. WPMU is known to be extremely server intensive as is.

Right now, most scaling solutions have been implemented for WPMU and the database structure that is already developed and in place. Mainly, blog sites like wordpress.com and edublogs.org. They have implemented multi-database solutions where the request gets analyzed for the blog hash and directed to the proper database and the connection only occurs to the database that houses that data. Databases can reside on any server in any location.

Images are also housed in directories created through the blog hash as well. This also allows you to have multiple image directories in multiple locations if you wanted. Some even offload some of their images to 3rd party services like S3.

At present time, AFAIK, there is no solution for spreading around the buddypress data. It hasn’t been addressed yet.

I am not going to argue and say this is the most ideal circumstance or setup. There are plenty of discussions on scaling both in the WPMU forums as well as in the WPMU Advanced Forums as well as on the WPMUDEV Premium Forums. Not to mention the WP Hackers list is also a great resource from the real developers and hackers of WP in general.

Buddypress, like WPMU, are open-source communities and all input is not only welcomed, it is encouraged! Feel free to add anything that you feel would be better. I am sure Andy is welcome to hearing all feedback if you know a better way to do something.

My previous comment on this topic was purely my opinion on how the current setup could be scaled based on my experience with already ongoing projects. Right or wrong, it is just my opinion.

Sidebar widgets: Design -> Widgets -> Blog-sidebar

Left side and all other content: wp-content/themes/buddypress-home/single.php

might as well.

my site is http://upd8t.com

it currently has no real definition on the targeted audience. all the same, i’m pretty happy with it and enjoying the site. i’m using the default buddypress theme. the buddypress concept is awesome!

Hi! I’m running buddypress as of yesterday on canhasjournal.com. I started the MU site many months ago and it’s not very active, but adding Buddypress may change this! I’d been watching the BP list and see most activity seems to have moved over here now. We’re having some minor oddness, but mostly things seem to be working pretty well and I commend everyone working on the project!

This is random, but if I were to give an educated guess–it seems like the toughest part to comprehend initially might be that you don’t put the member themes under the themes file (directory) you put them in wp-contents. Just a guess, hope you figure it out and have fun…

And also, is it possible that you were using the kubrick theme as your home theme instead of the BuddyPress Home Theme? That would give the plugin error.

Also to remove buddypress just remove all contents from mu-plugins and restore your theme to Kubrick.

It’s difficult to really determine this but from what I can gather about what you are trying to do

You are trying to get mu installed in a subdirectory called /blog/blogs under the document root of a live, existing wp 2.6.5 install.

The existing live install has the it’s domain mapped to /blog (not /blogs) where the wp 2.6.5 actually resides.

I didn’t see any evidence of buddypress so you must have been successful in uninstalling it while you get mu up and running.

It looks like you have chosen the subdirectory install option for mu.

Is all this guessing right? I don’t know. I hope your live site stays up and running throughout this and I look forward to you reporting back with success.

There’s no admin bar in the login form no.

I’m not sure what email link you are referring to. After signing up a user gets an email with an activation link and then a password and then logs in with a temp password to their blog.

To get to the admin backend (dashboard) of any blog you use: myblog.mysite.com/wp-admin/ or after logging in, the user has the option of using the menu bar’s ‘my blogs’ > ‘my new blog’ ><flyout menu> ‘dashboard’

That’s also the admin area of the blog.

There isn’t a ‘bbpress bar’ that I’m aware of. There’s a buddypress bar that has a ‘my account’ menu where you can visit your profile and other options.

Nice job – good luck with that!

Hey, I’m running http://www.pozlife.com. It’s a community for people affected but HIV and AIDS. I’m an activist

I just finished ironing out the basics, and its a very limited BP install – no groups, no blogs, no access to the dashboard for non admins. They do have member profiles, and flickr for more photos. I’ve also integrated my wpmu DB with BB press for seamless logins.

I’m going to add more stuff when people request it, but for now I think I can start to invite people to use it!

I’m really thankful for all the help I’m receiving via the forums! Keep up the good work.

The only blog that should be using the buddypress-home theme is the main blog. All other blogs can use whatever theme the users usually want if they are installed. I am getting the impression that you deleted the “default” folder out of /wp-content/themes/ and that is what is causing you issues.

Trent

you should fill out this form http://buddypressdev.org/add-plugin

That is a very good question! Never run across anyone that tried it, but I can’t see why it wouldn’t work since the hardcoding for site “1” is all gone now. Short of testing it out, I am not sure if anyone has an answer. I might get a chance to test this out later today though. If you test it out, let us know.

cdaniel09 – you need to move up to wpmu 2.7

awesome plugin!