webdevstudios / buddypress-registration-options Goto Github PK

"This plugin breaks all the javascript on the default Buddypress templates. I'm not entirely sure why (it doesn't generate any console errors - but it prevents any of the input elements for activity, forums etc from being rendered)."

Make it so admins of individual sites can manage the user list, not just the super admin. Will help those using WP for SaaS instances and need to allow others to maintain their own subsite.

Warning: Missing argument 2 for wpdb::prepare(), called in /home/content/c/s/l/_/html/training/wp-content/plugins/bp-registration-options/includes/admin.php on line 19 and defined in /home/content/c/s/l/_/html/training/wp-includes/wp-db.php on line 990

Is it possible to block logged out users completely at this point? Is that part of the map_meta_cap bit that I have going for the bbPress addon.

I think this may be part of user confusion. Also most definitely a "bug" because users are thinking it does this, and wanting it to completely exclude and we're not quite offering that yet.

Are there any settings within BuddyPress we need to make sure are being set?

"When any user logs into to site and goes to their dash board they will see the message:

You have "x" new member requests that need to be approved or denied. Please click here to take action.

If they click, they get:
You do not have sufficient permissions to access this page.

But, of course, they should not ever see that message to begin with :-("

"I have an non-approved (waiting approval) user who can post to the bbpress forum at my site. I have all the right settings - both check boxes in the BPRO settings checked."

Save an option when a user is banned and then use it to catch and prevent the IP from registering in the future.

Warning: in_array() expects parameter 2 to be array, null given in \bp-registration-options.php on line 1594

Check with fork for differences and fixes:
https://github.com/jibbius/bp-registration-options-wp3.5
--give credit

WP User Frontend Pro and the Buddypress Integration Add On to make a custom registration form.

http://wordpress.org/support/topic/approval-process-breaks-half-way?replies=3#post-4846400

The built-in forums from yesteryear are gone and bbPress is standalone. We'll need to find a way to prevent users from seeing those pages when not approved.

Ideas:
grab bbP settings for which page is the forum, redirect
check for CPT
check post content for bbpress shortcodes.

http://wordpress.org/support/topic/deny-button-doesnt-work?replies=13#post-4728324

$_POST['Save'], $_POST['Moderate'] etc. make something all lower case and underscore separated. perhaps prefixed.

http://codex.wordpress.org/Function_Reference/wp_localize_script

When the email is sent to confirm a new member
: username (email) would like to become a member of your website, to accept or reject their request please go to http://deltapialumni.com/wp-admin/admin.php?page=bp-registration-options&view=members

The link gives me the following: You do not have sufficient permissions to access this page.

4.1.1
#29 localization typo
#28 make sure emailed urls are properly spaced around words.

4.2
#30 Hooks for everything.
#27 BP 1.8 testing
#20 bbPress limiting
#17 Banning.

It looks like the function wds_bp_registration_options_bp_before_member_header is missing in plugins/bp-registration-options/includes/core.php

How can we leverage this for admins? :D

"When I ban a new member, they still come back and register again. The same ip number. This does not seem to be working for me, or have I done something wrong in the settings."

This would involve more of a complete rewrite, but a sound idea.

Found in core.php line 221.

Particularly for determined spam users.

http://wordpress.org/support/topic/checkbox-to-deny-fake-profiles-without-sending-any-messages?replies=2#post-4907836

Right now, they shouldn't get past the activation key stage. If they're using banned credentials, they'll have their account silently deleted.

Admin should get email notifications that someone with a banned IP and/or email tried to register.

Catchable fatal error: Object of class WP_Error could not be converted to string in /home/fmthost/public_html/memberswjc/wp-content/plugins/bp-registration-options/includes/core.php on line 229

Notice: Object of class WP_Error could not be converted to int in /Applications/XAMPP/xamppfiles/htdocs/wp/buddypress/wp-content/plugins/bp-registration-options/includes/core.php on line 206

Notice: Trying to get property of non-object in /Applications/XAMPP/xamppfiles/htdocs/wp/buddypress/wp-content/plugins/bp-registration-options/includes/core.php on line 221

Notice: Trying to get property of non-object in /Applications/XAMPP/xamppfiles/htdocs/wp/buddypress/wp-content/plugins/bp-registration-options/includes/core.php on line 222

"If you are thinking about integrating BP Registration Options with Gravity Forms Registration Add On then a list of developer hooks and filters for the GF Registration Add On can be found at:

http://www.gravityhelp.com/documentation/page/User_Registration_Add-on_Developer_Docs

The one that looks particularly interesting is:
gform_user_registration_add_option_group
Used to add a group of options to the "Additional Options" section of the User Registration Feed. Useful when you want to add one or two options without requiring a whole section.

You could potentially add a BP Registration Options choice to the Gravity Forms Additional Options menu."

/**
 * GF Registration Process Set User to Not Authenticated to enable verification
*/

function gf_bp_profile_activation( $user_id ) {
    global $wpdb;

     //Update the user status to '69' which we will use as 'not activated' (0 = active, 1 = spam, 69 = not active)
    $wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET user_status = 69 WHERE ID = %d", $user_id ) );

    if ( !is_multisite() ) {
        $activation_key = wp_hash( $user_id );
        $userdata = get_userdata($user_id);
        update_user_meta( $user_id, 'activation_key', $activation_key );

        if ( apply_filters( 'bp_core_signup_send_activation_key', true ) ) {
            bp_core_signup_send_validation_email( $user_id, $userdata->user_email, $activation_key );
        }
    }
}

add_action( 'gform_user_registered', 'gf_bp_profile_activation', 11 );

What does this plugin do, as of $current version.

What does this plugin not do, as of $current version.

Does it offer support for bbPress?

Does it account for multisite super admins being the only ones able to edit users?

Is this a good plugin to help prevent spam coming into my whole site?

1- The confirmation link was being sent to users before admins confirmed that user. Therefore, we had to edit the code to not send the confirmation link. Instead the users got a message telling them that their account is under review. We then just look at the email and the usermail and make a decision.

This way, an administrator can remove IPs and/or emails from the listings if they need to.

http://wordpress.org/support/topic/translation-88?replies=2

Hey Brian, curious on your thoughts for the next version number with what I did the past 4 days or so. Does this look like a 4.1 release? or should I move it down to more a 4.0.2

Make sure the BP member count is properly reflected depending on user status.

From the forum:

The user's access wasn't restricted after registration. As the administrator, I didn't get an email that the user had registered. There wasn't any diagnostic information that I could see, so I wasn't able to troubleshoot. Any suggestions on how to move forward? I'm using WP 3.5.1, BuddyPress 1.7.2, bbPress 2.3.2.

Right now, the wordpress.org repo says "Moderate new BuddyPress members, fight BuddyPress spam, set BuddyPress Groups or Blogs/Sites new members can join on the registration page. "

However, last looked, the Groups/Sites join limit isn't present, unless I simply missed that setting. Do we need to update the text that's in the header to more accurately present what the plugin currently does?

Review everything here
http://wordpress.org/support/topic/activation-causing-problems?replies=14

http://wordpress.org/support/topic/my-patch-to-fix-it-with-wp35?replies=12
http://wordpress.org/support/topic/some-problems-after-updating-wp-to-35-and-bp-to-162?replies=18

Make sure all incoming registrations must be moderated, when specified.

Hi Michael Beckwith asked me to post this idea over here from the Wordpress forums. Thanks

Would it be possible to check the user's forum role upon approval of their registration and update it to participant?

Something like this: (Hooked into the approval process.)

if (user_status != '69) && (forum_role = bbp_spectator) {

update forum_role to bbp_participant}

This way, upon registration and first login, their forum role could be set to 'spectator' using the auto process in bbPress. Then, when a user is approved by the admin it also does an automatic update of their forum user role to participant.

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'wds_bp_registration_options_bp_before_member_header' not found or invalid function name in /nfs/c07/h01/mnt/112059/domains/womenunitedfc.com/html/wp-includes/plugin.php on line 406

As per http://wordpress.org/support/topic/blank-new-member-request-admin-notifications?replies=7, WangGuard is deleting users in the middle of the process or before we can properly fetch user data. It seems we get a user ID but before we can get the info for it, the user gets deleted and we still send an email. Empty values result.

I think this is something we should incorporate support with, the best we can, because our plugin is likely to be used with plugins like WangGuard.

Ideas:
review user ID fetching and info fetching before the email is sent
check for hooks in wangguard that indicate the user has been deleted already. Stop if yes.
http://wordpress.org/plugins/wangguard/

Unless a more elegant way can be found, put this inside the $_GET check in wds_bp_registration_options_bp_core_activate_account() in core.php

//Somehow the WP-FB-AutoConnect plugin uses $_GET['key'] as well for user IDs. Let's check if the value returns a user.
$is_user = get_userdata( $_GET['key'] );
if ( $is_user && $bp_moderate ) { //if it IS a user, and $bp_moderate is still true
    $bp_moderate = false; //lets set it to false
    $sql = 'UPDATE ' .$wpdb->base_prefix.'bp_activity SET hide_sitewide = 0 WHERE user_id = %d';
    $wpdb->query( $wpdb->prepare( $sql, $user_id ) ); //and update the hide_sitewide column.
    return; //and then exit out like a sir.
}

--- includes/core.php Mon Oct 22 22:31:36 2012
+++ includes/core.php Tue Feb 05 23:19:49 2013
@@ -15,7 +15,7 @@
add_action( 'init', 'wds_bp_registration_options_core_init' );
function wds_bp_registration_options_core_init(){
global $bp_moderate, $bprwg_privacy_network, $wpdb, $bp, $user_ID, $blog_id;

• if ( !is_admin() ) {
• if ( !current_user_can( 'edit_users' ) ) {
  if ( is_multisite() ) {
  $blogid = $blog_id;
  switch_to_blog(1);
  @@ -31,14 +31,16 @@
  if ( $bp->current_component && $user_ID == 0 && $bp->current_component != 'register' && $bp->current_component != 'activate' ) {
  if ( $bp->pages->register->slug ) {
  wp_redirect( site_url().'/'.$bp->pages->register->slug );
• exit;
  } else {
  exit();
  }
  //if logged in and not approved then redirect to their profile page
  } elseif ( $bp->current_component && $user_ID > 0 && ( $bp->displayed_user->userdata == '' || $bp->displayed_user->userdata != '' && $bp->displayed_user->id != $user_ID ) ) {
  $user = get_userdata($user_ID);
• if ( $user->user_status == 69 ) {
• if ( $user->data->user_status == 69 ) {
  wp_redirect( $bp->loggedin_user->domain );
• exit;
  }
  }
  }
  @@ -197,7 +199,7 @@
  *
  */
  add_filter('bp_after_activate_content', 'wds_bp_registration_options_bp_after_activate_content');
  -add_filter('bp_before_member_header', 'wds_bp_registration_options_bp_before_member_header');
  +add_filter('bp_before_member_header', 'wds_bp_registration_options_bp_after_activate_content');
  function wds_bp_registration_options_bp_after_activate_content(){
  global $bp_moderate, $user_ID, $blog_id;
  if ( is_multisite() ) {
  @@ -205,7 +207,7 @@
  switch_to_blog(1);
  }
  if ( $bp_moderate && isset( $_GET['key'] ) || $bp_moderate && $user_ID > 0 ) {
• $activate_message = get_option('bprwg_activate_message');

• $activate_message = stripslashes(get_option('bprwg_activate_message'));
  echo '

  '.$activate_message.'

  ';
  }
  if ( is_multisite() ) {
  @@ -220,7 +222,7 @@
  *
  *
  */
  -add_action( 'bp_core_activate_account', 'wds_bp_registration_options_bp_core_activate_account');
  +
  function wds_bp_registration_options_bp_core_activate_account($user_id){
  global $wpdb, $bp_moderate;
  if ( $bp_moderate ) {
  @@ -243,5 +245,5 @@
  }
  }
  }

  +add_action( 'bp_core_activate_account', 'wds_bp_registration_options_bp_core_activate_account');
  ?>
  \ No newline at end of file

"Works great but it would be better if texts for approved or denied messages would accept

a) HTML standard codes and/or
b) sending text only emails (WordPress default)
"

link in my notification mail does not appear as a link: appears as '.... go tohttp://...

found in core.php
' .... request please go to', 'bp-registration-options')...
replaced by
' .... request please go to ', 'bp-registration-options')...