Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'disable registration'

Viewing 25 results - 576 through 600 (of 647 total)
  • Author
    Search Results
  • #54062

    In reply to: BuddyPress Spam

    Ruth Maude
    Participant

    I’m struggling with a lot of spam registrations.

    – a lot list country entry as random characters “Ot9XLfiFD7WNCu” Is there a way to set Country so it has to be a legit one?

    – a lot come from email addresses such as “myspacee.info” “@mysace.info” Is there a way to force email confirmation … so they have to receive an email and click on a link to confirm registration?

    – is there a way to mark someone as a spammer and delete them at the same time in the admin?

    Sigh… I don’t have time for this so I may give up.

    Would be nice if a site user can “Flag” a spam entry to disable the user.

    #6591
    Jeff Sayre
    Participant

    Many people have been inquiring about privacy options in BuddyPress. Some of you are aware that I am currently coding a Privacy Component for BuddyPress. I decided that it is time to fill the community in on my component, providing more details and a timeline.

    My Privacy Component will be entering a private alpha early next week. After the alpha phase is complete, it will then be available as a public Beta. If it goes well, and Andy likes it, it may be included in the BP core for version 1.2. If you look at the BP roadmap, you will see that that is when privacy filtering is scheduled to be included in core.

    In this screen capture of one of the privacy setting screens, you can see that there are actually six user classification filters that can be chosen for each BP object. The sixth option, “Relationship Mapped”, is made available by a separate plugin which I’ll be releasing later. The default Privacy Component will offer five levels.

    My current estimated release date for the first public beta is the week of October 5. This date may change depending on the feedback from the alpha phase.

    More Details

    This is taken from the Privacy Component’s current readme.txt file:

    BPAz is a privacy control component for BuddyPress that provides a site’s users a mechanism with which to control who has access to which pieces of their personal data.

    == Description ==

    The BuddyPress Authorization component (also referred to as BPAz, BP-Authz, or BuddyPress Privacy Component) is a BuddyPress component that allows users fine, granular control over who has access to which pieces of their personal data. It provides this service by hooking into BuddyPress’ core functionality, thereby giving users the ability to control (grant or deny) access to each piece, or grouping of, their personal data.

    The term “auth” is often used interchangeably for authentication or authorization. There is significant difference in meaning between them. Authentication is not authorization. Authorization is not authentication. Authentication must come before authorization. Authentication is handled by WPMU, initially by the registration process and subsequently by the login script. Authorization deals with verifying and managing the access rights a given authenticated user has to certain objects.

    Because of this confusion, the process of authentication is now often referred to as A1, or AuthN, or simply Au. The process of authorization is now often referred to as A2, or AuthZ, or simply Az. Since authentication must come before authorization, the A1-A2 ordinality of the terms is evident. This also explains the alternate names BPAz and BP-Authz.

    BPAz deals with authorization by verifying and managing access rights an authenticated user has to other’s objects–although a user may choose to expose their data to non-logged in users as well.

    The core BuddyPress objects on which rights can be set:

    • xprofile fields
    • activity stream actions
    • friends list
    • groups list
    • messaging
    • blogs
    • wire
    • status updates

    The basic access levels configurable per object (some objects offer only a subset of these rights):

    • allow/deny anyone (globally public or globally private). This is accomplished by setting an object’s viewing rights to either “All Users” or “Only Me”
    • allow only “Logged in Users” to view a given object
    • allow only friends to view a given object
    • allow only a specific list of users to view a given object. This is also called per user access control. This is accomplished by setting an object’s viewing rights to “These Users Only” and then entering a comma-separated list of usernames (a member’s login name) in a textbox that becomes visible.

    NOTE: Per relationship-type access control is possible if you use my BuddyPress Relationship Mapping plugin. For instance, allow by friend, colleague, partner, client, customer, fan, etcetera.

    Site Administration of BuddyPress User Privacy Tools

    Site administrators have ultimate control and oversight over the configuration of BPAz’s features and functionality via an additional administration panel under the BuddyPress menu hierarchy. The BuddyPress Privacy Component is enabled by default for all object groupings. However, Site Administrators can disable user-configurable sitewide privacy, or even individual privacy control objects, by using the Privacy Settings administration panel. As the Site Administrator, you will always be able to see each user’s complete content. Users do not have any options to hide content from Site Administrators.

    #52171

    In reply to: Fighting Splogs

    r-a-y
    Keymaster

    You also have to secure your bbPress install from spam signups (if you have forums installed).

    Things you’d want to do is disable registrations in bbPress and redirect attempted signups to WPMU’s signup page.

    #52098
    pxlgirl
    Participant

    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.

    #6475
    pxlgirl
    Participant

    Since I am going to disable user registrations, I would also like to remove any related link from my page, which would be on top next to the login button, on the Buddybar and wherever else it might appear. What lines in which files do I have to remove to do that?

    pxlgirl.

    #51849
    elemsee
    Participant

    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.

    #51806
    elemsee
    Participant

    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?

    #51791
    elemsee
    Participant

    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”

    elemsee
    Participant

    I’ve done a fair bit of searching without finding an answer, so please excuse me if this is asked and done with.

    I wish for our members to be able to participate in blogs that only the site admins have created. Thusly, the option for users to create blogs is turned off in the WP admin.

    However, the “create a blog” option still exists in 3 places in Buddy Press:

    My Account > Blogs > Create a Blog

    My Blogs > Create a Blog!

    (member page) > Blogs > Create a Blog

    Clicking any of these takes the user to a “Blog registration is currently disabled” message… I feel this makes us look as if we forgot something or made an error.

    I’d LIKE to be able to remove these “create a blog” references, at the very least, if not limiting users altogether. I’ve tried following Burt’s advice in “Limit Blog Creation to Admins,” but must confess that that level of php work is as yet beyond me. (http://buddypress.org/forums/topic/limit-blog-creation-to-admins)

    Has anyone thought of a solution for this or can think of a way to accomplish it without needing to manually edit a lot of php?

    Thank you guys, any answer would be appreciated.

    #50967
    Paul Wong-Gibbs
    Keymaster

    Just disable blog registrations in your Site Admin > Options panel. And please take some time to do a cursory search of Google or the WPMU forums as this is a basic question and nothing to do with Buddypress.

    Paul Wong-Gibbs
    Keymaster

    Am I reading this right? Couldn’t jorrie just disable user registration?

    #50751
    r-a-y
    Keymaster

    1) With WPMU and a user account, you can comment on any blog (provided you’re logged in)

    2) This is possible… that page is a template file, so you could customize that with whatever you want.

    3) If you already have users blogging on WPMU, BuddyPress will detect these user’s blogs (I’m quite sure BP detects them!). BP groups and forums build off of WPMU’s userbase; groups being a BP thing and forums being a BP/bbPress thing. So when you install BP, your users will have to configure their groups and forums from scratch.

    4) Not sure on this one. There’s an option in WPMU to disable blog registration, but if you do that I think it will disable blog registration sitewide. This would be a better question for the WPMU forums.

    5) BuddyPress does indeed utilize bbPress for forum functionality. The next version of BP will make it easy to integrate with. Right now, it still requires some grunt work.

    You say want a forum for each blog? That’s a little overkill… but something like this can be accomplished with groups and a BP plugin (Marius Ooms’ groupblog plugin or Burt Adsit’s BP Community Blog plugin)

    6) Yes you can list all blogs on a page using a WPMU function.

    Hope that helps!

    #50707
    creede
    Participant

    Any luck with bad behavior? I was having good success with wp-hashcash but recently found it was blocking all registrations. Even a legitimate one could never get off the wp-signup page. I finally had to disable it so people could register, and now I’m back to getting splogs again. All of them seem to be a name then numbers (angie539034). Very frustrating.

    #50547
    3318273
    Inactive

    Tried checking your site out but I can only see a wp-theme. Clicking registration gets me this:

    http://current_site_domaincurrent_site_path/

    Have you disabled it or is more things not working?

    #6044
    3635122
    Inactive

    Hi everyone

    Ok, here we go again. I have WPMU v2.8.2 and BP 1.0.3 installed. Also, the latest version of BBPress, FB-Connect, reCaptcha and Askimet.

    About a week ago, despite having ALL registrations/posts/comments completely disabled, a person/bot was able to sneak through and register for an account.

    I posted back here and asked what I should do about this and was advised to install reCaptcha (which I did).

    Now this morning I went to my BP site and see that once again someone has registered for an account and not only that but they have also used my FaceBook name as their sign-up name but when I click on their icon, instead of taking me to their BP profile, it just refreshes the page. A further look shows that they used a FaceBook URL but used several trailing slashes in the address and no email address was provided.

    At first I thought that perhaps this account had been automatically created when I logged into FaceBook under my FB developer account so I tried to recreate this but no dice.

    It looks like once again, someone has gotten through. I have no idea what their game/gig/motive was in creating an FB account using my name or how they even got in. I know it wasn’t a family member or friend playing a joke on me either (as has been suggested).

    Any ideas?.

    Thanks, Steve

    #49980
    3635122
    Inactive

    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

    #49979
    José M. Villar
    Participant

    Nope, Im afraid there´s not a newer version.

    1.1 was coded by Andy himself, and there are no signs that it is going to be updated. He has made clear many times that its up to Buddypress community to continue with the update of Facebook connect plugin.

    If I had coding skills, I would have updated it a long time ago, but I am still busy understanding how BP works ! ;-(

    #49978
    3635122
    Inactive

    Hey, thanks for all the great help!.

    I’ve installed reCaptcha and it works good. Won’t reCaptcha interfere with Askimet though since they are both anti-spam plugins (just wondering)?.

    I couldn’t find any place in the latest version of BBPress to disable new registrations. Where would I go to find this option?.

    I’m still stumped on the FB-Connect error. I’m currently using version 1.1. Is there a newer version (or an easy-to-install patch available?.

    Again, thanks so much, Steve

    #49976
    plrk
    Participant

    If you have disabled registration on your WordPress MU installation, and users are still signing up, you may have forgotten that if you are running group forums you have a bbPress installation that synchronizes users with the WordPress MU installation. Disable registration in bbPress and you should be good to go.

    #49971
    Windhamdavid
    Participant

    the fbc_get_avatar() error is from the facebook connect… it’s been addressed somewhere else in the forums. ..it’s been fixed. The spam.. the user “LnddMiles” is not just on buddypress sites, so it’s a spambot that looks for open registrations.

    You should add a captcha or math problem to your registration page to divert these.

    3635122
    Inactive

    Hi everyone

    I’ve had WordPressMU/BuddyPress installed for several months now. Recently I upgraded to WordPressMU v2.8.2 and BuddyPress v1.0.3. I’ve always had registrations disabled and recently I installed the latest version of Askimet.

    Everything has been installed by-the-book and everything has worked perfectly until this morning when I awoke to see that someone had registered with the user name “LnddMiles” – despite registrations being disabled and having Askimet installed.

    A Google search quickly showed that this same user has registered on thousands of other BuddyPress sites.

    Additionally, I am now getting the following error each time I access my admin center…

    Warning: Missing argument 5 for fbc_get_avatar() in /home/azonez/public_html/wp-content/plugins/bp-fbconnect/includes/wp-facebookconnect/fbconnect.php on line 529

    What does this mean and what can I do about this?.

    Thanks for any help and have a great day!.

    – Steve

    peterverkooijen
    Participant

    Is the hook to use this?:

    user_register

    Runs when a user’s profile is first created. Action function argument: user ID.

    So something like this?:

    <?php
    /*
    Plugin Name: Real Name Synchro
    Plugin URI: http://
    Version: v0.001
    Author: peterverkooijen
    Description: A plugin to store firstname and lastname from the fullname field in Buddypress registration in WPMU usermeta tables, based on examples in the <a href="http://www.devlounge.net">Devlounge</a> series.
    */
    if (!class_exists("RealNameSynchro")) {
    class RealNameSynchro {
    function RealNameSynchro() { //constructor

    }
    function xprofile_sync_wp_profile() {
    global $bp, $wpdb;

    if ( (int)get_site_option( 'bp-disable-profile-sync' ) )
    return true;

    $fullname = xprofile_get_field_data( BP_XPROFILE_FULLNAME_FIELD_NAME, $bp->loggedin_user->id );
    $space = strpos( $fullname, ' ' );

    if ( false === $space ) {
    $firstname = $fullname;
    $lastname = '';
    } else {
    $firstname = substr( $fullname, 0, $space );
    $lastname = trim( substr( $fullname, $space, strlen($fullname) ) );
    }

    update_usermeta( $bp->loggedin_user->id, 'nickname', $fullname );
    update_usermeta( $bp->loggedin_user->id, 'first_name', $firstname );
    update_usermeta( $bp->loggedin_user->id, 'last_name', $lastname );

    $wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET display_name = %s WHERE ID = %d", $fullname, $bp->loggedin_user->id ) );
    $wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET user_url = %s WHERE ID = %d", bp_core_get_user_domain( $bp->loggedin_user->id ), $bp->loggedin_user->id ) );
    }
    add_action( 'xprofile_updated_profile', 'xprofile_sync_wp_profile' );

    }

    } //End Class RealNameSynchro

    if (class_exists("RealNameSynchro")) {
    $dl_pluginSeries = new RealNameSynchro();
    }
    //Actions and Filters
    if (isset($dl_pluginSeries)) {
    //Actions
    add_action('user_register', array(&$dl_pluginSeries, 'xprofile_sync_wp_profile'), 1);
    //Filters
    }

    ?>

    Testing it now…

    Edit: Activating this plugin produces a white screen. Not a good start… :-(

    Where did I go wrong?

    #5914
    fangonk
    Participant

    What file/template do I need to modify to remove the Avatar upload in the registration process? I don’t want to disable avatars, just disallow them at signup.

    #49704

    just noticed you commented on this thread:

    https://bbpress.org/forums/topic/howto-disable-registration

    Do I understand that it doesn’t prevent new users, it just prevents registering from the mysite/forums/registration.php process and still allows auto joining via the BP process?

    Sorry, I was away camping! Yes, that’s exactly what it does.

    peterverkooijen
    Participant

    The cleanest way to get separate firstname and lastname into the database seems to be to

    1. make a two or more part name in fullname on the registration form required

    2. consistently split the input from Buddypress’ fullname field and synchronize with usermeta using xprofile_sync_wp_profile()

    How would I do that? I assume this could be turned into a plugin?:

    function xprofile_sync_wp_profile() {
    global $bp, $wpdb;

    if ( (int)get_site_option( 'bp-disable-profile-sync' ) )
    return true;

    $fullname = xprofile_get_field_data( BP_XPROFILE_FULLNAME_FIELD_NAME, $bp->loggedin_user->id );
    $space = strpos( $fullname, ' ' );

    if ( false === $space ) {
    $firstname = $fullname;
    $lastname = '';
    } else {
    $firstname = substr( $fullname, 0, $space );
    $lastname = trim( substr( $fullname, $space, strlen($fullname) ) );
    }

    update_usermeta( $bp->loggedin_user->id, 'nickname', $fullname );
    update_usermeta( $bp->loggedin_user->id, 'first_name', $firstname );
    update_usermeta( $bp->loggedin_user->id, 'last_name', $lastname );

    $wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET display_name = %s WHERE ID = %d", $fullname, $bp->loggedin_user->id ) );
    $wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET user_url = %s WHERE ID = %d", bp_core_get_user_domain( $bp->loggedin_user->id ), $bp->loggedin_user->id ) );
    }
    add_action( 'xprofile_updated_profile', 'xprofile_sync_wp_profile' );

    Hook it to register_post? Does this code already check if there’s a two part name? I suspect that happens at ‘if ( false === $space)…etc.’, but I don’t see an error message + redirect or something like that.

    Or is it impossible to use this code during register_post because of this line:

    $bp->loggedin_user->id

    How can I modify the code to make it work during registration? Can I just remove that line? Or run this function the first time the new user logs in? Is there a hook on_activation or something like that?

    Has anyone used xprofile_sync_wp_profile()? Can anyone share code examples? This would solve a major structural problem in Buddypress imho.

    I need to come up with a solution, because integration with most mailing lists depends on having firstname and lastname stored somewhere.

    Alternatively I can use fullname for firstname and create a second custom xprofile field for lastname, but I suspect that solution could cause lots of problems further down the line.

Viewing 25 results - 576 through 600 (of 647 total)
Skip to toolbar