BuddyPress.org

nahrizuladib – I’d be interested to know how you made the activity stream be the homepage, would you mind sharing that with me?

@all

I’m using these 3 plugins together and have no bot signups at all on WPMU2.9.2/BP1.2.3.

Cookies for Comments

RPX

WPMU Super Captcha

The occasional stubborn human does drop by once in a blue moon, and these few only manage to get through using RPX and an existing account, or they really take the time to fill out the registration form. Email domain banning and persistent account termination seem to be the only solutions in these cases.

Can someone give solution that users that wish to sign up dont use buddypress signup page, instead they use regular wordpress signup which is much much safer.

Hmm, interesting. The generic BuddyPress register form does seem like a bit of a sieve (though it could just be my frustration talking).

I think you would just delete/disable /registration/activate.php and /registration/register.php. You would lose the ability for users to fill out extended profile fields at signup. However, quick signups are probably preferable, with seasoned users filling out extended profile fields as needed. I’ve read at least one article via delicious.com that suggests to me that signup forms need to be as simple as possible to help users focus on getting “behind the wall” fast and easy.

excuse my ignorance of htaccess but is this even possible? and if so, how is it done?

I noticed a issue with spammers using CURL to download /registration so blocked that in .htaccess (It’s been mentioned on a thread somewhere how to)

I have a lot of problems with BuddyPress user registration in general. It seems:

– no emails are sent to the user for activation

– there is no “forgot password” feature

– there is no ability to (re)send the user an activation link, either from the user or the admin’s area.

On the emails, when I create a new user or blog via the admin area, I get a notification email, so it’s not a setup issue with the mailserver. The server is my localdomain/localhost dev box anyway. No webhost involved.

Ugh this may seem a small part of BP % wise but it seems without these features it’s really not usable. What is the deal? Can this fundamental stuff really be missing/so buggy?? It’s hard to believe.

Was this plugin working before and now it is not? If so, what has changed since then? Did you upgrade WPMU?

What versions of WP/MU and BuddyPress are you running?

If you look at the WP Plugin Repository for this plugin, others are having issues with it as well. I would suggest contacting the developer of the plugin and ask when they plan on updating it for the current versions of WP and BP.

In the admin sidebar click settings then general and on that page is a check to allow registrations.

How do I enable registration using an existing theme but I have added buddypress and buddypress template pack and I don’t see where to enable registration so people can register and post. How do I set up my theme so people can register and not using the wordpress screen but another form and can also post? This is urgent.

You need to allow people to register in Administration -> Settings

So it works? Tag the topic as resolved.

r-a-y,

I have a test install of BP on Bluehost and the email has worked flawlessly. I wonder if the problem with Bluehost (and likely any cpanel based host) is that the person installed it as an add-on domain in bluehost and not the main domain.

@ssanime

If you are hosting BP on Bluehost, there have been issues sending out email.

Try out the following:

https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions#post-45772

@ssanime-

Which versions of BP and WP are you running?

I have the same problem. users can register but they don’t receive a activation email and cannot login.

It becomes just string manipulation. Create a new function (my_funky_function) and do something like this:

function my_funky_function() {

echo str_replace( "username","", bp_get_the_profile_group_field_ids() );

}

Then replace the bp_the_profile_group_field_ids() call in edit.php (in your child theme of course) with my_funky_function().

I think that will work but it’s not tested.

Edit:

Oh, sorry, I’m sort of wrong. This is what I get in my edit.php form in the HTML:

<input type="hidden" name="field_ids" id="field_ids" value="1,3" />

Field_id 1 is the Username for me. You just need to filter that out so the str_replace call should be “1,” instead of “username”.

<input type="hidden" name="field_ids" id="field_ids" value="<?php bp_the_profile_group_field_ids() ?>" />

That line is your problem. Well, more specifically, the call to bp_the_profile_group_field_ids() which creates a list of the expected field names.

Unfortunately it doesn’t have a filter so you’d have to clone and own the function into your functions.php file and manually filter out the “username” field from the string that gets generated.

Make sense?

Oh, nope, it probably means that the code is actually checking that the field ‘username’ should be getting updated. I was sort of wondering if that would happen.

Along these lines…I haven’t seen much discussion about spammers lately.

Am I still the only one getting 100+ per day?

Please please please someone figure out how to make buddypress’s registration page reference the banned domain list!

I’m interested in this idea too. As I looked at the code, it seems like it goes through a number of steps during the registration process. I wonder if any plugin has modified/added to these steps. Is there documentation on the steps that it goes through during registration and how you could add a step into the registration process?

I think that if the low level core API of BuddyPress is strong and extensible, then ‘what BuddyPress is’ will mean different things to different people, depending on why they use it.

In a land before time, BuddyPress was actually intended to be several separate plugins, but having different components with different version numbers and dealing with the dependencies would have been a nightmare.

Now though, watching plugins merge and adapt, it doesn’t seem that unlikely.

Imagine if when you DL BuddyPress, you’re just DLing BuddyPress core, and the install routine lets you pick which additional components you might want for your social network, and it puts them in the BuddyPress directory. Not everyone needs friends, but maybe they want to follow each other. Different plugins for almost the same thing. Users should be walked through the component picking process to be able to shape their social network in a matter of minutes.

I believe the component API should be built for rapid deployment of new components. It should take care of the things we currently spend hours trying to dance around. I.E. component registration, template inclusion, URL rewriting, GET/POSTing, and it needs to give each new component its own API at the same time, so that we can easily communicate between these components and make them talk to each other in a universal way.

Then BuddyPress will become less of a “friends/activity/groups/profiles/pm” plugin, and more of a “sum of its parts” plugin.

So, the API would need to be fairly self aware, and include setters/getters/checkers for just about every routine there is for them to possibly do.

We had a ticket open about 4 months ago with a transitional API that I started for a general BP_Component class. It wasn’t much, but maybe a start?