[Rich Spott]

http://premium.wpmudev.org/project/ning-to-buddypress-user-importer/

That will help you transfer all of the users over to buddypress, but I don’t have any advice on the content

[Rich Spott]

Same problem here, only gravatars show, not local avatars http://baseballpastandpresent.com after upgrade to bp 1.2.4.1. Local avatars appear on main blog http://sportsblognet.com, but not single blogs

[Rich Spott]

bump

[Rich Spott]

I, also, have this same problem (after upgrade to BP 1.2.4.1) running wpmu 2.9.2

[Rich Spott]

still no help?

[Rich Spott]

Yes, I tried taking out all plugins and mu-plugins except for buddypress obviously), but still the same error when I, or any of my users, try to post a private message.

[Rich Spott]

bump

[Rich Spott]

I just did it manually in phpmyadmin, with:

hide_sitewide tinyint(1) default ‘0’,

those settings. It seemed to work fine, no more errors in my logs regarding that. Thank you.

[Rich Spott]

I deactivated and reactivated BP and I am still getting four of those errors every minute. Can I manually create the column? If so do I name it hide_sitewide?

[Rich Spott]

I just thought, in case anyone was wondering…

I started a server from scratch (Ubuntu Hardy, Apache 2, PHP 5 MySQL 5) and installed a fresh WPMU 2.7.1 with a brand new bare database, only using the default theme w/out any plugins (w/out buddypress too)…and was STILL able to reproduce the internal redirect.

I then thought to see if other MU installs would react the same way…

so I tested these (plus about 30 others, not all Buddypress sites, some just MU installs)

http://bp-dev.org/wp-cotent/plugins/bp-core/images/mystery-man.jpg

and…

http://www.flokka.com/wp-cotent/plugins/bp-core/images/mystery-man.jpg

(I misspelled “wp-cotent” and the error came)

It happened on MOST WPMU installs (buddypress.org and WordPress.com returned 404 errors)

I realize this is a WordPress Mu issue, so I reported on their forums

https://mu.wordpress.org/forums/topic/12676

But if anyone has an idea as to make these errors a 404 like buddypress and wordpress.com do, Please Help.

[Rich Spott]

You’ve just got to tear out *everything*. All this domain mapping and other things. Get down to a bare install of bp 1.0 using the default themes and wpmu 2.7.1.

I did that, took out all plugins except for buddypress 1.0, and changed the themes to the default buddypress theme, and default buddypress member theme, and used a vanilla .htaccess for wpmu 2.7.1.

Still got an internal redirect when Googlebot-Images came through and looks for something that is not there. I even recreated the error and was able to see the 500 error.

Did you remove your previous bp install from /mu-plugins? Why is it trying to get to an avatar image from there? I suspect it’s all your *other* addons in some combination with the upgrade to 2.7.1 from 1.x and the addition of bp into the mix that is causing your problems

Yes, I removed buddypress RC-1 from mu-plugins before proceeding with installing BP 1.0. I dont know why it is grabbing files that dont exist. But that’s not really why i’m worried about it, it’s more that if any sites links to tries to get a file that is not currently on the site, it creates a 500 error.

I didn’t upgrade from WPMU 1.x to 2.7.1, I went from 2.7 to 2.7.1, and 2.6.5 before that and basically following each and every update that there has been since 1.3.3 last april. Maybe it was confusing in the way I wrote it.

Take things back to a known, working state. Start with bare 1.x. Then upgrade to wpmu 2.7.1 incrementally. From everything I hear on the wpmu forums this is the recommended procedure. Jumping from 1.x to the latest version in one step isn’t recommended.

I went from WPMU 2.7 to 2.7.1, and it was working fine in 2.7 with BP RC-1

But I did have everything stripped out for a matter of 10 hours and i still got the same errors. I do know that some plugins leave tables in the database, should i drop those tables associated with a plugin and see if that works? Because even if I have a clean install of WPMU 2.7.1, then BP 1.0, i still have a database with all of the remnants of the old stuff.

