Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'registration'

Viewing 25 results - 2,551 through 2,575 (of 7,642 total)
  • Author
    Search Results
  • #207114
    1a-spielwiese
    Participant

    Yes, there should be a way, but I was not able to follow the instructions / to realise that way.

    The basic idea is:

    • Create two (or more) new WordPress user roles, e.g.: Users-UK and Users-USA.
    • Then you can assign one xProfile-field, ‘In which [federal] state do you live?’, exclusively to your users with the user role Users-USA; and another x-Profile, ‘In which county do you live?’, to your users with the user role Users-UK.

    The instructions for that solution you find there:

    https://buddypress.org/support/topic/resolved-different-profile-types-and-different-user-roles/

    (The user roles there are ‘bands’ and ‘fans’).

    And my report about my attempt to apply that instructions you find there:

    https://buddypress.org/support/topic/different-profile-types-and-different-user-roles-part-ii/

    My user roles are (sport) ‘teams’ and ‘fans’.

    But unfortunately, I was not able to hinder, that ‘fans’ get displayed the questions (xProfile-fields) for ‘teams’ was well; and the ‘teams’ the questions for ‘fans’…

    Further problem:

    Even if there is a solution regarding later profile edits – even complicate seems to be, to make already the registration page “input senstive”, because during registration the new user isn’t yet registered (i.e.: has no user role yet).

    Cfr. there:

    http://forum.wpde.org/buddypress/133961-registrierungsseite-umgestalten-anleitung-und-fragen.html (section 4. – unfortunately in German).

    #206284
    1a-spielwiese
    Participant

    For me also not:

    I tried it with

    Mitglieder-Kategorie (Team oder Fan?)

    instead of

    'name of your field'

    as well as with

    'Mitglieder-Kategorie (Team oder Fan?)'

    But my users can still change the values for this field. –

    I tried as well – already before and now again – this code of @noizeburger:

    //hide the user role select field in edit-screen to prevent changes after registration
    add_filter("xprofile_group_fields","bpdev_filter_profile_fields_by_usertype",10,2);
    function bpdev_filter_profile_fields_by_usertype($fields,$group_id){
    //only disable these fields on edit page
    if(!bp_is_profile_edit())
    return $fields;
    //please change it with the name of fields you don't want to allow editing
    $field_to_remove=array("User Role");
    $count=count($fields);
    $flds=array();
    for($i=0;$i<$count;$i++){
    if(in_array($fields[$i]->name,$field_to_remove))
    unset($fields[$i]);
    else
    $flds[]=$fields[$i];//doh, I did not remember a way to reset the index, so creating a new array
    }
    return $flds;
    }

    It works neither with

    "Mitglieder-Kategorie (Team oder Fan?)"

    nor with

    Mitglieder-Kategorie (Team oder Fan?)

    nor with:

    'Mitglieder-Kategorie (Team oder Fan?)'

    #205551
    Ruby Sinreich
    Participant

    I ma having the same problem. It started as soon as my new site was live (I just migrated servers at the same time as installing BuddyPress). I installed this honeypot https://wordpress.org/plugins/registration-honeypot/, and it helped a little, but I won’t be able to deal with this once I have real members registering since I can’t always tell who is real or fake.

    There’s got to be a better way. Or at least a better admin view of new users so I can screem them with more profile data.

    #205182
    r-a-y
    Keymaster

    BuddyPress does not have shortcodes.

    – Remove the shortcode on the “Register” page.
    – Also ensure that under “Settings > BuddyPress > Pages” that your register page is properly attached.
    – If you’re using single-site, under “Settings > General”, make sure registration is enabled.

    #205160
    Halo Diehard
    Participant

    Kk, sorry it took so long to get back to this; I had to walk away from it all for a bit as my whole setup is taking more of my time than I am able to produce any content, and I’m ready to throw in the towel.

    I just took a peek in my database and it looks like the plugin just takes the person’s account name from whatever account they log into and uses that for everything, the login, nicename and display/nickname, so no way of knowing which one it pulls the @mention from.

    I’m assuming in a normal registration it takes it from the person’s first and last name, though? This probably works on a lot of “business”-types sites, where people use their birth-names anyway, but the vast majority of forums I’ve visted show that people prefer to use quirky, expressive names that reflect their personalities. For this reason, I think BuddyPress would better serve a lot of forums with the @mentions if there were at least an option to use the nicename instead of the username.

    I understand it gets really complicated with people being able to change their nicename, but on most forums people don’t get to do that, only Admins can do that for them, because it confuses the other membership; they don’t know who’s “talking”.

    So for a ton of people who are used to phpbb3-type forums, it would be great to turn off the ability to change nicenames and have nicenames be @mentions. Or even have nicenames be @mentions, and if you change your nicename, your @mention just has to stay the same, because it’s just too complicated to get the coding to do that, but still, nicename over “real name”, because when you put your real name in a forum you don’t expect it to be used as your forum name, you just don’t. And hand-holding or no, it *will* discourage people from using a forum.

    There’s mah feedbacks, lemmie know if there’s anymore database peeking you’d like me to do, and thanks for trying to help 🙂

    #204299
    ecrip
    Participant

    Nor is mine
    WordPress 4.0 running Cosmic Buddy theme
    BuddyPress 2.1
    bbPress Version 2.5.4
    http://lifeplusstyle.com/site/

    Registration, signup, Activate don’t work. Takes me to a blank page http://lifeplusstyle.com/site/register/

    Neither does the vast majority of the drop-downs in the upper right corner; also takes me to a blank pages.

    I have tried testing in several themes including Twenty-Twelve and Twenty-Fourteen. The same issues are present using these themes too.

    ~Ecrip

    1a-spielwiese
    Participant

    Regarding the note at the end: You can ignore it. (I have decided to remove the blog-details-section from my registration page.
    When a new user register, then I [as the superadmin] now create a blog for him [or her] manually – and therefore I can choose for the subdomain-URL the same name as the user choose, for his/her user name. And everything is fine – insofar.)

    However, my link issue persits:

    Let’s take for example my activity-page: Everywhere, where there currently for the user name “Fans Eins” is linked to http://1a-spielwiese.de/teams/fan1/ I want to link instead to http://fan1.1a-spielwiese.de – and the same regarding my other users and other places, where they are mentioned.

    How can I do this?

    #203941
    Hugo Ashmore
    Participant

    and your registration form does show but not on an expected page but on a members page of some description, so tread carefully with these custom aspects that they work as expected.

    1a-spielwiese
    Participant

    @hnla / https://buddypress.org/support/topic/different-profile-types-and-different-user-roles-part-ii/#post-201146:

    By chance I found the solution regarding the ‘default user role’-issue:

    Within the wp-admin-folder there is not only an options-general.php, rather as well an options.php.

    Within the comment at the beginning of this file is written: ‘If accessed directly in a browser this page shows a list of all saved options along with editable fields for their values.’

    Therefore I adressed this file with 1a-spielwiese/wp-admin/options.php – and there I found the opportunity to change the default user role:

    http://1a-spielwiese.de/wp-content/uploads/2014/10/wp-admin-options-php.jpg

    After changing it into ‘fan’ (note: it’s not possible to leave the line blank!), on the page options-general.php?page=wp-roles-at-registration it is now possible to select only the roles ‘fan’ and ‘team’:

    http://1a-spielwiese.de/wp-content/uploads/2014/10/rar-settings_without_subscriber.jpg

    And after saving it, ‘subscriber’ disappears from the registration page as well:

    http://1a-spielwiese.de/wp-content/uploads/2014/10/register-page_without_subscriber.jpg

    —-

    However, these other above mentioned problems:

    A. How can I make profile fields, which are asigned only to one member category / user role, ‘required’? Cfr. above.

    C. What is the purpose of the penultimate step of the instructions of @noizeburger? – What have I to check for seeing, whether it works or not?

    and

    D. Why does the last step of the instructions of @noizeburger do not work for me? How can I make the member category / user role unchangeable for my members?


    @amalsh
    / @jonaro / @lebearuk / @kamillamonkey and @jeffacubed:

    Do you have any idea regarding this issues?

    – cfr. regarding D.: http://kampfsportlerinnenneuwied.1a-spielwiese.de/wp-content/uploads/sites/2/2014/09/user_role_still_changeble.jpg

    are still unresolved.

    #203649
    1a-spielwiese
    Participant

    Let’s come back to the beginning:

    1st: Revolved.

    2nd: Resolved.

    a) I decided finally for having only one border color. If you want to have different border colors, you have to make different definitions for #buddypress .standard-form #basic-details-section and #buddypress .standard-form #profile-details-section

    and, if you use them, for: #user-role-section and #buddypress .standard-form #blog-details-section.

    b) I have abstained from having the text lines ‘WordPress’ respec. ‘BuddyPress’ at the borders and from making the bottom-borders more strong.

    3rd: Revoled.

    4th: Revolved.

    5th:

    I guess, it would be most comfortable, to have within the Dashboard check boxes for deciding, whether a certain field group or field should be displayed on registration page or not.

    Not revolved.

    6th to 8th:

    a) Finally I have abstained from having the blog-details-section on the registration page.

    b) I didn’t collect information about changing this section.

    —-

    So, the main issues are revolved. I would have no objections against marking the entire thread as ‘[Resolved’].

    #203620
    r-a-y
    Keymaster

    As hnla mentioned, if you’re using theme compatibiliy, /wp-content/themes/our-theme/registration/register.php is the wrong file to use for your overrides. This file is for older bp-default themes. BP 2.1 made the change so only bp-default themes can use this older template naming convention.

    If you only want to modify the contents of the registration template part and not the entire page template, you should copy:
    /wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/single/register.php

    to:
    /wp-content/themes/our-theme/buddypress/members/single/register.php.

    Then, you should compare your older registration mods and copy them to this file.

    If you want to change the entire registration page layout (header, footer, etc), check out the Template Hierarchy codex article for more info:

    Template Hierarchy

    #203616
    1a-spielwiese
    Participant

    PS. @ section 1.a):

    I have just seen:

    template_notices can’t used; it inserts the text at issue as well on the activity and group page.

    Therefore I did the following:

    a) I changed template_notices into rar_at_beginning.

    b) I inserted into register.php behind the lines

    		<?php if ( 'request-details' == bp_get_current_signup_step() ) : ?>
    
    			<?php do_action( 'template_notices' ); ?>

    that line:

    <?php do_action( 'rar_at_beginning' ); ?>

    —-

    Besides (whether with template_notices or with rar_at_beginning):

    Behind the line, to which the wp-role-at-registration.php refers, (for esthetical reasons regarding my borders) a <br> is needed.

    #203615
    1a-spielwiese
    Participant

    I found two more solutions:

    1st:

    a) The place of the field for determining the user role is depending on the plugins/wp-roles-at-registration/wp-roles-at-registration.php

    The relevant line of the original version of that file is:

    add_action('bp_after_signup_profile_fields', array($wp_rar_plugin, 'bp_choose_roles_registration_form'));

    I substituted there bp_after_signup_profile_fields by template_notices and now the field at issue is displayed not the end, rather at the beginning of my registration page:

    http://1a-spielwiese.de/registrieren/

    b)

    For creating the headline and the introductory text I made a second change within the same file. I changed the following section. The first and the last line of the quote is the original code, and the lines inbetween I inserted:

        <div class="register-section" id="user-role-section">
        
        <h4-a><?php _e( 'Benutzer/in/rolle', 'buddypress' ); ?></h4-a>
    
        <p><small><em>Entscheide Dich bitte als allererstes f&uuml;r eine der Benutzer/in/rollen "Team" oder "Fan" (bitte w&auml;hle nicht die Rolle "Subscriber"; diese Angabe soll noch gel&ouml;scht werden). In Abh&auml;ngigkeit von Deiner Antwort wirst Du nach Abschluss der Registrierung und wenn Du Dich das erste Mal bei 1a-Spielwiese einloggst und Dir Dein Profil ansiehst, die M&ouml;glichkeit haben, einige erg&auml;nzende rollenspezifische Profilangaben zu machen.</em></small></p>
    
        <label for="wp_rar_user_role"><?php echo $this->wp_rar_role_label; ?></label>

    2nd:

    As well I was able to integrate now not only the ‘base’-profile field group. For that it is neccessary to copy a long section of the buddypress register.php. This sections begins with:

    			<?php /***** Extra Profile Details ******/ ?>
    
    			<?php if ( bp_is_active( 'xprofile' ) ) : ?>
    
    				<?php do_action( 'bp_before_signup_profile_fields' ); ?>
    
    				<div class="register-section" id="profile-details-section">
    
    					<h4><?php _e( 'Profile Details', 'buddypress' ); ?></h4>
    
    					<?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?>
    
    					<?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

    And it ends with:

    					<input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_field_ids(); ?>" />
    
    					<?php endwhile; endif; endif; ?>
    
    					<?php do_action( 'bp_signup_profile_fields' ); ?>
    
    				</div><!-- #profile-details-section -->
    
    			<?php endif; ?>

    The only two things, which are obligatory then:

    • You have to insert the entire copied section behind the last line of the original section.
    • And you have to change 'profile_group_id' => 1, into 'profile_group_id' => 2, (for adressing your second profile field group – and so on regarding the further profile field groups).

    Besides I changed the <h4>-headline and inserted introductory text behind that headline. Therefore my code there is:

    					<h4-a><?php _e( 'Profile Details - Teil II: Kontaktendaten', 'buddypress' ); ?></h4-a>
    
    				<p><small><em>Beachte bitte, dass Du in zu den Profilfeldern in diesem Abschnitt selbst entscheiden kannst, wem Deine Angaben, die machst, angezeigt werden sollen.</small></em></p>
    #203597
    Hugo Ashmore
    Participant

    Initial thoughts is if you are still in development why are you choosing to use the bp-default theme approach rather than using the newer(since 1.7) theme compat approach and to which you allude in trying /our-theme/buddypress/ /our-theme/community/

    If that later approach were to work for you you need to understand that registration does not have it’s own folder/dir but the reg template lives in /members/ have a look at /bp-legacy/buddypress/ to see the directory structure which must be mirrored in the theme also templates under theme compat are not full page templates i.e complete with header and footer calls as they get called and injected into a parent template – generally page.php unless the hierarchy invoked and another named template is use.

    Although this doesn’t address your immediate issue, unless you are wanting the old bp-default visual styling I would suffer the change to theme compat templating now before you go further?

    #202801
    1a-spielwiese
    Participant

    @ Section 3rd, a)

    I deleted now that code

        #user-role-section {
          width: 48%;
          float: left;
          clear: left;
        }
        #wp_rar_user_role {
          width: 50%;
        }

    directly within the original wp-roles-at-registration.php (within the /wp-content/plugins/wp-roles-at-registration-folder) – and now the width is as I want.

    How can I determine the same effect within ‘Simple Costum CSS’-plugin respec. inside by child-theme?

    #202786
    bitpath
    Participant

    Hello, if they are getting in some other way, will you please let me know?
    I’m not accusing Buddypress, it’s great, but could someone please confirm for me that it doesn’t open up an alternative registration method somewhere?
    It could be as simple as just increased users and an incompatibility with my captcha counting.
    Thank you very much! 🙂

    #202778
    1a-spielwiese
    Participant

    I decided to test theses instructions – and in general they work.

    My registration page has now a new design:

    http://1a-spielwiese.de/registrieren/

    This result I got using two means:

    1st:

    I tested with ‘Simple Custom CSS’-Plugin that code:

    #buddypress .standard-form #basic-details-section, #buddypress .standard-form #blog-details-section, #buddypress .standard-form #profile-details-section {
        border: 2px solid #8b008b;
    	float: none;
      	clear: left;
      	width: 100%;
      	padding: 10px;
      	margin-bottom: 1em;
    }
    
    #user-role-section {
      	border: 2px solid #8b008b;
        float: none;
        width: 100%;
      	padding: 10px;
    }
    
    #wp_rar_user_role {
          width: 100%;
        }
    
    h4-a {
    	color: #8b008b;
    	font-size: 11px;
    	font-size: 1.1rem;
      	font-weight: bold;
    	letter-spacing: 0.05em;
    	line-height: 1.9091;
    	text-transform: uppercase;
    }
    
    .wp-editor-container {
        border: 1px solid #DCDCDC;
    }

    Finally I will insert it into my child-theme.

    2nd:

    The relecant section of the register.php with in my reddle-child/buddypress/members-folder is now:

    		<?php if ( 'request-details' == bp_get_current_signup_step() ) : ?>
    
    			<?php do_action( 'template_notices' ); ?>
    
    			<p><?php _e( 'Mitglied bei 1a-Spielwiese zu werden, ist sehr einfach - und kostenlos. F&uuml;lle einfach die Felder unten aus und wir erstellen f&uuml;r Dich umgehend ein Benutzer/in/konto und in K&uuml;rze auch einen eigenen Blog (Webseite).', 'buddypress' ); ?></p>
    
    			<?php do_action( 'bp_before_account_details_fields' ); ?>
    
    			<div class="register-section" id="basic-details-section">
    
    				<?php /***** Basic Account Details ******/ ?>
    
    				<h4-a><?php _e( 'Account Details', 'buddypress' ); ?></h4-a>
    
    				<p><small><em>Diese Daten werden f&uuml;r Deine Registrierung als neues Mitglied und die Einrichtung Deines eigenen Blogs (Webseite) ben&ouml;tigt.</em></small></p>
    
    				<label for="signup_username"><?php _e( 'Username', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
    				<?php do_action( 'bp_signup_username_errors' ); ?>
    				<input type="text" name="signup_username" id="signup_username" value="<?php bp_signup_username_value(); ?>" />
    
    				<label for="signup_email"><?php _e( 'Email Address', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
    				<?php do_action( 'bp_signup_email_errors' ); ?>
    				<input type="text" name="signup_email" id="signup_email" value="<?php bp_signup_email_value(); ?>" />
    
    				<label for="signup_password"><?php _e( 'Choose a Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
    				<?php do_action( 'bp_signup_password_errors' ); ?>
    				<input type="password" name="signup_password" id="signup_password" value="" class="password-entry" />
    				<div id="pass-strength-result"></div>
    
    				<label for="signup_password_confirm"><?php _e( 'Confirm Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
    				<?php do_action( 'bp_signup_password_confirm_errors' ); ?>
    				<input type="password" name="signup_password_confirm" id="signup_password_confirm" value="" class="password-entry-confirm" />
    
    				<?php do_action( 'bp_account_details_fields' ); ?>
    
    			</div><!-- #basic-details-section -->
    
    			<?php do_action( 'bp_after_account_details_fields' ); ?>
    
    			<?php /***** Extra Profile Details ******/ ?>
    
    			<?php if ( bp_is_active( 'xprofile' ) ) : ?>
    
    				<?php do_action( 'bp_before_signup_profile_fields' ); ?>
    
    				<div class="register-section" id="profile-details-section">
    
    					<h4-a><?php _e( 'Profile Details', 'buddypress' ); ?></h4-a>
    
    				<p><small><em>Diese Daten werden k&uuml;nftig in Deinem Profil angezeigt. Einige Angaben sind verpflichtend, um aussagekr&auml;ftige Profile zu erhalten; bei anderen Formularfeldern ist es Dir selbst &uuml;berlassen, ob Du Angaben machst oder nicht.</small></em></p>
    
    					<?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?>
    
    					<?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>
    
    					<?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>
    
    						<div<?php bp_field_css_class( 'editfield' ); ?>>
    
    							<?php
    							$field_type = bp_xprofile_create_field_type( bp_get_the_profile_field_type() );
    							$field_type->edit_field_html();
    
    							do_action( 'bp_custom_profile_edit_fields_pre_visibility' );
    
    							if ( bp_current_user_can( 'bp_xprofile_change_field_visibility' ) ) : ?>
    								<p class="field-visibility-settings-toggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>">
    									<?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?> <a href="#" class="visibility-toggle-link"><?php _ex( 'Change', 'Change profile field visibility level', 'buddypress' ); ?></a>
    								</p>
    
    								<div class="field-visibility-settings" id="field-visibility-settings-<?php bp_the_profile_field_id() ?>">
    									<fieldset>
    										<legend><?php _e( 'Who can see this field?', 'buddypress' ) ?></legend>
    
    										<?php bp_profile_visibility_radio_buttons() ?>
    
    									</fieldset>
    									<a class="field-visibility-settings-close" href="#"><?php _e( 'Close', 'buddypress' ) ?></a>
    
    								</div>
    							<?php else : ?>
    								<p class="field-visibility-settings-notoggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>">
    									<?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?>
    								</p>
    							<?php endif ?>
    
    							<?php do_action( 'bp_custom_profile_edit_fields' ); ?>
    
    							<p class="description"><?php bp_the_profile_field_description(); ?></p>
    
    						</div>
    
    					<?php endwhile; ?>
    
    					<input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_field_ids(); ?>" />
    
    					<?php endwhile; endif; endif; ?>
    
    					<?php do_action( 'bp_signup_profile_fields' ); ?>
    
    				</div><!-- #profile-details-section -->
    
    				<?php do_action( 'bp_after_signup_profile_fields' ); ?>
    
    			<?php endif; ?>
    
    			<?php if ( bp_get_blog_signup_allowed() ) : ?>
    
    				<?php do_action( 'bp_before_blog_details_fields' ); ?>
    
    				<?php /***** Blog Creation Details ******/ ?>

    3nd:

    Nevertheless I have two questions regarding the design:

    a) Why the 100%-width for #wp_rar_user_role is ignored?

    b) How can I place the third section (‘Mitglieder-Kategorie’) above the other two sections (or between the other two sections)?

    4th:

    I recognised as well: Deleting there:

    <?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

    'profile_group_id' => 1, results in getting not only displaying the ‘base group’ of the xProfile fields, rather all fields of all field groups. 🙂

    Questions:

    a) How can I get the names (titels) of the different xProfile field groups displayed as well?

    b) How can I ensure, that only new members, which choose the user role ‘team’, get displayed the profile fields for teams and new members, which choose the user role ‘fan’, get displayed the profile fields for fans?

    #202681
    missnishar
    Participant

    yes,it absoulty possible with wordpress,Even for security you can also include login process with registration.

    #202529
    bp-help
    Participant

    @kris35
    You can use BuddyPress registration for now but I am not sure about once you decided to start charging for memberships how it would effect the retroactive members that had used the BuddyPress registration. It would probably just effect the users after you used a plugin for charging for memberships and not the retroactive members. I believe the S2 Member plugin handles all the registration once installed and configured.

    #202522
    Kris35
    Participant

    Hi @bp-help,

    Yes I have, but I am so busy with other stuff at the moment I just wanted to know if I can stick to the buddypress reg for now? I mean, I have no idea if I did that and gained say 100 members and decided to start charging – how difficult would it be? Could I just export (or whatever) my members out and switch over to a payment option like s2member? And then in the future I can start to research payment registration options. I dont even know if I can add a payment (Paypal tab) to the default Buddypress sign up page? I guess I can right?

    #201158
    1a-spielwiese
    Participant

    @ D.:

    I guess, the mistake was, that I – after creating the new user roles ‘Team’ and ‘Fan’ – forgot to asign my already existing members to that categories. But, however, when I try it now, then I can’t:

    http://1a-spielwiese.de/wp-content/uploads/2014/09/changing_user_role.jpg

    However, as alreday mentioned: On the registration page the new user roles are displayed:

    http://1a-spielwiese.de/wp-content/uploads/2014/09/Reg_Form_with_User_Roles.jpg

    #201151
    1a-spielwiese
    Participant

    Follow-up:

    7th:

    Capability Manager Enhanced to define custom user roles, if you’re not satisfied with the default wordpress roles (subscriber, contributor,…).
    The first step is to create your user roles

    https://buddypress.org/support/topic/resolved-different-profile-types-and-different-user-roles/

    As ready implied there: I did this – and it works so far.

    8th:

    Create a xprofile field (selectbox) with the title “User Role” and name the options “Band Role” and “Fan Role” – in my case. You can call them whatever you want. Place this field in the “base” profile group, otherwise it won’t be shown during registration. Also make the field “required”. In my case the user can’t decide, if the visibility of the field can be changed.

    I did it already, when I installed and activated ‘BP Profile Search’-plugin – and it works.

    However, to choosed a dropdown menu and the categories ‘team’ and ‘fan’.

    9th:

    I modified:

    ?php
    function custom_bp_core_signup_user($user_id) {
        $user_role = strtolower(xprofile_get_field_data('User Role', $user_id));
        switch($user_role) {
            case "Band Role":
                $new_role = 'band';
                break;
            case "Fan Role":
                $new_role = 'fan';
                break;
        }
        wp_update_user(array(
            'ID' => $user_id,
            'role' => $new_role
        ));
    }
    add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

    into:

    function custom_bp_core_signup_user($user_id) {
        $user_role = strtolower(xprofile_get_field_data('Mitglieder-Kategorie (Team oder Fan?)', $user_id));
        switch($user_role) {
            case "Team":
                $new_role = team';
                break;
            case "Fan":
                $new_role = 'fan';
                break;
        }
        wp_update_user(array(
            'ID' => $user_id,
            'role' => $new_role
        ));
    }
    add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

    (I omitted <?php, because I created not a new bp-costum.php, rather inserted the code into my yet existing bp-costum.php. I inserted the modified code above the line ?>.)

    I did not understand, which effect this insertion should have – but, however, – as far as I see – it causes no harm.

    Did anyone understood, for which purpose the above mentioned code is?

    10th:

    I inserted as well:

    //hide the user role select field in edit-screen to prevent changes after registration
    add_filter("xprofile_group_fields","bpdev_filter_profile_fields_by_usertype",10,2);
    function bpdev_filter_profile_fields_by_usertype($fields,$group_id){
    
    //only disable these fields on edit page
    if(!bp_is_profile_edit())
    return $fields;
    //please change it with the name of fields you don't want to allow editing
    $field_to_remove=array("User Role");
    $count=count($fields);
    $flds=array();
    for($i=0;$i<$count;$i++){
    if(in_array($fields[$i]->name,$field_to_remove))
    unset($fields[$i]);
    else
    $flds[]=$fields[$i];//doh, I did not remember a way to reset the index, so creating a new array
    }
    return $flds;
    }

    into my bp-costum.php – again above the line ?>.

    It does not work:

    — threre the user role is still changeable:

    http://kampfsportlerinnenneuwied.1a-spielwiese.de/wp-content/uploads/sites/2/2014/09/user_role_still_changeble.jpg

    http://1a-spielwiese.de/members/kampfsportlerinnenneuwied/profile/edit/group/1 causes an redirection error. – The redirection error disappears, when I’m not logged in as kampfsportlerinnenneuwied, rather as superadmin.

    #201146
    Hugo Ashmore
    Participant

    Good point – doesn’t exist, MS is a law unto it’s self.

    You may need to write a function hooked to the registration process that changes the user role then.

    #201140
    1a-spielwiese
    Participant

    En passant: Is there any way for truly renaming the user roles from ‘contributor’ to ‘team’ and from ‘subscriber’ to ‘fan’, sothat I could keep the ‘Label’ simple (i.e.: without explaining: ‘Choose as Team: Contributor; and as Fan: Subscriber’)?

    Whether renaming, I still don’t know. But with ‘Capability Manager Enhanced’-plugin I could create entirely new user roles ‘team’ and ‘fan’ – and with ‘WP Roles at Registration’-plugin i could place them on the registration page:

    http://1a-spielwiese.de/wp-content/uploads/2014/09/Reg_Form_with_User_Roles.jpg

    But a problem remains: How can I make ‘Subscriber’ not being the standard user role anymore?

    #201130
    ivanguinea
    Participant

    Sorry:

    This is the list of my plugins:
    BackWPup
    Better WordPress Minify
    Breadcrumb NavXT
    Buddypress
    BuddyPress Registration Groups
    Formulario de Contacto 7
    Cookie Law Info
    Gears
    Hide Admin Bar From Non-admins
    Hide User Profile Fields
    LĂ­mitador de intentos de login
    Nav Menu Images
    Paid Memberships Pro
    PMPro Check Levels
    PMPro Customizations
    PMPro Email Templates
    PMPro Register Helper
    Regenerate Thumbnails
    Remove Dashboard Access
    Revolution Slider
    Simple Social Icons
    Editor de Roles
    WordPress SEO
    WP-Optimize
    WPBakery Visual Composer
    WP Google Fonts
    WP Smush.it
    WP Super Cache
    WP User Frontend Pro

    My theme is Klein (http://klein.dunhakdis.me/)

Viewing 25 results - 2,551 through 2,575 (of 7,642 total)
Skip to toolbar