Try reinstalling your WP3.0 system again, and see if that works in multisite setup.
Once that’s fine, try installing BuddyPress using the install automatically option in plugins
Did it really say “cheatin, uh?”
Well, i thought it will be everything allright, but when i installed my network just like in that guide, one very big problem appeared.
I set up all superadmin options, so next step should be installing buddypress right?
so i downloaded it, went to the “plugins” in my admin panel, clicked “install for all network” and…. CRACK
wordpress told me “cheatin, uh?” so i logged out, and tried to log in one more time, and nothing.
i cant log in, when i try to do this wp send me back to my homepage and tell nothing.
so i tried one more time, and now when im going to mypage/wp-login.php the site is all white,
theres nothing there. What should i do now?
@san61236
Please don’t jump in on others threads if you have a question start your own post.
You might need to check that you have allowed registration in the super-admin settings.
Oh there are many more than that as soon as you start to try and block them a new address will be used
is there a plugin that i can use to simply ban certain keyphrases in email addresses from registering? most of my spam signups have the below phrases in their urls, as well as others, i’d like to simply block all of the below them from signing up at all.
buyfioricetnow
junklessmail
trophaeum
picture-movies
stampfreemail
supermailpro
designersmail
freeeeemail
hothdvids
travel1234
freemailme
hotbabesonly
informaniac
belzy
watchathf
@djpaul You are a genius! 
I figured out what was wrong. I wanted to be sure I had your assumed setup and after deactivating my plugins everything worked. I had at some time activated a plugin called qTranslate (https://wordpress.org/extend/plugins/qtranslate/) which broke BuddyPress.
So if anybody else runs into my problem, try deactivating all plugins to see if anyone of them is causing the weird behavior.
Should a plugin like that be able to break another plugin? Do we need some sort of a plugin interoperability page to inform users what works together and what does not work together?
I have no means to test this but if this is an issue with BP 1.2.5.2, please would someone who has this issue report it as a bug on http://trac.buddypress.org? You can use the same username/password as you do for this site to log in. Thanks
What version of BuddyPress are you running, Tom? This works as it should on http://testbp.org/ which I believe is running what will become BuddyPress 1.2.6.
If I get time after work I’ll write up the URI handling process, it’s not something I can knock out in 5 minutes. So, I’m assuming you’re using stock BP 1.2.5.2, and the BP-Default theme (which you do not need to move into /themes/)? And only the BuddyPress plugin active?
Look at BuddyPress’ bp_blogs_update_option_blogname() function for an example of how to do it.
Not sure of the process but even if you haven’t got bbpress running locate and remove the file. If spambots are managing to get around hidden fields that should remain empty it suggests they are not using whatever form that protection is on.
For CURL try adding this: (but check carefully things still work!)
# trap curl registration downloaders – block in allow,deny rules
SetEnvIfNoCase User-Agent “^curl” blog_spammer
Order Allow,Deny
Allow from All
Deny from env=blog_spammer
Be careful about blocking IP ranges it’s a difficult practice and one that technically you are supposed to notify about in case innocent yet important sites get blocked, you can add further rules to the deny lines above but unless there is a very persistent IP it’s probably not worth it and likely spoffed anyway.
@tedmann – have a search on your install for the bbPress folder and remove the register.php file. I guess it doesn’t have to be activated for the file still to be there and therefore usable by the spammers.
It worked like a treat for myself and @footybible
@jimhellas – yes, I find myself using “find in files” a lot in my editor 
Finding time to write sections on the API in the documentation is step 2!
I’ve got the Humanity plugin running on our site, with a semi-difficult question. Likewise, I’ve done the htaccess trick, register slug, and so on. Haven’t blocked CURL requests (how do you do that?).
I never configured bbpress for our site. Even if I haven’t done that, is it possible that register.php file is still lurking somewhere on the site? Are there any more drastic measures I can take? We’re getting killed every morning — not just with spam signups, but spam blog posts. Would blocking the offending IPs (quite a few) be a viable solution?
Are you getting any errors? A blank site is usually called by a fatal error. Set WP_DEBUG to true in your config file define( ‘WP_DEBUG’, true ); . If you still don’t see any errors then do search through the files in wp-content/plugins/buddypress for any error_reporting(); calls and set it to error_reporting( E_ALL);
Same here, BuddyPress 1.2.5.2, WordPress 3.01 and can’t delete users.
@boonebgorges is @kebdarge meaning there isn’t one for this site?
@djpaul – I saw one closed this week, that had been open just a day or so. I think you closed it. The guy was referred to another old thread, which didn’t reach a conclusion on how to solve the problem.
I’ve also seen a user, albeit an irritating user, blocked from using the site for the ‘crime’ of arguing with a core developer. That really isn’t good practice. The user was being abusive, but not overly so; the core developer arguing with him was being equally petty though.
Amend: apology, @djpaul it wasn’t closed by you, but it was closed and pointed to a thread that finished without a working answer
That’s precisely the thing, I don’t think I modified any other files. I only uploaded themes into the theme folder and activated them. Once I tried the BP theme pack which created a conflict between two files so I removed one of them but that’s all I can remember doing.
Still, there is quite a large possibility that I made some changes I can’t remember (since I’ve been playing around a lot), which is the reason I wanted to know how the flow for URI handling in BP is. Then I could trace myself through the files and methods and see where things are going wrong (and see if I changed something).
I have tried to delete and reinstall BuddyPress but still no positive results.
Since you’re using the filter I posted, I would manually setup a group loop. Then in this loop, I would use the bp_core_fetch_avatar() function with the “html” parameter set to false (view the full function and parameter list in /bp-core/bp-core-avatars.php).
Doing this will return the URL of the avatar, then you can manually define the width and height in an IMG tag.
DSParticipant
Found the cullprit; the ‘SI Captcha’ plugin was preventing it because of a wrong set file permission.
Check the plugin settings page and it will say what is wrong.
hi @r-a-y
I am using your code given at : Click Here
I am using this plugin:https://buddypress.org/community/groups/jet-group-could/
When I browse user profile -> my groups, the group avatars in the sidebar become thumbails even though I have set 25X25 size in this plugin. Is there a way to fix the size if avatars displayed in the sidebar? I want any avatar showed in sidebar to be 25X25
thanks.
