[Aeryn-Lynne]

I’ve tried recreating the error to get an error-log, but nothing so far.

I was able to recreate the error though where turning off xprofile would mean that pending friendships and the invite friends to groups areas would show “no pending friendships” or a blank list respectively.

Sorry I couldn’t be more help on this @djpaul.

[Aeryn-Lynne]

Oops! Sorry didn’t see your message initially. I think the error would generate in the log when someone would check to see if they had a pending friendship? The logs didn’t have a specified page from what I could see.

I can try to recreate the error and give you that log…

[Aeryn-Lynne]

Nevermind, I’ve figured out what to change to make wp-admin/profile that place to go.

Again, thanks for your help on this!

[Aeryn-Lynne]

I’m currently not using a cache plugin until our site is truly out of beta, just so that I can ensure everything sets up well.

The database name is correct/exists, I did shut off the xprofile extension in buddypress though. I have users creating their info in the wp-admin/profile.php section so I didn’t need xprofile to run.

It did work initially, as I had been able to confirm friendships on the front end before. It was probably before I turned off xprofile as well….

So I’ve just turned xprofile back on and can now find people to invite in groups and pending friendships. Problem solved, woot!!

But now the xprofile area is back which for me is an issue. Is there any way of disabling the xprofile form so that users must edit their info in wp-admin/profile.php? For this site its less work if all member info remains and is edited there only.

Thanks for helping me fix my initial issue @djpaul!! I’ve been tearing my hair out on this, lol.

[Aeryn-Lynne]

Sorry to be a pain, but does anyone have a suggestion? For me this issue is a high priority (the site will be seen by a slew of potential new customers for my client in less than a week’s time). I really need to find a fix for this…

[Aeryn-Lynne]

If you have access to the database, I would either a: delete/drop the instances of the old user entirely so there is no issue for new subscribers with similar needs, OR b: go into the specific area of where the blog name sits in the database and edit the name field to “OLD_name of blog”. I’d expect that you’d really only need one character difference in the OLD filed for someone else to use the original blog name.

It might confuse Google and SEO for a bit if the old blog was active for a long time, but if you’re not concerned about that, there shouldn’t be any issues.

I’d like to add a caveat though… Before you do *anything* to your database, please back it up to your computer harddrive first, ’cause if the suggestions I give you turn out to create more errors you’ll probably need to import the untouched database to fix any issues (and its good practice to make a back up anytime you decide to work directly within your database).

[Aeryn-Lynne]

Woot! Glad it worked @bojan85

[Aeryn-Lynne]

Assuming you have a similar setup…

Go into your members folder directory in your theme and open the index.php file. (Theme>members>index.php)

Look for any code that mentions a sidebar and delete it. Or if you have a full-width template, copy it and paste it into the members>index.php file (around the members directory code of course.)

Hope that helps…