I had this same problem. I ended up doing a couple things. I made sure all my other plugins were disabled, I reinstalled the forum, and I made sure I was using a standard buddypress theme. One of those things seemed to fix the problem and my buddypress plugin went from fatal error to saying it was activated.
WMPU 2.8.2 BP 1.03 getting the same error FWIW
Any luck with bad behavior? I was having good success with wp-hashcash but recently found it was blocking all registrations. Even a legitimate one could never get off the wp-signup page. I finally had to disable it so people could register, and now I’m back to getting splogs again. All of them seem to be a name then numbers (angie539034). Very frustrating.
I’m getting the same thing as well. As admin I had an original account set up. Set up a test account with facebook connect. Deleted it. Now it keeps coming back. I love the ease of the plugin for new users but it still needs some tweaking.
Andy, the new theme is top notch! Really nice work. I can’t wait to see some member submitted themes showing up on the theme page.
Still getting the same problems with r599 too.
Ticket is here –> https://trac.buddypress.org/ticket/180
Glad I’m not the only one.
Here is the full call
<li id="uid-Array">
<img class="avatar" width="50" height="50" alt="" src="http://utahmodern.org/wp-content/blogs.dir/1/files//2008/10/dsc-0002-32-1-avatar1.jpg"/>
<h4/>
<span class="activity">active 24 seconds ago</span>
<div class="action">
<code><a href="http://utahmodern.orggroups/7/invites/remove/Array">Remove Invite</a></code>
</div>
<code></code>
other members appear to be ok, just the admin that’s jacked up.
<li id="uid-6">
<img class="avatar" width="50" height="50" alt="" src="https://secure.gravatar.com/avatar/6280316883ec4d884420975a9769b8f2?d=wavatar&s=50"/>
<h4>
Michelle Fitch
</h4>
<span class="activity">active active 1 hour, 21 minutes ago ago</span>
<div class="action">
Remove Invite
Here’s a clue, source code reveals <a id="uid-Array" class="remove" href="http://utahmodern.orggroups/7/invites/remove/Array">Remove Invite</a>
I don’t know where the utahmodern.orggroups is coming from but that is why I can’t remove old invites and keeping getting more each try.
New user ID set up. For some reason it is still only sending out invites to the original site admin. I even went as far as to drop that old user entirely from wp_users
Thanks guys. I have created a new user and I have updated the wp_bp_friends rows so that the new user has all the friends of my old admin. Same with groups. Looks like it should work fine now.
Update. #1 I was able to find the row in wp_bp_friends where the deleted member was still showing up as a confirmed friend. Once I dropped that row, the member no longer shows up for invites.
Seems like it is only a problem when the invites come from my user id. If someone else does an invite it works fine.
I know I’m talking to myself here, but any ideas? I have downloaded the latest from svn, disabled all plugins, WPMU 2.6.3.
Every time I try and invite someone to a group, it says that they were invited but really it just invites myself. If I go back to the invites tab for that group I can see myself invited multiple times. Even if I remove myself, the next time I invite someone (even one person) it multiplies the number of invites it sends to me. I’m up to 21 invites for one click. No invites are making it out to anyone else besides admin. Kind of frustrating.
Looks like when I go to the Invite tab even though my friends show up in the check boxes, I only see my avatar repeated to the right.
SLC, olympus cove to be exact. You?
http://utahmodern.org
Still not officially launched, but running the latest from buddypress.
Custom theme, seems to be working for me.
http://utahmodern.org/about/
I’m not using the home theme either, although I do have it in the proper folder. Have you replaced all the files with the latest from the trunk?
Looks like I forgot to update my buddypress-home and buddypress-member themes. It’s all better now.
I’m getting the same error with the new trunk..
I didn’t see any difference with the htaccess code above.
