BuddyPress.org

Seems that only fixed the admin panel problem.

However it’s throwing up errors on the front end now.

To be honest I think this plugin is maybe outdated.

I’ll list here my site’s configuration, and what errors I’m getting in-case anyone fancies making this plugin work as it should.

OK.. Groups and Blogs are disabled site-wide (Except for the main site blog).

The setting “Allow new registrations” is set to “Only user account can be created.”

And “Registration notification” set to “Yes”

1st problem (As previously mentioned in this thread)… When I go to the admin panel and try to edit the options for the plugin, and hit save, it throws up the errors that I posted here:

https://buddypress.org/forums/topic/moderate-members?replies=1#post-33514

I managed to get rid of those errors by doing as mentioned here:

https://buddypress.org/forums/topic/moderate-members?replies=1#post-33517

However… it turns out that was not a fix for the plugin, so I reverted the file back to original state.

OK, I couldn’t edit the emails that would be sent out due to those errors, but I could of worked around that (editing within the file itself)… so I continued to the next step, which was to try and create a new account, to see if the plugin actually done what it’s supposed to.

After entering all my required fields, and hitting the submit button, I was taken to the upload avatar page. I was also shown the “Check your email address for your activation email” notice. Also, at the top of the page these errors appeared:

Warning: implode() [function.implode]: Invalid arguments passed in /home2/puezq/public_html/mysite.com/v2/wp-content/plugins/bp-registration-options/bp-registration-options.php on line 639

Warning: implode() [function.implode]: Invalid arguments passed in /home2/puezq/public_html/mysite.com/v2/wp-content/plugins/bp-registration-options/bp-registration-options.php on line 642

Since I know only very little php, I had a look to see what those lines were in the plugin php file, but done nothing with them. Here are those lines:

639 $bp_groups_str = implode(",", $bp_groups);

642 $bp_blogs_str = implode(",", $bp_blogs);

So I’m guessing these errors are showing because I have blogs and groups disabled on the site?

However the plugin php file is full of terms relating to blogs and groups, so I saw no point just removing those lines from the file as other errors would appear from somewhere… surely?

Anyway, to see what happened next- I then uploaded an avatar, successfully. The errors at the top of the page disappeared when it was uploaded.

I then clicked on the activation link in the email I received, and logged into the site. I was able to EDIT my profile and browse the site pages normally, but not able to view member profiles, my own public profile, or even view the members search page.

I then received an email saying there was a new member registration (to my admin email)… and the notice also appears in the admin panel saying there’s a user awaiting moderation.

And that’s where Im at.

Come to think of it, and after having read through this post several times now- It seems that the plugin’s actually working… with the exception of those errors that are flagging up in the admin panel (when editing the emails that will be sent out), and at the top of the front end page. Hopefully one of you guys can tell me how to get rid of those errors… or at least the ones on the front end.

This truly does sound like a fantastic plugin, but with non-existent support at the forum link in the README.txt file, I think it can only carry on living if one of you geniuses are willing to fix the bugs.

Unless anyone knows of another plugin that will allow new member moderation? (I have searched, but couldnt find anything).

Found this in bp_core_activation.php:

/***

* bp_core_disable_welcome_email()

*

* Since the user now chooses their password, sending it over clear-text to an

* email address is no longer necessary. It's also a terrible idea security wise.

*

* This will only disable the email if a custom registration template is being used.

*/

function bp_core_disable_welcome_email() {

if ( '' == locate_template( array( 'registration/register.php' ), false ) && '' == locate_template( array( 'register.php' ), false ) )

return true;



return false;

}

add_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

So I guess I could just remove this function?

Is sending that password really such a “terrible idea security wise”? Are criminal gangs intercepting these emails to break into WordPress accounts?

EDIT: Yes, removing that function works. A regular WPMU welcome email is sent.

But the password in the email is eight numbers instead of the eight letters password I’d entered. Why?! Does Buddypress do its own encryption on the password? Does it use other tags or “placeholders” or whatever they’re called to call the password?

Going to sit in a corner and cry…

Peterverkooijen: Of course, the goal is certainly *not* to disable the standard registration procedure — if that was the case, neither I would be interested in doing this. The point is to /support/ Open ID registration, not to enforce it (besides, IMO it would be against any true open ideology to do that; how is enfocring open-ness open? )

Xevo that is another thing that would be great.. They way I thought about that issue is to give members 2 options upon registration:

1: Simple blog (like you described)

2: Advanced blog (a fully featured WordPress blog like we have currently)

And the options for admins to disable one of the two if they rather have all users to have simple/advanced blogs

And are you saying I can already implement the BP menu on al blogs with the global header plugin, without any new code being written?

Ok, I sort of “solved” the problem by editing the message in /buddypress/bp-core/bp-core-signup.php. I wrote that registrations are disabled and added a link to the application form. It’s quick and dirty, but works for now

pxlgirl.

sigh

I:

— installed BP through wpmu plugin admin without any error messages.

— have not altered any directories, save for moving bp-themes to wp-content as instructed in setup instructions.

— have not touched any php files, save for bp-core-adminbar.php

— have only added the code above.

— am not using supercache.

— have cleared computer cache three times.

I’m going to have to find another solution. Maybe find the language “create a blog” and “blog registration has been disabled” and make it say something else. Thank you for your help, though.

In the meantime, can someone either a) address my original question and create a plugin (not that I’m demanding someone do work for me) or b) add something to the BP admin where you can turn off “create a blog” instances, or c) any other solution that I am clearly not well-versed enough to think of.

thanks.

Thank you, Jason. I’ve cleared my cache, as well as had two other people try this (restarting server not an option, unless my host can be asked to do so….)

Let me walk through what I’ve done:

• In wpmu site admin, “Only user account can be created” is enabled.
• Within bp-core-adminbar.php, I replaced this code:

echo '<li' . $alt . '>';

echo '<a>loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';

echo '';

• With this code from the patch:

if ( bp_blog_signup_enabled() ) {

echo '<li' . $alt . '>';

echo '<a>loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';

echo '';

}

• Saved and re-uploaded to buddypress/bp-core
• We created a new subscriber account to test. New user sees:

— “My Account” in admin bar, with “Create a blog” on flyout

— “You haven’t created any blogs yet, create one” on [profile] > Blogs > My Blogs

— “Blog registration is currently disabled” on [profile] > Blogs > Create a Blog

All “Create a blog” references should be gone, no?

Any obvious misstep?

If that means what I hope it does, I offer myself as a life-long fan

And can now gratefully retire from hunting where I can edit the text “Blog registration is currently disabled”

The FB-Connect issue was successfully addressed by removing the $DIM variable from fbconnect.php. However, this no longer seems to be effective and the error message I’m receiving seems to be complaining that out of 5 variables in fbc_get_avatar(), one is missing ie;

Missing argument 5 for fbc_get_avatar()

There are 5 variables here and I’ve removed one. However, even if I replace it so that there are now “5”, I still get the same error.

– Steve