[Rich Spott]

The specific error that shows in the error log is

[Fri May 22 15:44:40 2009] [error] [client xx.xxx.xxx.xxx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: https://buddypress.org/forums/topic.php?id=2840

I just clicked the link from an earlier post and the 500 error happened.

xx.xxx.xxx.xxx - - [22/May/2009:15:44:40 -0700] "GET /wp-content/mu-plugins/bp-core/images/mystery-man.jpg HTTP/1.1" 500 612 "https://buddypress.org/forums/topic.php?id=2840" "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) FirePHP/0.3"

the latter is from my access log.

My permissions are set correctly, that’s usually the first thing i check.

now onto a couple more of your questions:

Have you searched the WPMU forums for 500 Internal Server Error thread? I think this may be more related to you WPMu install than BuddyPress?

Yes, I have searched WPMU forums, and even posted on there my problem, but no one reponded. I was pretty sure that it was related more towards WPMU. But these errors only started happening a few weeks ago, after I upgraded to WPMU 2.7.1 and BP 1.0

Are you using some special permalink structure? That should not be causing the lack of 404’s but every bit of info helps.

No, everything I was using was either in the htaccess.dist and the wp-super-cache (which has since been taken out until i find the cause). The permalink structure that I use on http://sportsblognet.com is the “year/month/day/name” option, which is one of the standard ones.

Did you carefully follow the readme.txt file that comes with WPMU?

I just re-read it to be sure, yes, yes I did follow it.

Is this a new WPMU 2.7.1 install, or did you upgrade from an older version?

This is an upgrade from WPMU 2.7, it was first created with WPMU 1.3.3 over a year ago. We’ve been following buddypress since October of 2008 and have been using it since 12/08, when the first beta came out. I’ve upgraded pretty much everytime without problem. And these Internal Redirects only started after the upgrade to WPMU 2.7.1 and BP 1.0 at the beginning of May.

[Rich Spott]

The offending party is usually Googlebot-images (but it has been others in the past).

I did what you said a disallowed googlebot-images with robots.txt, it seems to be working, but googlebot might only come through every 6-12 hours so can’t tell yet.

But even if that does work, I can easily recreate the error myself.

If I type in (which doesn’t exist):

http://sportsblognet.com/wp-content/mu-plugins/bp-core/images/mystery-man.jpg

I get a 500 Internal Server Error

If I type in (which doesn’t exist):

http://rotoassist.com/wp-content/mu-plugins/bp-core/images/mystery-man.jpg

It comes up as the proper 404 error

the rotoassist site is a regular WP 2.7.1 site on Site5 (one-click install type)

On another topic…is it good to create a ginormous robots.txt file? I’m wondering if that slows down your site at all.

And yes I use Firefox and have the Web Developer Add-on. The only info it gives me with the error though, is that it is a 500 internal error.

Another question…would you know anything about MySQL? Or do you know who I could talk to? I have some questions on our database and the speed of it.

Thanks for the constant help.

[Rich Spott]

Ok, well all is not well…

I jumped the gun in concluding no internal redirect errors…

after I methodically put a plugin in and tested it, i got an error, and then realized that there were two more earlier that i didnt see.

They happened at 4am, and the site was without all plugins from about 10pm or so last night until about 9am this morning.

So it doesn’t appear to be a plugin…

Please help! I took out all plugins again, except buddypress (and the bbpress support plugin from buddypress)

I really dont know what to do next.

[Rich Spott]

Nope, the error is gone.

and i checked my access logs and all of the GET requests that were looking for files that weren’t there are now 404 instead of turning into 500.

So, now my plan of attack is to add in my plugins, one-by-one, in order of most needed to frivolous. And try to call files that aren’t on my site. And see how that goes.

Thank you very much. I’ll let you know if anything changes, or what the problem seems to be. I am thinking that it must be a conflict between two plugins, because most of the plugins I use are used by lots of people without problems.

[Rich Spott]

Actually i did have some mu-plugins still running, so now everything is out, just buddypress.

With the domain mapping plugin I am using it so that bloggers can use their own domain (ie http://baseballpastandpresent.com) instead of the subdomain way (baseballpastandpresent.sportsblognet.com)

Currently we only have 2 domains which require this plugin, but I’m slated to convert at least 10 more to their own domains within the next week, but I’ve halted that until I get the site running correctly.

This is a subdomain install.

Here’s the phpinfo

http://pastebin.com/m71bb419b

[Rich Spott]

Okay, thank you for helping me, I’ll try to go through your questions one-by-one.

First I’ll let you know what I have:

Slicehost

1GB slice

Ubuntu Hardy LTS 8.04

Running Apache, PHP 5, MySQL 5.0 (followed Pickeled Onion’s walk-throughs on how to set it up, I am by no means an expert, and my very first barebones VPS was this one.)

I help run http://sportsblognet.com where we have WPMU 2.7.1 and BP 1.0, along with bbPress 1.0-alpha6

Have you tried deactivating all non-buddypress plugins, wp-super-cache in particular?

I deactivated all but buddypress, feedwordpress (because our theme will break), wp-super-cache, and doncha’s domain mapping plugin. But maybe I will remove them all for an hour to see if any errors get through

I am removing wp-super-cache right now, but it was tough to get rid of the wp-content/cache folder because it was owned by the root user. But i got it deleted and removed the wp-super-cache stuff in the .htaccess and I’ll guess i’ll have to wait to see how that goes.

Have you tried using the default .htaccess file that ships with WPMU?

I just tried to, but it won’t let me.

My current working .htaccess (minus wp-super-cache stuff)

<FilesMatch ".(ico|pdf|flv|jpg|jpeg|png|gif|js|css|swf)$">

Header set Expires "Thu, 15 Apr 2015 20:00:00 GMT"

</FilesMatch>



RewriteEngine On

RewriteBase /



#uploaded files

RewriteRule ^(.*/)?files/$ index.php [L]

RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*

RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]



# add a trailing slash to /wp-admin

RewriteCond %{REQUEST_URI} ^.*/wp-admin$

RewriteRule ^(.+)$ $1/ [R=301,L]



RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule . - [L]

RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]

RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]

RewriteRule . index.php [L]



<IfModule mod_security.c>

<Files async-upload.php>

SecFilterEngine Off

SecFilterScanPOST Off

</Files>

</IfModule>

and the WPMU standard one

RewriteEngine On

RewriteBase BASE/



#uploaded files

RewriteRule ^(.*/)?files/$ index.php [L]

RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*

RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]



# add a trailing slash to /wp-admin

RewriteCond %{REQUEST_URI} ^.*/wp-admin$

RewriteRule ^(.+)$ $1/ [R=301,L]



RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule . - [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]

RewriteRule . index.php [L]



<IfModule mod_security.c>

<Files async-upload.php>

SecFilterEngine Off

SecFilterScanPOST Off

</Files>

</IfModule>

it wont let me use the standard one, and the only difference that I can see is the expires header setting that i added.

Are there any PHP errors in your log files?

this is my current concern right now

Request exceeded the limit of 10 internal redirects due to probable configuration error.

ALERT - canary mismatch on efree() - heap overflow detected

for the ALERT error, I contacted slicehost and they upgraded my kernel, they said that has fixed other people’s problems (fingers crossed – but no errors since they did that this morning) if that doesnt work i have to go through and install php without the suhosin patch.

most of the other errors are of spam scripts trying to signup and not finding wp-signup (i changed the signup name)

what are the other listed errors in your apache log?

That’s pretty much it.

EDIT: it’s about 30 minutes later and an Internal Redirect Error just showed up in my logs with wp-super-cache out, and all but buddypress plugins out. So it doesn’t look like its a plugin.

[Rich Spott]

um….it depends on what you want and need.

