Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'disable registration'

Viewing 25 results - 376 through 400 (of 463 total)
  • Author
    Search Results
  • #65442
    zageek
    Participant

    Thanks Andrea I didnt even realise that other users could add new users, because I was also wondering how they were spamming me even after I disabled registrations.

    I feel kind of sorry for the spammers, because if we all put our heads together they won’t have anymore sites left to spam. I still wonder why they are attacking buddypress, is it to drive users to other platforms? Enemys of Buddypress?

    So far I have built a list of domains, most of them are .info or .co.cc in otherwords free domains and of course some .com domains. They get clever and get a user to sign up with gmail every now and then to trick me. So i just ban the Gmail users and send them an email from my personal account asking them who they are if they look legitamate. Luckily for me I am in South Africa and its easy to spot non South African “culture” in terms of the types of names and usernames of members.

    I have also checked where the IP addresses come from and most are coming from the United States ( do they use proxy servers and could the be from elsewhere in the world) Some IP addresses are also from Sweden.

    Btw, I was also angry and blamed the devs for this problem but the more I devote time to looking at the more I am starting to realise that no matter what BP devs do the spammers always try new things and if the devs had to devote lots of time to fighting spam all the time they would never have a chance to improve buddypress and sort out bugs that come along. And if they didnt sort out the issues we would be even more upset.

    So I think the fight against spam is in our hands the users, it will also help us learn more about being better webmasters. Its also the least we could do to help give back something in exchange for a product that we are getting for free and that could quite easily be charged for. We need to stop expecting things for free and in our laps and learn to be greatful for what the developers of open source software are putting in and giving away for free.

    #65274
    zageek
    Participant

    I wonder where the spammers get the time to figure out ways to spam sites is there like a spam university or something lol

    On my site I even disabled registrations and I still two splogs appear after that, which is very confusing for me indeed.

    I can see one problem with sharing info on this forum about fighting spam, and that is that it will give the spammers the info they need to come up with counter attacks. I propose we start a spam eater group where we can share spam info behind the scenes, in fact I am going to start it now, not a perfect solution but still one that could work. What do you guys think?

    https://buddypress.org/groups/spam-eater

    Its a private group but anyone is welcome to join.

    #65253
    Famous
    Participant

    I had the same problem. Odd, my sign up link didn’t even show up??? But I did what windHamDavid said and I went here /wp-admin/wpmu-options.php

    Note: because I have MU installed maybe different for regular wordPress

    I disabled registrations saved and re-enabled, and it worked.

    Thanks windHamDavid

    Hugo Ashmore
    Participant

    I’m somewhat at a loss as to why people debate this issue or try and state it’s a WP issue as logically that doesn’t make sense?

    As jfigura posts this is an inherent problem, I have it on a production install and it must be hugely confusing for users, and yes the only approach so far has been to modify the text and remove the WP password from the confirmation emails.

    Further testing points to the initial blog registration as being possibly the issue:

    Clean install of WP MU 2.9.1 & BuddyPress 1.2 no significant further plugins activated.

    Test Condition 1:

    WP MU with BuddyPress disabled – admin options -> Allow New Registrations ->’Only user account can be created’

    Register new user

    Receive confirmation email of new registration along with Activation key

    Activate registration

    Receive second email with account username and pass

    All as expected!

    Test Condition 2:

    WP MU with Buddypress activated – admin options for registration still set as ‘User Account only’

    Register new user

    Receive confirmation and activation key

    Activate registration – screen message stating ‘you can now login with user name and password you set’

    No further emails sent!

    Test Condition 3:

    WP MU BuddyPress still activated – admin options -> Allow New Registrations -> ‘Enabled. Blogs and user accounts can be created.’

    Register new user as well as a blog!

    Receive confirmation and activation for account and new blog

    Activate registration – screen message ‘you can now login with password you set etc etc’

    Receive further email from WP! (copied below)

    Dear User,

    Your new *********.co.uk Blogs blog has been successfully set up at:

    http://eggs.********.co.uk/

    You can log in to the administrator account with the following information:

    Username: eggbert

    Password: 5f112917

    Login Here: http://eggs.**********.co.uk/wp-login.php

    We hope you enjoy your new blog.

    Thanks!

    –The Team @ ********.co.uk Blogs – Sent via Site Admin options email

    So having new accounts and new blogs enabled at initial registration triggers the sending of the ‘Welcome Email’ noted above.

    clearly this is confusing as it contains the WP generated password.

    Why is it that BP registration doesn’t disable / override the WP registration completely? To my mind this IS a BP issue, but I may very well be wrong on that score as I don’t profess to have a deep understanding of the core coding involved here.

    On a sidenote:

    Testing this and the slightly odd behavior of ‘Allow New Registrations’ where option for ‘only logged in users can take a blog’ actually seems to prevent all registrations. It occurred to me that on a social community ,and from our experience, blogs are not necessarily what users register for and that I would prefer the option to have a blog be only available for registered users from their account options. what actually happens is that registration is disabled completely! Not the effect I desired. I realise this IS a WP MU issue but is simply daft behavior and that set of options needs to be re-worded to be a lot clearer as to what it really does.

    It would be great to be able to restrict blog signup to users already with account set up and remove, completely, the option to take a blog on initial signup, I have done this by simply scripting out the option / section for registering a new blog in BP register page but feel it’s not the best approach?

    #64389
    dailynewarker
    Participant

    @emilywebber, thanks for the reply! So, I looked in my WordPress Dashboard Settings (Dashboard > Settings > General) and I don’t have a setting for allowing user registration. I think it was moved in WordPress Multi-User to this menu: Site Admin > Options, where I have these choices:

    * Disabled

    * Enabled. Blogs and user accounts can be created.

    * Only user account can be created.

    * Only logged in users can create new blogs.

    Selecting “Enabled” or “user account can be created” doesn’t fix the issue.

    @Sunset Cowboy, no that didn’t help. The BuddyPress 1.2 theme (appropriately) doesn’t show the link to users who are logged in. Logging out and clicking on the “Create New Account” link still just redirects to the homepage.

    Is there something else I’m missing? Perhaps some other setting? I’m thinking of shutting off BuddyPress and trying to create a new account in just WPMU.

    Thanks,

    K

    Windhamdavid
    Participant

    this doesn’t sound good. I would disable all registrations immediately, clean out all of the users whom have been added, delete all of your wp and bp files and reinstall to make sure that you don’t have any modified files. And you might examine the db tables closely to see if they need may need repair.

    https://trac.buddypress.org/browser/trunk/bp-core/bp-core-activation.php#L79

    There are two ways for this email to still get sent:

    1.) Your active theme does not have either /register.php or /registration/register.php in it.

    2.) You are an admin that has just added a user to your site.

    If either of those things are true, the email will get sent out.


    If you are hard pressed to make this issue go away, try adding this to your functions.php or bp-custom.php.

    /* Unhook BuddyPress wpmu email blocker */
    remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

    function block_wpmu_email() {
    if ( is_admin() && $_GET['e'] )
    return true;

    return false;
    }
    /* Rehook custom function */
    add_filter( 'wpmu_welcome_user_notification', 'block_wpmu_email' );

    The above routine doesn’t help us test this issue any, but it does stop the email from going through unless you add a user yourself.

    #63486
    Andy Peatling
    Keymaster

    This is a problem with WPMU and spammers simply wanting to register spam blogs. I’ve not really seen the problem on standard WordPress, and with blog registration disabled.

    peterverkooijen
    Participant

    @snark, I simply removed the function bp_core_disable_welcome_email() from bp_core_activation.php. But then the password in the welcome email is wrong, as discussed here. Haven’t been able to come up with an explanation/solution for that… :-(

    snark
    Participant

    Still not working. I did find the filter itself in the file /plugins/buddypress/bp-core/bp-core-activation.php:

    add_filter( ‘wpmu_welcome_user_notification’, ‘bp_core_disable_welcome_email’ );

    I suppose I could just delete that line to remove the filter, but then every time BP is updated it’ll probably get overwritten and I’ll forget all about it. Not sure why your filter hook didn’t work. Any ideas?

    Thanks a million for your help — I really appreciate it.

    r-a-y
    Keymaster

    Re #1:

    Sorry I forget that you need to hook the filter to an action.

    Try this:

    function snark_reenable_welcome_email() {
    remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );
    }
    add_action('init', 'snark_reenable_welcome_email');

    The file is /wp-content/plugins/bp-custom.php

    r-a-y
    Keymaster

    1) By default, an email isn’t sent to the user because the user password is sent via plain text (not a good thing security-wise).

    You can re-enable this welcome email by adding the following code to /wp-content/plugins/bp-custom.php (create this file if you don’t have one – be sure to add PHP open and closing tags as well):

    remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

    2) Please post the avatar bug on BuddyPress Trac:

    https://trac.buddypress.org/newticket

    Login with the same credentials you use on buddypress.org.

    3) WP-reCAPTCHA is not compatible with BuddyPress.

    BuddyPress uses a different registration mechanism.

    You might want to try one of these solutions listed here:

    http://www.bp-tricks.com/tips_and_tricks/stopping-the-sploggers/

    #62162
    r-a-y
    Keymaster

    Did you disable new user registration?

    #62045
    symm2112
    Participant

    Any suggestions on this anyone? I’m still debating splitting my main news site from the community site but just wondering which one makes more sense and is easier to integrate with gigya. Should I let people register on my community site and disable registration on my main blog and just let a plugin add the users to the main blog or should i use gigya wp plugin to let people hit wp-login? I think that’s more my concern is which one is more secure. My other question is since the gigya plugin lets you create users when logging in, does that actually completely bypass the registration page from bp with all its fields?

    Thanks for the help anyone.

    #61895
    Mike Pratt
    Participant

    I wholeheartedly agre with @andy. It’s an age old debate between making it as simple as possible to register and become a member and requiring some unique information that not only serves your purpose well but adds an extra layer to the process that fights spam.

    We have been running our prod site since BP was in alpha (Nov ’08 – crazy, I know) but have had only 2 spam registrations. Both were from Russia and both seemed pointless. But we banned the domain in the WP backend and have had none since. We have not even changed our signup slug.

    That said, we require 5 fields on registration, 3 are drop downs and we don’t allow blog registration (we’re building a community not a blog network)

    On a side note: We ran reCaptcha flawlessly for 6 months. We disabled it as an experiment to see if we could avoid that extra step (plus reCaptcha words are damn hard to read) and have not had spam since. fingers crossed.

    #61720
    peterverkooijen
    Participant

    Which registration emails do you mean? The WPMU welcome email is disabled in BP; see function bp_core_disable_welcome_email() in bp_core_activation.php. It’s a feature…

    #61407
    Diesel Laws
    Participant

    @mercime – You my friend are the saviour of the blogosphere! Thank you so much!

    Changed to 2 blogs allowed and it works – however….

    Now it brings up the other issue (not life threatening), when they subscribe for a new blog it removes their role on the main blog. Which now means they can still create another blog – so essentially they can have two blogs if they want – I have searched and it seems like other users have this issue, please post an issue if you find one, but for now this problem is considered fixed! Thanks so much mercime!

    #61394
    @mercime
    Participant

    “limit blogs plugin is set to 1”

    That’s where it goes awry. Remember that your members already have 1 blog – even as a subscriber to the blog where your BuddyPress is installed, that is counted. So increase Limit Blogs to 2 so that in addition to main blog as subscriber or whatever role you made them to be, they can create one new blog for themselves.

    #61366
    Diesel Laws
    Participant

    1. WordPress MU 2.8.6

    2. Directory

    3. Root

    4. Yes, 2.8.4 I believe

    5. Yes

    6. 1.1.3

    7. 1.1.2

    8. Yes, a lot, however they were installed previously

    9. Customised

    10. Slightly in regards to avatars not working

    11. no

    12. bbPress built-in

    13. Few errors but nothing that I believe relates

    14. Hostmonster

    #61188
    Paul Wong-Gibbs
    Keymaster
    #61119
    Psyber
    Participant

    I would like to bring up this topic again, as it is very crucial to the development of my website and I want to see if there have been any updates in the 10 months since this was posted. Right now I have blogs disabled, the main purpose of the site is to have different types of users interact on the site, and be able to search the site based the different details in their profiles..

    Multiple profile types:

    For my website I would like to have 4 profile types, all profiles have the same permissions, they just have different details listed in their public profile. These details can be defined during the registration process.

    2-Stage registraion:

    When the user decides to register, they are prompted with a page where they will select their profile type. Upon selecting their profile type, they will be taken to a second part of the registration process where they will fill in their profile information, each type of profile having a different form to fill in.

    This should go along the lines of what Dev posted, minus the permissions. This is a huge hurdle for me to overcome, and if I can there will be one more addition to the Buddypress Community. :-) Any help or direction is appreciated.

    peterverkooijen
    Participant

    There’s not supposed to be any generated password upon activation in 1.1.3. No passwords are ever sent by email in 1.1.3. You may have missed something in the upgrade.

    We had noticed that the welcome email includes a wrong password, perhaps because of different encryption between WP and BP. The password that was entered upon registration still works.

    Note that in 1.1.3 the WPMU is disabled by default. To bring it back you have to remove a function from the core files.

    #60617

    In reply to: Moderate members

    Tom
    Participant

    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).

    #59997
    peterverkooijen
    Participant

    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…

    #58786
    Jeff Sayre
    Participant

    @Harry

    Yes, my Privacy Component works just as I described. It is an advanced beta available for testing. See this thread for more details: https://buddypress.org/forums/topic/buddypress-privacy-component-an-update/page/3#post-30574

    @David

    I wouldn’t give users the option to set it to friends only. Or at least… I would like the site admin to have the ability to disable that option.

    In my Privacy Component, the site admin can choose to disable this feature.

    But, to get back on topic, I agree that the best solution is the one that requires the brunt of the filtering to be accomplished through invisible, behind-the-scenes techniques. Requiring users to prove that they are members and not bots should not be the first line of defense. I think it is okay, even necessary for registration purposes. But that is a one time occurrence. After that, the system should do more of the policing.

    Concerning your second link above, perhaps we could create a new CAPTCHA that could harness the collective intelligence of site members to solve the Unified Field theory.

Viewing 25 results - 376 through 400 (of 463 total)
Skip to toolbar