Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'registration'

Viewing 25 results - 7,326 through 7,350 (of 7,641 total)
  • Author
    Search Results
  • #48323
    peterverkooijen
    Participant

    This particular request is a WPMU issue and has nothing to do with BuddyPress. I’m afraid there is nothing we can do here to help you, but I strongly encourage you to search the WPMU forums for a similar thread and post a new thread if you can’t find anything related.

    It has everything to do with Buddypress. My question is about the relationship between Buddypress X-Profile tables and how WPMU handles first and last name. It’s about optional fields and how to integrate them into the registration process.

    I do understand this concept and your desire to achieve this type of setup. However, as I said in my previous post, WPMU is blog-centric, not user-centric. The username field is actually what WPMU stores in the “user_login” field of the wp_users table. Therefore, the way WPMU currently works, this datum is mandatory.

    This thread is NOT about the username issue. I use the wp-email-login that allows members to log in with their email address, but I understand the username is still mandatory. That’s why I would like to figure out a way to autogenerate it from first+last name.

    Which brings me back to first and last name. Let me restate the question:

    How does Buddypress handle first name + last name?

    Buddypress puts a default first x-profile field Name on the registration form; is it possible to replace that with separate first name + last name fields? Or should I use Name as First name and create a custom field for Last name?

    Or is there already a native solution for first name + last name in WPMU that Buddypress could tap into? (Nicola Greco: ‘… you could replace it with the wp built-in name & last name, or use xprofile fields fot that …”)

    WPMU is blog-centric, not user-centric.

    Isn’t the whole point of Buddypress to turn the WordPress base into something more user-centric?

    #48317
    peterverkooijen
    Participant

    So, my best advice is that you will have to do as Mike Pratt suggests and then code a custom function to extract the new firstname and lastname data from an xprofile table as you see fit, or just output that data in your theme files.

    I’m not too worried about displaying firstname and lastname once they are in the database, whereever they end up. My problem is how to customize the registration process to get them there, trying to find the shortest route, avoid redundancies.

    As far as registration, have you looked at Mike’s site (http://buglenotes.com/register) to see what he does? If that is what you want, you should PM him and get more advice.

    That is exactly what I want to avoid! Username is still at the top. I want to eliminate that impersonal username as much as possible. I want a simple, inviting, natural registration form like this:

    • First name
    • Last name
    • Email address
    • Blog name (=username, preferably auto-generated from first+last name)

    That should be enough! Additional optional profile fields would be on a next page or in the members account settings.

    Mike’s site has too many required fields. I assume Display Name is the default full name field in Buddypress and that he just added the others as custom fields.

    This form has username + display name + first name + last name; way too confusing and annoying to potential members. Totally unnecessary, but understandable since Buddypress/WPMU makes it almost impossible to do anything else.

    #48310
    Jeff Sayre
    Participant

    OK… So what does that mean practically?

    Haha! Well, good question.

    WPMU is not designed as a user-centric platform. It is blog-centric. BuddyPress puts the focus on the user.

    So, my best advice is that you will have to do as Mike Pratt suggests and then code a custom function to extract the new firstname and lastname data from an xprofile table as you see fit, or just output that data in your theme files.

    As far as registration, have you looked at Mike’s site (http://buglenotes.com/register) to see what he does? If that is what you want, you should PM him and get more advice.

    r-a-y
    Keymaster

    No, they would see the same screen on the registration page, but when the user hits “Next”, the second page will allow the user to customize their blog (name of blog, etc.).

    Dewey Hulsey
    Participant

    Would that make the default value for the blog creation the user’s username?

    #48296
    lokers
    Participant

    I totally understand you Peter, I am now trying to fix the fact that bp and wpmu have name and surname in two different places in mysql. I just don’t understand it why someone would like to keep it that way? Also, there is a function I found xprofile_sync_wp_profile() which is trying to sync both information, however it doesn’t do it after the registration confirmation and it’s called only after profile update. Currently I am working on big project based on wpmu and bp and many other plugins and opensource code and I must say half of my time I need to fix bugs cos they just don’t work together like they should. Anyway, I shouldn’t complain, at the end of a day it’s free…

    r-a-y
    Keymaster

    You could hide the “Create a Blog” section on the registration page, which would mean that blog creation will be checked by default.

    Add the following to your CSS file:

    #blog-or-username {display:none;}

    #48266
    Jeff Sayre
    Participant

    Great!

    As I often say, we aim to please and sometimes we actually manage to do just that.

    #48261
    gutster13
    Participant

    Got it thanks. I reinstalled WPMU, must have been a bad initial install. There wasn’t a Site Admin or other drop down, now they are there. Thanks!

    #48235
    Kieran
    Participant

    Yes, I had this problem. I figured it could be a plug-in conflict as, like connorg said, the registration worked fine at the beginning. For me it was the Google Analytics plugin – I deactivated it and all works fine again!

    #48228
    Jatinder Dhiman
    Participant

    Hi,

    I am using WordPress MU 2.7.1 . I have the same problem with user registration form. When a user sign up’s and enter his details in the form after the registration when the user login to the site then the only nick name is displayed and he has to fill all the information in the form again then the information is displayed in his profile.

    Jatinder

    #48224
    Jeff Sayre
    Participant

    You need to log into WPMU’s backend as site admin ( /wp-login.php), and then go to

    Site Admin > Options > Allow new registrations

    and set the options you want.

    Also I am unable to create an extended profile like shown in some of the demos. It only allows me change the “base” and avatar. I can’t put birthday, location, etc.

    To add additional profile fields, you need to navigate to the BuddyPress submenu grouping in WPMU’s backend. If BuddyPress is installed and activated, this submenu group is found at the very bottom of the menu column.

    So, go to

    BuddyPress > Profile Field Setup

    and set up the additional fields you want.

    #48215
    Ted Mann
    Participant

    If anyone is looking to hack the adminbar so that when users log in, they stay on the current blog they’re on, just edit the bp-core-adminbar.php file and change the reference to $bp->root_domain, under the “log in and sign up links” section, to $current_blog. Also, I took out the redirect as well. So, my login widget now looks like this:

    // **** "Log In" and "Sign Up" links (Visible when not logged in) ********
    function bp_adminbar_login_menu() {
    global $bp;

    if ( !is_user_logged_in() ) {
    echo '<li class="bp-login no-arrow"><a href="' . $current_blog . '/wp-login.php">' . __( 'Log In', 'buddypress' ) . '</a></li>';

    // Show "Sign Up" link if registrations are allowed
    if ( get_site_option( 'registration' ) != 'none' ) {
    echo '<li class="bp-signup no-arrow"><a href="' . bp_signup_page(false) . '">' . __( 'Sign Up', 'buddypress' ) . '</a></li>';
    }
    }
    }

    Jeff Sayre
    Participant

    @sandeepdude

    the confirmation email is not sent to newly registered users

    It seems that WPMU is doing its duties fine. PHP is responsible for taking care of the mail sending. The issue is most likely with your mail server. Check your mail server’s logs.

    If you continue to see this behavior, you should contact your host.

    found this on my error log…

    [27-Jun-2009 13:20:07] PHP Warning: array_merge() [function.array-merge]:

    Concerning the array_merge() error, that function has to do with registering new user blogs. This does not affect the initial registration of new users nor the sending of registration emails. There is a fix for this particular issue in this thread.

    Andy Peatling
    Keymaster

    Problem fixed in 1.0.2, closing.

    Burt Adsit
    Participant

    This only happens in 1.0.1 when you use the same computer. Normal users signing up will not see this issue.

    peterverkooijen
    Participant

    OK, upgraded to 1.0.2.

    Deleting the earlier test users to “free up” some email addresses I can use for testing. Why do deleted members remain in wp_signups? Is that necessary?

    Deleting those users manually in phpmyadmin…

    Then testing registering with an email address that I had used before:

    testuser

    peter@testaccount.net

    Peter Testuserman

    The expected error message:

    Sorry that email address is already used

    Reloading register page.

    mumbaitest

    peter@mumbaiaccount.com

    Raj Mumbaiman

    Congratulations, you are now registered!

    Your new username is: mumbaitest

    And this time the full name on the account is Raj Mumbaiman. So I guess 1.0.2 fixed the problem. :-)

    Leaving this long post here for reference and comments…

    Paul Wong-Gibbs
    Keymaster

    Yes.

    peterverkooijen
    Participant

    WordPress MU 2.7.1 + BuddyPress 1.0.1.

    Was this issue fixed in version 1.0.2? I will upgrade, test and report back, but any info on this from your side is appreciated.

    Clearing the browser cache should not be necessary. Regular users could try registering different accounts from the same computer as well. You can’t tell them to first clear the cache before trying to register.

    Jeff Sayre
    Participant

    Peter-

    Are you using BP v1.0.1 or 1.0.2? i believe there was an issue with cookies that could cause this problem in v1.0.1.

    Did you clear your browser’s cache in between registration attempts?

    #48181
    Jeff Sayre
    Participant

    Switch to the default BuddyPress themes and deactivate all plugins except BuddyPress. Try the registration process again. If it works, switch to the FaceBuddy theme. Try registration again. If it is still working, activate one of the plugins, etcetera.

    You must distill your BP environment down to the lowest common denominator–default themes, no plugins except BudddyPress activated–and see if everything works with that set up. If so, you then add one thing back at a time (first your custom theme, then one plugin at a time) until the problem occurs again.

    Let us know what you discover.

    Jeff Sayre
    Participant

    i have set to enable the new user registration and blog creation option in the wp-admin/wpmu-options.php page.

    What you need to do is log into WPMU’s backend as site admin ( /wp-login.php), and then go to:

    Site Admin > Options > Allow new registrations

    and set the options you want.

    #48009
    plrk
    Participant

    “Soon” is good enough for me.

    #48007
    Burt Adsit
    Participant

    Yep plrk that is the exact issue. ETA is ‘soon’. :)

    #48005
    plrk
    Participant

    I see. I was just about to add that the previous registrant’s name is only used if I register again using the same browser; when I register in another browser (without the associated cookies) I simply get an empty field.

    Is there any ETA on 1.0.2, then?

Viewing 25 results - 7,326 through 7,350 (of 7,641 total)
Skip to toolbar