We used to run WordPress MU on site5, which is shared hosting, but they do the wildcard thing for you. It was $240 for 2 yrs ($10/mo) and runs WordPress MU well, if it is a small site with not too many super active bloggers or tons of blogs. It has unlimited Ram and bandwidth, but we had complications once we started to grow, and had to move.

We are now on Slicehost, which is VPS, it starts out at $20/mo (no contract) for 256MB of Ram and 100GB bandwidth, which barely runs WPMU. Upgrade to $38/mo for 512MB and 200 GB bandwidth and you should be fine for a relatively small site. We upgraded to a 1GB Ram and 400 GB bandwidth for $70/mo, for a somewhat large site, and it runs fine. Plus you can upgrade and downgrade at anytime, and it takes 5 mins and they do it all for you.

[Rich Spott]

While this issue is being worked out

Do you mean while I get this situation worked out? Or do you mean that people are working on this because numerous people have been getting this issue?

you should either block the offending site(s) from attempting to accessing the non-existent files, or you should do a 301 redirect of the moved files–or at least the moved directories.

How do I block the offenders (especially when one of them is googlebot)? How do I do a 301 redirect of the moved files (this might be the best, except for when they dont exist anymore like old plugins that i no longer use and deleted) ?

Thank you for your prompt reply, too.

[Rich Spott]

From what I can see, the latest BuddyPress Support Plugin for bbpress is still version 1.0-RC1, even in BuddyPress 1.0 (or at least its marked that way).

There is no BuddyPress Support Plugin 1.0.

[Rich Spott]

I had this problem too, I found that it was a conflict with some of my plugins.

First, take out any plugins in /mu-plugins and try to activate the email again.

I found that wp-super-cache was causing some conflict in my blog, I took it out and it works perfectly now.

Then, if your activation works, place the buddypress plugins back in /mu-plugins and try to activate.

If these work, then one by one add the plugins that you had until you find the one that broke it.

That’s what I had to do and now my site works fine.

[Rich Spott]

if you don’t know what you’re doing…you could always go into bp-core-adminbar.php and take the code from there and just apply it where you want it.

bp-core-adminbar.php (in bp-core) has all three of those links already.

[Rich Spott]

I had this problem too when i attempted to adjust the buddypress-member theme. http://sportsblognet.com/members/rich

It’s caused by the base.css in the the buddypress-member theme calling

input, select, textarea {

width: 100%

}

you can either adjust that in the base.css (not recommended)

or you can place

#wp-admin-bar input {

width: auto;

}

below the previous call in the base.css, that way it will call the 100% width for other inputs, except for the wp-admin-bar.

[Rich Spott]

Bigkill,

glad to see that it’s working (although not as secure as you thought) as i understood it, you have to force it sitewide because the registration page is for your whole site, not just the main one.

As far as wp-recapatcha not being the best, well this might be the case, but it does prevent some spammers. I was having a problem with scripts bypassing the entire registration process and starting up profiles and blogs without entering any of the required fields, and the only way i got them to stop, was to change my “wp-signup.php” to something different like “sbn-start.php” and replaced the 4 instances of it in the “wp-signup.php” file with “sbn-start.php” and then went into “bp-core-template-tags.php” and replaced the one instance of “wp-signup.php”.

This solved the problem (crossing fingers), but I still have a few people getting by that I have to manually spam and ban, but I can deal with 2-3 a day versus waking up in the morning and finding 200 spam blogs signup over night.

Hope I helped.

[Rich Spott]

I added padding to the bottom of the members and blogs and it fixed my issue with it showing up offset to each other.

This is what I added to the theme CSS.

ul#members-list.item-list li, ul#blogs-list.item-list li, ul#groups-list.item-list li, ul#featured-member-list.item-list li, ul#recent-posts.item-list li {



padding-bottom: 10px;

line-height: 1.5em;

overflow: hidden;



}



ul#featured-blog-list.item-list li {



padding-bottom: 10px;

line-height: 1.25em;

overflow: hidden;



}

http://sportsblognet.com