[@djpaul Keymaster 14 years ago]

What screen are you looking at? The registration, or the member profile screens?

[@djpaul Keymaster 14 years ago]

Changeset 6331 was against trunk, not the 1.6 branch. If you are patching 1.6.1 with changeset 6330, then you are running a custom version, and you should let people know how you’ve changed core when asking for support. This could be relevant as this changeset affects activity, which is where you’re having problems.

Does your site *require* r6330 to work? Are you able to test it running “stock” 1.6.1 work on your upgrade installation?

[@djpaul Keymaster 14 years ago]

Please please stop posting this on multiple topics. If you haven’t had a reply yet, it means no-one’s sure what the fix is.

How did you install BuddyPress? What versions of WordPress and BuddyPress are you using? Do you have a bp-custom.php file (if so, what’s in it)?

[@djpaul Keymaster 14 years ago]

If we could recreate it, of course we’d fix it. Sometimes figuring out why bugs occur is the hardest part.

[@djpaul Keymaster 14 years ago]

Wow. This must a record for oldest resurrected thread.

Please start a new topic

[@djpaul Keymaster 14 years ago]

I believe that’s the only plugin that does this sort of thing. Knowing the author, I would be surprised if the plugin didn’t work.

[@djpaul Keymaster 14 years ago]

The built-in profile validation should never stop working. Maybe you’ve got another plugin interfering with things? What else are you using?

[@djpaul Keymaster 14 years ago]

I agree probably should do it, but it ought to be implemented in the new version of bbPress rather than BuddyPress.

[@djpaul Keymaster 14 years ago]

You’d probably have to write some custom code (or hire someone to do it for you) to only accept two people in a PM conversation. Nothing like this out of the box.

[@djpaul Keymaster 14 years ago]

Activity doesn’t have a “pending moderation/approval” concept like comments does. Right now, it’s either published or spam.

[@djpaul Keymaster 14 years ago]

1. Either. It doesn’t matter which order.

2. bbPress would continue working, as it’s a separate plugin. Deactivating BuddyPress won’t affect or delete your bbPress data.

[@djpaul Keymaster 14 years ago]

The simplest approach may be to surpress the “click here to activate your account” emails, and use something like https://wordpress.org/extend/plugins/unconfirmed/ to manually activate them.

[@djpaul Keymaster 14 years ago]

One option is to set the groups as “private”, not “public”. People can’t auto-join then.

The constant you refer to ought to work in BP 1.6+, it’s not been deprecated.

[@djpaul Keymaster 14 years ago]

I suppose you could build a feature like this, but there’s nothing out of the box.

[@djpaul Keymaster 14 years ago]

I still can’t find anywhere that BuddyPress sends emails when something happens in the forums (unless another plugin is providing this feature for you). Best I can find is if someone replies to an Activity item created by someone posting on the forum.

[@djpaul Keymaster 14 years ago]

No need for the topic written like that.

[@djpaul Keymaster 14 years ago]

I’ve just checked the code, and BP doesn’t send any emails from forum activity. We explicitly send emails for the other types of activity you’ve mentioned.

[@djpaul Keymaster 14 years ago]

The default theme with BuddyPress doesn’t have a log in widget. If you’re not using a different theme and you’re referring to the sidebar area, that’s hardcoded into the template. In this case, some extra text with a register link will appear as long as user registrations are enabled on your site.

To check, http://www.agentwp.com/enable-or-disable-user-registration-in-wordpress

[@djpaul Keymaster 14 years ago]

Are you using bbPress 1 still, or are you using bbPress 2 (aka site wide forum)?

[@djpaul Keymaster 14 years ago]

No? Only if the PHP is bad.

[@djpaul Keymaster 14 years ago]

If you’re doing anything new with forums, use bbPress 2 (aka Site Wide Forums).

[@djpaul Keymaster 14 years ago]

It was built the way it was because of architectural reasons. It’s something we want to change, it’s just as simple as no-one’s done it yet.

[@djpaul Keymaster 14 years ago]

It’s something we want to change, it’s just as simple as no-one’s done it yet.

[@djpaul Keymaster 14 years ago]

I’ve personally done a 1.2.4(ish) all the way up to 1.5.4(ish — whatever the latest version was at that time). Worked ok, I don’t think there’s a need to step through 1.5 versions.

[@djpaul Keymaster 14 years ago]

Marcy, you’re going to have to trace the AJAX request backwards and see where it’s failing. I’m assuming this is an out-of-the-box javascript rather than a custom one you’ve written.