@newrambler this is in the index.php of the buddypress theme… you have to go into the buddypress plugin –> then theme….
The site I get when I try to access the BuddyPress sites is my theme’s (twenty-ten’s) 404.php. So somewhere along the way the url points at the wrong place.
My .htaccess looks like this:
RewriteEngine On
RewriteBase /
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.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>
Any recent updates on the best configuration for W3 Total Cache – still looking…
@newrambler – for /index.php, it’s on line 26:
https://trac.buddypress.org/browser/tags/1.2.5.2/bp-themes/bp-default/index.php
@pisanojm – maybe a filter on the_time() would suffice, some might like the existing relative time. Definitely create an enhancement ticket!
You’re quite correct it does still exist which I find very odd as I seem to have a recollection of comments that said it would be / was removed.
I am using a dropdown panel BuddyPress Sliding Login Panel plugin that is very nice to have works great after member logs in with all buddypress menu for members.
I have the latest version of buddypress and I had to delete the register.php from bbpress, as is suggested above. This reduced my spam signups from around ten a day to none.
All you need to do is deactivate in BuddyPress Component Setup and just activate it when you want to use it in future.
Would like to get this working with WP 3.0 and latest BP.
I had lot of problems to stop spamblogs from signing up than I have installed Buddypress Humanity plugin and its been a month and i have not got a single spamblog signup as this plugin lets you set your own question and answer.
Thanks for all the great feedback. I think I will be avoiding a demo. This is in the developer track, so I’m going to have to try and balance features and functions with demoing cool sites. Should be fun!
@markhahnel – you should ask @sbrajesh at BuddydDev.com forums where he’s active in responding to questions about his plugins.
Thought the stray registration file had been dealt with.
As well as rename the register slug, rename the footer links as they are searched out in their default form. I also added a rule to htaccess that checked the referer page and if it wasn’t the site chucked the request to somewhere else (do need to make that somewhere interesting) also blocked any CURL requests for the register page, finally made the decision that blogs could not be created during sign up, once registered members could create blogs and this made a difference.
@tedmann – there was a register file kicking around in the bbPress forum files, and I think that was the back door into the BuddyPress system. I don’t know if that issue has been addressed in the latest BuddyPress / bbPress releases.
We stopped spam registrations almost completely on Hello Eco Living by removing the register file in the bbPress installation, and changing the url of the BuddyPress registration page.
Here’s what I don’t understand: All our recent Spam registrations are completely bypassing the BP registration form. I’ve got a tricky Humanity plugin question on there, as well as several required fields. But when I look at the accounts the spammers are creating, they have none of those fields filled out.
Is there some kind of backdoor registration option in BP or WPMU? How are they getting in?!
@jeremyltn It now works like a charm! Thanks again for this, it will no doubt become a BP essential. This should be written into the core code to be honest.
Liked it very much.A value addition to any site.
@modemlooper
When can we expect it in repo.
Thanks,
Prashant
@jeremyltn Thank you SO much for this! I’ll try it out and let you know how I get on! Great stuff!
@zanzaboonda –
To make it easier to provide help: please provide more information –
Which version of WP / BP?
Does the problem exist if you switch to the default BP theme?
Have you tried de-activating other plugins and testing whether one of them is interfering with the behaviour of BP?
@ch8rt
The BuddyPress activity loop fetches blog post activity, so yes – you can get the latest blog posts from within the activity loop.
https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-activity-stream-loop/
There shouldn’t be a problem having the login-form inside a widget ( side-bar ) as that’s how it is in the bp sidebar ( sidebar.php in bp-default theme ).
Regardless of the above, copy the form code from sidebar.php and insert it anywhere you like ( header, footer.. ), you can contain the form in a div, styling it to suit your needs.
Take note that if you are not using a child theme, your changes will be over-written when you upgrade buddypress. ( https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/ )
This should be the login/log out form used in the bp-default theme: http://pastebin.com/gngAD97g
@mvvspr @rossagrant @fashionblogs and everyone else – I’ve changed some things and added the plugin to the repo https://wordpress.org/extend/plugins/buddypress-mass-messaging.
All of the errors should be taken care of, but if you still have issues please post here http://jeremylitten.com/buddypress-mass-messaging-plugin
Quick thoughts from my iPad…
For there to be more core committers, there needs for there to be more outstanding core patchers. There are a handful of great ones already, and they are noticed and recognized for their contributions. The leads are Andy and myself, and ultimately the future of the core project is decided by us. Very similar to WordPress, we keep an eye on developer plugins to look for anything that would make a good core feature.
Feature requests are great when there are people to do create them, but the best place to talk about core development is on the trac. The forums are more for support and discussion than they are for code talk, but part of that is also because currently the forums don’t play nicely with code blocks.
I don’t think we’re closing threads unless the discussion goes severely off topic or is no longer productive. If we are, I would agree that we shouldn’t be locking topics prematurely. Regarding the codex, anyone has the ability to modify it, so if anything is out of date anyone is free to fix it.
I also agree that things will be easier for us and make more sense when buddypress.org is a website worthy of being in its own showcase. Right now it’s a basic install with lots of custom bits to help integrate wp.org plugins.
It hurts to just add committers for the sake of having committers. Commit rights are earned through writing great core patches and showing a comprehension for the direction of the core project. There are plenty of great plugin devs that have written thousands of lines of their own code, but haven’t directly contributed to core.
Ultimately it would be great if we had one developer per core component to focus on it’s future, but so far no one has showed initiative to want to make improvements to anything. Right now we’re in a transition period where the branch and trunk need to be merged before I think a few more people are comfortable writing giant patches, but that time will come.
Paul hit almost every nail on the head in his reply above. It’s great that you see the need, now fill it. 
There is a link to support forums for your suffusion buddypress pack theme at end of the post – http://www.aquoid.com/news/plugins/suffusion-buddypress-pack/
