Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'hide xprofile fields'

Viewing 25 results - 1 through 25 (of 93 total)
  • Author
    Search Results
  • #335662
    wpuser
    Participant

    Hi there,

    I had the issue with posting a reply yesterday too. Weird.
    That is why I split my message in 2 and than I could post it.

    I was able to read your share txt and the next replies and also view that images.

    Anyway… I am willing (if you are willing to put the time in it) to give you access to my staging site, but I rather not post the link in public, to avoid traffic from Google and such to that staging website. But there does not seem to be a way to share the link with you in private. Do you have any suggestions?

    To further explain my situation: I did not make any customizations to my buddypress or xprofile plugin that have anything to do with the profile fields. From the clean install, the “Name” field is already there from the start, when installing the buddypress plugin.

    I am not adding users via the admin section, I am letting them signup via the website register form. So following this process, the situation is as described before, where the “Name” will be filled in by the user as part of the registration process. The Name field is mandatory, set by Buddypress, which I can not influence nor rename.

    I did nothing to influence the Name field, other than translating it like I explained before.
    The Name is operating as a seperate field, that does not seem to link to username by default. And that is also not what I want. Because it would lead to the username being shown twice on a profile page, which is ridicilous of course. Since you can not block or hide the Name field, it will be there. Also, the Name field is always on the register form, and the field is mandatory (which you cannot change), so people CAN and probably will fill in something different than their username. Most likely their first name. Which is what happened on my site anyway, people fill in their regular first name. Only a handfull will choose like a second username/nickname for the field value. Anyway, in 99% process of the time, the Name field is populated with a different value than the username as a result of the website registration process (which is not changed, it is by default like that, since installing buddypress).

    I use the BuddyX theme. But the issue is not related to the theme, because using a default WordPress theme (like twenty two or so), will have the same result.

    So, it poses as a problem, if the usernames show up on the userlist, but the sorting will go on the “Name” field, which is not identical to the username. This will lead to a really undesired situation, where the sorting does not seem to work properly on the frontend, because “invisible” the userlist is sorted on the Name field.

    And also, this is new. Before, this was not the case. It did NOT sort on the “Name” field. And I’m oblivious why it does now, what is the intent by changing this.

    So, to address the situation, and to avoid having duplicate usernames on the profile page, I would rather stick with people using the Name field as their first name or something like that.

    I would like to sort on display name. Is there a way to do that? Do you have a suggestion?

    lbnn
    Participant

    Hello,

    I modified the profile-loop.php file some time ago to hide profile fields that are empty but my code doesn’t work anymore, has any change been done to the code some updates ago ?

    Here is what I modified :

    <h2 class="screen-heading view-profile-screen"><?php esc_html_e( 'View Profile', 'buddypress' ); ?></h2>
    
    <?php bp_nouveau_xprofile_hook( 'before', 'loop_content' ); ?>
    
    <?php if ( bp_has_profile('hide_empty_fields=0') ) : ?>
    
    	<?php
    	while ( bp_profile_groups() ) :
    		bp_the_profile_group();
    	?>
    
    		<?php if ( bp_profile_group_has_fields() ) : ?>
    
    			<?php bp_nouveau_xprofile_hook( 'before', 'field_content' ); ?>
    
    			<div class="bp-widget <?php bp_the_profile_group_slug(); ?>">
    
    				<h3 class="screen-heading profile-group-title">
    					<?php bp_the_profile_group_name(); ?>
    				</h3>
    
    				<table class="profile-fields bp-tables-user">
    
    					<?php
    					while ( bp_profile_fields() ) :
    						bp_the_profile_field('hide_empty_fields=0');
    					?>
    
    						<?php if ( bp_field_has_data() ) : ?>
    
    							<tr<?php bp_field_css_class(); ?>>
    
    								<td class="label"><?php bp_the_profile_field_name(); ?></td>
    
    								<td class="data"><?php bp_the_profile_field_value(); ?></td>
    
    							</tr>
    							
    						<?php elseif ( !bp_field_has_data() ) : ?>
    						
    							<tr<?php bp_field_css_class(); ?>>
    
    								<td class="label"><?php bp_the_profile_field_name(); ?></td>
    
    								<td class="data"><?php bp_the_profile_field_value(); ?></td>
    
    							</tr>
    							
    						<?php endif; ?>
    
    						<?php bp_nouveau_xprofile_hook( '', 'field_item' ); ?>
    
    					<?php endwhile; ?>
    
    				</table>
    			</div>
    
    			<?php bp_nouveau_xprofile_hook( 'after', 'field_content' ); ?>
    
    		<?php endif; ?>
    
    	<?php endwhile; ?>
    
    	<?php bp_nouveau_xprofile_hook( '', 'field_buttons' ); ?>
    
    <?php endif; ?>
    
    <?php
    bp_nouveau_xprofile_hook( 'after', 'loop_content' );
    

    Can someone help me to hode those fields again please šŸ™‚

    petertucker
    Participant

    Here is the solution for anyone who is going to see this post in the future.

    1. Install the username change plugin:
    https://buddydev.com/plugins/bp-username-changer/
    2. Add to the plugins code (bp-change-username.php) on line 163;

    
    xprofile_set_field_data(1, $user_id,  $new_user_name);
    

    3. In your theme function.php file add the follow code to hide XProfile editing:

    
    function bpfr_hide_profile_field_group( $retval ) {
            if ( bp_is_active( 'xprofile' ) ) :     
    
            // hide profile group/field to all except admin 
            if ( !is_super_admin() ) {
                    //exlude fields, separated by comma
                    $retval['exclude_fields'] = '1';  
                    //exlude groups, separated by comma
                    //$retval['exclude_groups'] = '1';
            } 
            return $retval;         
    
            endif;
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );
    

    I hope this helps anyone who finds it.

    #302438
    msteimann
    Participant

    Thanks for your quick reply, Venutius!

    I have tried the WP 2015 Theme and got the same results. So I switched back to KLEO and noticed, that the xProfile fields do change to the desired visibility settings, AFTER the user clicks the SAVE SETTINGS button. So I guess I was confused by the fact that BEFORE you hit the save button there is a misleading visual feedback (the visibility term does not alter to the according setting the user has just changed it to, it still displays the same value as before).

    Could this be changed in the next release?

    My first problem still remains: the ā€žchange display name visibility optionā€œ is displayed beneath the name field on the user Registration page. This doesn’t make sense, if the name’s visibility throughout BuddyPress network is mandatory. How can I get rid of this line? Does this line and it’s user changeable visibility options really not appear on a default install?

    In the WP Dashboard I cannot change the options for the primary Name field. Only the fields under the details tab can be altered by admin and set to be visibility-changeable by the user. (Hope you understand what I try to say šŸ˜‰

    Regards,
    Martin

    Hide visibility option on registration page?

    #302171
    sedmikraska
    Participant

    I want all profile fields to be visible on my site. So I want to remove the subnav Settings > Profile Visibility.

    I have added below command into bp-custom.php but it does not work.

    function bpfr_hide_visibility_tab() {
    if( bp_is_active( ‘xprofile’ ) )

    bp_core_remove_subnav_item( ‘settings’, ‘profile’ );

    }
    add_action( ‘bp_ready’, ‘bpfr_hide_visibility_tab’ );

    Something has changed probably because the conversation I found about this issue is two years old.

    Could you please let me know updated command that I have to use ?

    WordPress: 5.0.3–sk_SK
    BuddyPress: 4.1.0
    mamatwist.com

    Thank you,
    Dana

    olandir
    Participant

    I have a corporate Intranet running on WordPress 4.9.8 and BuddyPress 3.1.0

    I have specific xprofile fields that I’d like only editable to people who have the “Edit Users” capability.

    I’ve seen snippets of code here or there that almost do what I’m looking for but everything I’ve found is old and out of date.

    Could someone help me with this.

    Basically I need the PHP equivalent of

    If we’re on the edit BuddyPress profile page AND user does not have the “edit users” capability then hide profile fields with X id(s).

    I’d also be happy with specifying a role instead of capability as long as I can specify multiple role ids.

    Thank you in advance.

    lz430
    Participant

    Hey everyone,
    I have a membership site. It’s running Woocommerce, WP 4.9.6 and Buddypress 3.0.0. My BuddyPress status is below.

    I’m having a problem when someone is choosing a any kind of membership(I only have free and 1 paid at the moment). When they get to the billing screen they can either use Facebook or Google to login and fill in the details.

    Once they do that, Buddypress redirects them to their wall. I want them to be able to continue the checkout process. I’ve tried so many things, but can’t override it.

    Please help!

    
    ### WordPress Environment ###
    
    Home URL: http://www.specialtactics.global
    Site URL: http://www.specialtactics.global
    WC Version: 3.4.1
    Log Directory Writable: āœ”
    WP Version: 4.9.6
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    WP Cron: āœ”
    Language: en_US
    External object cache: –
    
    ### Server Environment ###
    
    Server Info: Apache
    PHP Version: 7.1.16 - We recommend using PHP version 7.2 or above for greater performance and security. How to update your PHP version
    PHP Post Max Size: 128 MB
    PHP Time Limit: 3000
    PHP Max Input Vars: 1000
    cURL Version: 7.54.0
    OpenSSL/1.0.2k
    
    SUHOSIN Installed: –
    MySQL Version: 5.6.39-cll-lve
    Max Upload Size: 128 MB
    Default Timezone is UTC: āœ”
    fsockopen/cURL: āœ”
    SoapClient: āœ”
    DOMDocument: āœ”
    GZip: āœ”
    Multibyte String: āœ”
    Remote Post: āœ”
    Remote Get: āœ”
    
    ### Database ###
    
    WC Database Version: 3.4.1
    WC Database Prefix: wp_
    MaxMind GeoIP Database: āœ”
    Total Database Size: 11.24MB
    Database Data Size: 10.10MB
    Database Index Size: 1.14MB
    wp_woocommerce_sessions: Data: 0.04MB + Index: 0.00MB
    wp_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_order_items: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_order_itemmeta: Data: 0.00MB + Index: 0.01MB
    wp_woocommerce_tax_rates: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB
    wp_woocommerce_log: Data: 0.00MB + Index: 0.00MB
    ts_redirects: Data: 0.00MB + Index: 0.00MB
    wp_achievements: Data: 0.02MB + Index: 0.01MB
    wp_bp_activity: Data: 0.01MB + Index: 0.01MB
    wp_bp_activity_meta: Data: 0.00MB + Index: 0.01MB
    wp_bp_friends: Data: 0.00MB + Index: 0.00MB
    wp_bp_groups: Data: 0.00MB + Index: 0.00MB
    wp_bp_groups_groupmeta: Data: 0.00MB + Index: 0.00MB
    wp_bp_groups_members: Data: 0.00MB + Index: 0.00MB
    wp_bp_links: Data: 0.00MB + Index: 0.00MB
    wp_bp_links_categories: Data: 0.00MB + Index: 0.00MB
    wp_bp_links_linkmeta: Data: 0.00MB + Index: 0.00MB
    wp_bp_links_votes: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_drafts: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_labels: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_label_message: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_messages: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_meta: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_notices: Data: 0.00MB + Index: 0.00MB
    wp_bp_messages_recipients: Data: 0.00MB + Index: 0.00MB
    wp_bp_notifications: Data: 0.00MB + Index: 0.00MB
    wp_bp_notifications_meta: Data: 0.00MB + Index: 0.00MB
    wp_bp_user_blogs: Data: 0.00MB + Index: 0.00MB
    wp_bp_user_blogs_blogmeta: Data: 0.00MB + Index: 0.01MB
    wp_bp_xprofile_data: Data: 0.00MB + Index: 0.00MB
    wp_bp_xprofile_fields: Data: 0.03MB + Index: 0.05MB
    wp_bp_xprofile_groups: Data: 0.00MB + Index: 0.00MB
    wp_bp_xprofile_meta: Data: 0.01MB + Index: 0.02MB
    wp_buddyboss_media: Data: 0.00MB + Index: 0.00MB
    wp_buddyboss_media_albums: Data: 0.00MB + Index: 0.00MB
    wp_commentmeta: Data: 0.00MB + Index: 0.01MB
    wp_comments: Data: 0.01MB + Index: 0.01MB
    wp_gde_profiles: Data: 0.00MB + Index: 0.00MB
    wp_gde_secure: Data: 0.00MB + Index: 0.00MB
    wp_learndash_user_activity: Data: 0.01MB + Index: 0.03MB
    wp_learndash_user_activity_meta: Data: 0.04MB + Index: 0.03MB
    wp_links: Data: 0.00MB + Index: 0.00MB
    wp_options: Data: 2.97MB + Index: 0.09MB
    wp_pmpro_discount_codes: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_discount_codes_levels: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_discount_codes_uses: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_memberships_categories: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_memberships_pages: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_memberships_users: Data: 0.00MB + Index: 0.01MB
    wp_pmpro_membership_levelmeta: Data: 0.00MB + Index: 0.00MB
    wp_pmpro_membership_levels: Data: 0.00MB + Index: 0.01MB
    wp_pmpro_membership_orders: Data: 0.00MB + Index: 0.02MB
    wp_pmxi_files: Data: 0.00MB + Index: 0.00MB
    wp_pmxi_history: Data: 0.00MB + Index: 0.00MB
    wp_pmxi_imports: Data: 0.00MB + Index: 0.00MB
    wp_pmxi_posts: Data: 0.00MB + Index: 0.00MB
    wp_pmxi_templates: Data: 0.00MB + Index: 0.00MB
    wp_postmeta: Data: 0.83MB + Index: 0.21MB
    wp_posts: Data: 2.47MB + Index: 0.17MB
    wp_pp_login_builder: Data: 0.01MB + Index: 0.00MB
    wp_pp_password_reset_builder: Data: 0.01MB + Index: 0.00MB
    wp_pp_registration_builder: Data: 0.01MB + Index: 0.00MB
    wp_revslider_css: Data: 0.09MB + Index: 0.00MB
    wp_revslider_layer_animations: Data: 0.00MB + Index: 0.00MB
    wp_revslider_navigations: Data: 0.00MB + Index: 0.00MB
    wp_revslider_sliders: Data: 0.02MB + Index: 0.00MB
    wp_revslider_slides: Data: 0.18MB + Index: 0.00MB
    wp_revslider_static_slides: Data: 0.00MB + Index: 0.00MB
    wp_signups: Data: 0.00MB + Index: 0.00MB
    wp_social_users: Data: 0.00MB + Index: 0.00MB
    wp_termmeta: Data: 0.00MB + Index: 0.01MB
    wp_terms: Data: 0.00MB + Index: 0.01MB
    wp_term_relationships: Data: 0.00MB + Index: 0.01MB
    wp_term_taxonomy: Data: 0.00MB + Index: 0.01MB
    wp_usermeta: Data: 0.05MB + Index: 0.04MB
    wp_users: Data: 0.00MB + Index: 0.01MB
    wp_waiting: Data: 0.00MB + Index: 0.00MB
    wp_wc_download_log: Data: 0.00MB + Index: 0.00MB
    wp_wc_webhooks: Data: 0.00MB + Index: 0.00MB
    wp_wfBadLeechers: Data: 0.00MB + Index: 0.00MB
    wp_wfBlockedCommentLog: Data: 0.00MB + Index: 0.00MB
    wp_wfBlockedIPLog: Data: 0.00MB + Index: 0.00MB
    wp_wfBlocks7: Data: 0.00MB + Index: 0.00MB
    wp_wfConfig: Data: 0.36MB + Index: 0.01MB
    wp_wfCrawlers: Data: 0.00MB + Index: 0.00MB
    wp_wfFileChanges: Data: 0.00MB + Index: 0.00MB
    wp_wfFileMods: Data: 0.48MB + Index: 0.11MB
    wp_wfHits: Data: 0.14MB + Index: 0.03MB
    wp_wfHoover: Data: 0.00MB + Index: 0.00MB
    wp_wfIssues: Data: 0.00MB + Index: 0.00MB
    wp_wfKnownFileList: Data: 0.97MB + Index: 0.12MB
    wp_wfLeechers: Data: 0.00MB + Index: 0.01MB
    wp_wfLiveTrafficHuman: Data: 0.00MB + Index: 0.00MB
    wp_wfLocs: Data: 0.00MB + Index: 0.00MB
    wp_wfLogins: Data: 0.01MB + Index: 0.00MB
    wp_wfNet404s: Data: 0.00MB + Index: 0.00MB
    wp_wfNotifications: Data: 0.00MB + Index: 0.00MB
    wp_wfPendingIssues: Data: 0.00MB + Index: 0.00MB
    wp_wfReverseCache: Data: 0.00MB + Index: 0.00MB
    wp_wfScanners: Data: 0.00MB + Index: 0.00MB
    wp_wfSNIPCache: Data: 0.00MB + Index: 0.00MB
    wp_wfStatus: Data: 0.06MB + Index: 0.03MB
    wp_wfVulnScanners: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_category: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_form: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_lock: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_master: Data: 0.02MB + Index: 0.00MB
    wp_wp_pro_quiz_prerequisite: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_question: Data: 1.24MB + Index: 0.03MB
    wp_wp_pro_quiz_statistic: Data: 0.01MB + Index: 0.00MB
    wp_wp_pro_quiz_statistic_ref: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_template: Data: 0.00MB + Index: 0.00MB
    wp_wp_pro_quiz_toplist: Data: 0.00MB + Index: 0.00MB
    wp_wsluserscontacts: Data: 0.00MB + Index: 0.00MB
    wp_wslusersprofiles: Data: 0.00MB + Index: 0.00MB
    
    ### Post Type Counts ###
    
    attachment: 121
    bmt-member-type: 4
    bp-email: 32
    cdfc: 1
    condition_group: 1
    custom_css: 1
    customize_changeset: 9
    forum: 1
    jetpack_migration: 2
    mc4wp-form: 1
    nav_menu_item: 33
    page: 39
    post: 24
    product: 12
    revision: 1003
    scheduled-action: 16
    sfwd-certificates: 1
    sfwd-courses: 7
    sfwd-lessons: 36
    sfwd-quiz: 38
    sfwd-topic: 147
    shop_order: 7
    shop_subscription: 5
    sidebar: 1
    sp_wps_shortcodes: 1
    topic: 4
    wc_membership_plan: 6
    wcps: 1
    woocarousel: 1
    wpachievements: 3
    wpcf7_contact_form: 1
    wpe_product_carousel: 1
    yith_wcps_type: 1
    
    ### Security ###
    
    Secure connection (HTTPS): āŒ
    					Your store is not using HTTPS. Learn more about HTTPS and SSL Certificates.
    Hide errors from visitors: āœ”
    
    ### Active Plugins (50) ###
    
    Addons for WPBakery Page Builder: by Livemesh – 1.9.1
    Akismet Anti-Spam: by Automattic – 4.0.7
    bbPress: by The bbPress Community – 2.5.14
    Better Search Replace: by Delicious Brains – 1.3.2
    Boss for LearnDash: by BuddyBoss – 1.3.0
    BP Redirect To Profile: by Brajesh Singh – 1.2.2
    BuddyBoss Inbox: by BuddyBoss – 1.1.3
    BuddyBoss Media: by BuddyBoss – 3.2.4
    BuddyBoss One Click Installer: by BuddyBoss – 1.0.6
    BuddyBoss Wall: by BuddyBoss – 1.3.3
    BuddyPress for LearnDash: by BuddyBoss – 1.2.4
    BuddyPress Member Types: by BuddyBoss – 1.1.2
    BuddyPress: by The BuddyPress Community – 3.0.0
    Contact Form 7: by Takayuki Miyoshi – 5.0.2
    Force HTTPS: by LittleBizzy – 1.0.6
    Google Doc Embedder: by Kevin Davis
    Dan Lester – 2.6.4
    
    Insert or Embed Articulate Content into WordPress Trial: by Brian Batt – 4.292
    WPBakery Page Builder: by Michael M - WPBakery.com – 5.4.7
    LearnDash Content Cloner: by WisdmLabs – 1.2.2
    LearnDash & bbPress Integration: by LearnDash – 2.0.2.1
    LearnDash Course Grid: by LearnDash – 1.4.1
    LearnDash ProPanel: by LearnDash – 2.1.3
    LearnDash WooCommerce Integration: by LearnDash – 1.4.0 – Not tested with the active version of WooCommerce
    Mega Addons For Visual Composer: by Nasir – 2.2
    Nextend Social Login: by Nextendweb – 3.0.10
    Nextend Social Login Pro Addon: by Nextendweb – 3.0.8
    WooCommerce Product Carousel Slider: by ADL Plugins – 3.0.2 – Not tested with the active version of WooCommerce
    Restrict Content: by Pippin Williamson – 2.2.3
    Slider Revolution: by ThemePunch – 5.4.7.3
    LearnDash LMS: by LearnDash – 2.5.8.2
    Simple Buddypress Profile Privacy: by Justin Hansen – 0.7.7
    String Locator: by Clorith – 2.3.0
    Theme My Login: by Jeff Farthing – 6.4.16
    Uncanny LearnDash Toolkit: by Uncanny Owl – 2.4.2
    Uncanny LearnDash Toolkit Pro: by Uncanny Owl – 2.3.1
    UpdraftPlus - Backup/Restore: by UpdraftPlus.Com
    DavidAnderson – 1.14.11
    
    Essential WPBakery Page Builder (formerly Visual Composer) Addons: by themebon – 1.9.1
    Waiting: by Plugin Builders – 0.4.5
    WC4BP -> WooCommerce BuddyPress Integration (Premium): by ThemeKraft – 3.1.4 – Not tested with the active version of WooCommerce
    WC4BP -> Subscriptions: by ThemeKraft – 1.1.0 – Not tested with the active version of WooCommerce
    WC4BP -> BuddyPress xProfile Checkout Manager: by ThemeKraft – 1.3.0 – Not tested with the active version of WooCommerce
    WooCommerce Colors: by WooThemes – 1.0.7 – Not tested with the active version of WooCommerce
    WooCommerce PayPal Express Checkout Gateway: by WooCommerce – 1.5.5
    WooCommerce Stripe Gateway: by WooCommerce – 4.1.6
    WooCommerce Memberships: by SkyVerge – 1.10.4
    WooCommerce Social Login: by SkyVerge – 2.5.2
    WooCommerce Subscriptions: by Prospress Inc. – 2.2.21
    WooCommerce: by Automattic – 3.4.1 – 3.4.2 is available
    WP File Manager: by mndpsingh287 – 2.7
    WP Rollback: by WordImpress – 1.5
    
    ### Settings ###
    
    API Enabled: āœ”
    Force SSL: āœ”
    Currency: USD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 2
    Taxonomies: Product Types: course (course)
    external (external)
    grouped (grouped)
    simple (simple)
    subscription (subscription)
    variable (variable)
    variable subscription (variable-subscription)
    
    Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
    exclude-from-search (exclude-from-search)
    featured (featured)
    outofstock (outofstock)
    rated-1 (rated-1)
    rated-2 (rated-2)
    rated-3 (rated-3)
    rated-4 (rated-4)
    rated-5 (rated-5)
    
    ### WC Pages ###
    
    Shop base: āŒ Page not set
    Cart: #562 - /cart/
    Checkout: #9648 - /woocommerce-checkout/
    My account: #9671 - /membership/
    Terms and conditions: āŒ Page not set
    
    ### Theme ###
    
    Name: Boss. Child Theme
    Version: 2.4.3
    Author URL: http://www.buddyboss.com
    Child Theme: āœ”
    Parent Theme Name: Boss.
    Parent Theme Version: 2.4.6
    Parent Theme Author URL: https://www.buddyboss.com
    WooCommerce Support: āœ”
    
    ### Templates ###
    
    Overrides: –
    
    ### subscriptions ###
    
    WCS_DEBUG: āœ”
    						No
    Subscriptions Mode: āœ”
    						Live
    Subscriptions Template Theme Overrides: –
    Report Cache Enabled: āœ”
    						Yes
    Cache Update Failures: āœ”
    						0 failure
    
    bassibabes1
    Participant

    I’ve seen that this problem crops up a lot, but I can’t seem to find a solution that works…

    I have Membership Pro 2 and BuddyPress installed. I’m using the BuddyPress registration form with extra profile fields. Currently, the registration form asks for the Username and Name (display name in BP terms). Obviously, this is really confusing for new members when they’re registering so I need to remove one of these. I’ve tested it out and the WP Username is the one that seems to be used throughout the site, so it would be good just to hide/remove the BP Name. I can hide the field with CSS, but then there is an error and the form won’t submit due to the missing field.

    Do I just need to find the code to allow the form to be submitted without this required field?

    I’ve seen people use the two plugins:

    BuddyPress Usernames Only

    BP XProfile WordPress User Sync

    But I can’t see how these can work with this particular issue?

    Any help is appreciated.

    #267803
    artempr
    Participant

    Hi. If it still an issue , I d recommend you to look at bp-xprofile-settings.php

    function bp_xprofile_get_settings_fields( $args = '' ) {
      //if u have ome custom user roles  you can simply filter here which groups to hide  
        if(!current_user_can("owner")){
            $query='5,6,4';
        }else{
            $query='1,3,4,5';
        }
    	// Parse the possible arguments.
    	$r = bp_parse_args( $args, array(
    		'user_id'                => bp_displayed_user_id(),
    		'profile_group_id'       => false,
    		'hide_empty_groups'      => false,
    		'hide_empty_fields'      => false,
    		'fetch_fields'           => true,
    		'fetch_field_data'       => false,
    		'fetch_visibility_level' => true,
    		'exclude_groups'         => $query,
    		'exclude_fields'         => false
    	), 'xprofile_get_settings_fields' );
    
    	return bp_has_profile( $r );
    }
    #263397
    john.horning
    Participant

    Thanks for the quick response, but doesn’t seem to be working for me. I created the template overload of profile-loop.php and stored it in wp-content/themes/buddyboss-child/buddypress/bp-templates/bp-legacy/buddypress/members/single/profile. I’ve pasted the entire file below after modification.

    I can’t find it now, but there was a thread somewhere that indicated that the following line needed to be changed in bp-xprofile-template.php so was wondering what you thought of that.
    $hide_empty_fields_default = ( ! is_network_admin() && ! is_admin() && ! bp_is_user_profile_edit() && ! bp_is_register_page() );

    Anyway, here’s my profile-loop.php:
    `

    #260277
    danbp
    Participant

    It relate to this filter bp_get_profile_field_data

    This example will hide tabs and fields to all except admin

    function bpfr_hide_profile_field_group( $retval ) {
    	if ( bp_is_active( 'xprofile' ) ) :	
    	
    	// hide profile group/field to all except admin	
    	if ( !is_super_admin() ) {		
    		//exlude fields, separated by comma
    		$retval['exclude_fields'] = '1';  
    		//exlude groups, separated by comma
    		$retval['exclude_groups'] = '3'; 			
    	} 
    	return $retval;		
    	
    	endif;
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

    These tricks hide the tab content, not the tab itself. (it seems that it doesn’t work for groups at the moment…i asked devs for information) Use CSS display:none to hide the tab or consider this plugin.

    Masoud
    Participant

    @shanebp
    hi. tnx for answer and patience. got 5 more minutes? šŸ™‚
    i read and worked on what you said. and if i want to be honest, i could’t do anything special unfortunately.
    now, i want to ask your opinion about this idea:
    i’ve come up with the idea of hiding that field. (not email field), how?
    with the use of if condition… (if it’s not empty show it. if it has data, hide it)!
    ——-
    i’ve created a custom-meta with this code in theme functions:

    add_action( 'personal_options_update', 'my_save_extra_profile_fields' );
    add_action( 'edit_user_profile_update', 'my_save_extra_profile_fields' );
    function my_save_extra_profile_fields( $user_id ) {
    if ( !current_user_can( 'edit_user', $user_id ) )
    	return false;
    /* Copy and paste this line for additional fields. */
    add_user_meta( $user_id, ā€˜person_relation’, 30318 );
    update_usermeta( absint( $user_id ), 'person_relation', wp_kses_post( $_POST['person_relation'] ) );
    update_user_meta( $user_id, 'person_relation', $_POST['person_relation'] );
    }

    and used it in my buddypress signup form, to get data from users. ok?
    after what you said, i went to edit.php (copy to my theme buddypress folder…)
    and added these codes. but it seems that they do not recieve/send data at all.
    it looks like they are empty!! 😐
    after <?php at the start,
    i added :

    global $user, $user_id;
    $person_relation = get_the_author_meta( 'person_relation', $user->ID );
    $user_id = get_current_user_id();

    and in the <form> ,
    i added this piece of code (not working)
    then copied and changed the “save changes button”.
    so there is 2 buttons. one is for my-custom-meta, and the other is for buddypress form.
    buddypress edit page
    if user writes the name and click save. the box/button, all should gone. and i have to see the data in Users admin panel.
    but nothing is getting save… and i dont know where am i doing it wrong

    <?php if( $person_relation == '' ): ?>
    <tr>
    <th><label for="person_relation">Invitor's Name</label></th>
    <td>
    <input type="text" name="person_relation" id="person_relation" value="<?php update_usermeta( $user_id, 'person_relation', $_POST['person_relation'] ); ?>" class="regular-text" /><br />
    <span class="description">Please enter your invitor's name.</span>
    </td>
    </tr>
    <input type="hidden" id="userID" value="<?php echo $user_id ?>"/>
    <div class="submit">
    <input type="submit" name="profile-group-edit-submit" id="profile-group-edit-submit" value="<?php esc_attr_e( 'Save Name', 'buddypress' ); ?> " />
    </div>
    <input type="hidden" name="person_relation" id="person_relation" value="<?php update_usermeta( $user_id, 'person_relation', $_POST['person_relation'] ); ?>" />
    <?php add_action( 'personal_options_update', 'my_save_extra_profile_fields' ); ?>
    <?php add_action( 'edit_user_profile_update', 'my_save_extra_profile_fields' ); ?>
    <?php do_action( 'xprofile_profile_field_data_updated'); ?>
    <?php endif; ?>

    so sorry for long description. tnx for help.
    any suggestions do you have?

    #253525
    danbp
    Participant

    Perhaps this can help you to go further.

    For point 2, maybe this snippet can do the job. Give it a try ! Add it to bp-custom.php

    function custom_display_xprofile_fields() {
    
    // single field item
    if ( $data = bp_get_profile_field_data( 'field=Industry' ) ) : // change field name to yours
    	echo '<div class="industry">'. xprofile_get_field_data( 'Industry', bp_displayed_user_id() ) .'</div>';
    endif;
    }
    add_action( 'bp_after_profile_loop_content' , 'custom_display_xprofile_fields' );
    #249689
    calvin
    Participant

    After adding the fields you want using xprofile, go to your regi page. If you are using google chrome, right click on the multiline box and inspect

    you should find out the the id of the visual/text box something similar this ‘wp-field_664-editor-tools’ (yours should be a bit different cos field number is different)

    you should also find out the id of the mce panel using the same method

    After that you should be able to add the custom css to your theme stylesheet.
    Example (hiding the item using css):
    #wp-field_664-editor-tools {display:none;}

    You may need to double check on the edit profile page. if it still appears there, you can use the same method to hide it.
    Hope this helps.

    #246500
    danbp
    Participant

    Hi @ma3ry,

    unable to visit the indicated page due to redirection… BP’s xProfile text box contains are autolinked by default for the 5 first words.
    This is handy when you use a field called city for example. The city name is autolinked and let each user click on it to find other who may entered the same name.

    Of course, an about me box with a long description, which several autolinked words has less interrest. Fortunately, you can deactivate xprofile autolinking.
    Two options for this: all or selected.

    Here 3 snippets. The first can be used if you want to completely remove autolink from all field values.
    The second is a new filter to let you choose the field(s) you want to deactivate. This need two snippet. The first to rewrite a filter and the second to remove / replace the existing BP filter.

    Add the snippet to bp-custom.php.

    // remove any autolink from profile
    function remove_xprofile_links() {
    remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
    }
    add_action( 'bp_init', 'remove_xprofile_links' ); 
    
    // custom filter to selectively remove autolink
    function my_xprofile_filter_link_profile_data( $field_value, $field_type = 'textbox' ) {
    
        // Access the field you are going to display value.
        global $field;
    
        // In this array you write the ids (separated by comma) of the fields you want to hide the link.
        $excluded_field_ids = array(2);
    
        // If the id of this $field is in the array, we return the value only and not the link.
        if (in_array($field->id, $excluded_field_ids))
    	return $field_value;
    	
    	if ( 'datebox' == $field_type )
    	return $field_value;
    	
    	if ( !strpos( $field_value, ',' ) && ( count( explode( ' ', $field_value ) ) > 5 ) )
    	return $field_value;
    	
    	$values = explode( ',', $field_value );
    	
    	if ( !empty( $values ) ) {
    		foreach ( (array) $values as $value ) {
    			$value = trim( $value );
    			
    			// If the value is a URL, skip it and just make it clickable.
    			if ( preg_match( '@(https?://([-\w\.]+)+(:\d+)?(/([\w/_\.]*(\?\S+)?)?)?)@', $value ) ) {
    				$new_values[] = make_clickable( $value );
    				
    				// Is not clickable
    			} else {
    				
    				// More than 5 spaces
    				if ( count( explode( ' ', $value ) ) > 5 ) {
    					$new_values[] = $value;
    					
    					// Less than 5 spaces
    				} else {
    					$search_url   = add_query_arg( array( 's' => urlencode( $value ) ), bp_get_members_directory_permalink() );
    					$new_values[] = '<a href="' . $search_url . '" rel="nofollow">' . $value . '</a>';
    				}
    			}
    		}
    		
    		$values = implode( ', ', $new_values );
    	}
    	
    	return $values;
    }
    
    /**
     * We remove the buddypress filter and add our custom filter.
     */
    function remove_xprofile_links() {
        // Remove the old filter.
        remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
        // Add your custom filter.
        add_filter( 'bp_get_the_profile_field_value', 'my_xprofile_filter_link_profile_data', 9, 2);
    }
    add_action('bp_setup_globals', 'remove_xprofile_links');
    #238134
    danbp
    Participant

    hi @utahman1971,

    this is the default behave of extended profile fields. Also it’s very handy, as those links became searcheable keywords. This let users click and find other entered same words.

    That said, a bio is generally more personnal, so those links maybe less important…

    Here’s a snippet (bp 2.0.1 +) you can add to bp-custom.php. It let’s you selectively disable those automated linking from some fields and let some other in place.

    function my_xprofile_filter_link_profile_data( $field_value, $field_type = 'textbox' ) {
        // Access the field you are going to display value.
        global $field;
        // In this array you write the ids of the fields you want to hide the link.
        $excluded_field_ids = array(2,6,7);
        // If the id of this $field is in the array, we return the value only and not the link.
        if (in_array($field->id, $excluded_field_ids))
    	return $field_value;
    	
    	if ( 'datebox' == $field_type )
    	return $field_value;
    	
    	if ( !strpos( $field_value, ',' ) && ( count( explode( ' ', $field_value ) ) > 5 ) )
    	return $field_value;
    	
    	$values = explode( ',', $field_value );
    	
    	if ( !empty( $values ) ) {
    		foreach ( (array) $values as $value ) {
    			$value = trim( $value );
    			
    			// If the value is a URL, skip it and just make it clickable.
    			if ( preg_match( '@(https?://([-\w\.]+)+(:\d+)?(/([\w/_\.]*(\?\S+)?)?)?)@', $value ) ) {
    				$new_values[] = make_clickable( $value );
    				
    				// Is not clickable
    			} else {
    				
    				// More than 5 spaces
    				if ( count( explode( ' ', $value ) ) > 5 ) {
    					$new_values[] = $value;
    					
    					// Less than 5 spaces
    				} else {
    					$search_url   = add_query_arg( array( 's' => urlencode( $value ) ), bp_get_members_directory_permalink() );
    					$new_values[] = '<a href="' . $search_url . '" rel="nofollow">' . $value . '</a>';
    				}
    			}
    		}
    		
    		$values = implode( ', ', $new_values );
    	}
    	
    	return $values;
    }
    
    /**
     * We remove the buddypress filter and add our custom filter.
     */
    function remove_xprofile_links() {
        // Remove the old filter.
        remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
        // Add your custom filter.
        add_filter( 'bp_get_the_profile_field_value', 'my_xprofile_filter_link_profile_data', 9, 2);
    }
    add_action('bp_setup_globals', 'remove_xprofile_links');

    If you want to deactivate completely profile fied links, you can use this function:

    function bpfr_remove_xprofile_links() {
        remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
    }
    add_action('bp_setup_globals', 'bpfr_remove_xprofile_links'); 
    danbp
    Participant

    hi @mcpeanut,

    this snippet useable from BP 2.0.1 and above, can be added to bp-custom.php
    it will hide the field ID 1 which is the default Name field to all, except site admin.

    it will also avoid the user to edit that field. So if you use this, i recommand you tell them on register page that once they entered a name it they could change it later. You can than ask them $$$$ to do it. šŸ˜€

    function bpfr_hide_profile_field_group( $retval ) {
    	if ( bp_is_active( 'xprofile' ) ) :	
    	
    	// hide profile group/field to all except admin	
    	if ( !is_super_admin() ) {		
    		//exlude fields, separated by comma
    		$retval['exclude_fields'] = '1';  
    		//exlude field groups, separated by comma
    		$retval['exclude_groups'] = '1'; 			
    	} 
    	return $retval;		
    	
    	endif;
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

    More here:

    Using bp_parse_args() to filter BuddyPress template loops

    #230724
    danbp
    Participant

    Sorry to answer you with a big laught, it’s not html but php. šŸ˜€
    You should also find the time to read more attentively the forum, or search by keywords.
    in this case: hide xprofile fields

    https://buddypress.org/support/search/hide+xprofile+fields/

    You’re welcome. Glad you got it. šŸ˜‰

    #230718
    danbp
    Participant

    Hi @amic58, @tecca

    When BP is installed and xProfile is activated, the original WP profile settings are not accessible to user.

    The WP register process use only username, password and email and BuddyPress add by default a Name field as base for other extended profile fields.

    In short this means that username and name fields can contain a same information(a name, a pseudonym, a first or/and a last name). The plugin you mention is best for a WP install where user had choosen first/last name as output on post, comments, etc Once BP is activated, this became a little different.

    Now to the initial question.
    The CSS trick is a very inelegant solution as it lets everybody knowing how BP works to surround this invisibility. You’re also loosing any flexibility if you want to show some fields privately for example.

    You can do this properly with a little snippet, as explained here:

    Using bp_parse_args() to filter BuddyPress template loops

    Here’s an example which let you hide fields or fiels group to members, but not to site admin

    function bpfr_hide_profile_field_group( $retval ) {
    	if ( bp_is_active( 'xprofile' ) ) :	
    	
    	// hide profile group/field to all except admin	
    	if ( !is_super_admin() ) {		
    		//exlude fields, separated by comma
    		$retval['exclude_fields'] = '1';  
    		//exlude groups, separated by comma
    		$retval['exclude_groups'] = '1'; 			
    	} 
    	return $retval;		
    	
    	endif;
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

    Add it to bp-custom.php or your child-theme functions.php

    Of course you can also choose to show a field or group, but remove the possibility for the user to edit it later. Simply add more conditionnal to the function.

    Here another example:

    function bpfr_hide_profile_edit( $retval ) {	
    	// remove field from edit tab
    	if(  bp_is_user_profile_edit() ) {		
    		$retval['exclude_fields'] = '54'; // ID's separated by comma
    	}	
    	// allow field on register page
    	if ( bp_is_register_page() ) {
    		$retval['include_fields'] = '54'; // ID's separated by comma
    		}		
    	
    	// hide the field on profile view tab
    	if ( $data = bp_get_profile_field_data( 'field=54' ) ) : 
    		$retval['exclude_fields'] = '54'; // ID's separated by comma	
    	endif;	
    	
    	return $retval;	
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_edit' );

    Hope to be clear.

    #227729

    In reply to: Separate Business User

    Henry Wright
    Moderator

    Hi @navinachettri

    1. Have you searched the plugin directory?
    2. This can be done via hooks. It will need some custom code (not much, just a few lines).
    3. You could hide or show xProfile fields according to role. How exactly roles are created and managed will be dependent on point 1
    4. Again, to distinguish business users from ‘normal’ users, you’d use the roles created via the plugin you’re using from point 1. The jobs and adverts could each have their own custom post type
    5. This will need to be custom coded

    Hope that helps?

    1a-spielwiese
    Participant

    The problems are still unresolved:

    ++ Cfr. regarding problem A. (Making xProfile fields required only for members with a certain user role):

    https://wordpress.org/support/topic/making-bp-xprofile-fields-required-for-certain-user (posted today)

    ++ Hide theses xProfile fields for members with other user roles:

    https://wordpress.org/support/topic/bb-xprofiles-acl-does-not-work (posted one week ago)

    ++ Cfr. regarding problem D. (Making answers unchangeable):

    https://buddypress.org/support/topic/how-to-make-some-xprofile-field-to-uneditable/#post-206808 (posted two days ago).

    #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?)'

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

    #193476
    danbp
    Participant

    @jessicana,

    The field NAME in the field group BASE is required. This group is used for the registration page to work. As you already know, it’s also this group who allows you to show custom fields on the registration page.
    The NAME field in BuddyPress is intended to receive first and last name and replace the two original fields (first name, last name) coming with WordPress.

    That said, you can hide this field to users, but you can’t give them the choice to show/hide it.

    The above snippet will hide the field NAME to all visitors/members, but not to site admin and the concerned profile.

    function bpfr_make_name_members_only( $retval ) {	
    	//hold all of our info
    	global $bp;
    	
    	// is xprofile component active ?	
    	if ( bp_is_active( 'xprofile' ) )
    	
        // The user ID of the currently logged in user
        $current_user_id = (int) trim($bp->loggedin_user->id);
    	
        // The author that we are currently viewing
        $author_id  = (int) trim($bp->displayed_user->id);
    	
    	// user can see only his name && admin can see everyone 
    	if ($current_user_id !== $author_id && !current_user_can('delete_others_pages') ) {
    		$retval['exclude_fields'] = '1';	
    	}
    	return $retval;	
    }
    add_filter( 'bp_after_has_profile_parse_args', 'bpfr_make_name_members_only' );

    Add this to your child-theme functions.php or to bp-custom.php

    ChiefAlchemist
    Participant

    => re: “Note that you need to add the correct id(s) for exclude_fields.”

    Thanks shanebp. But is this the only way? I mean, I can’t do mucking with the code every time the client wants something new? Can I?

    => re: …/buddypress-xprofile-custom-fields-type/

    “Add new visibility setting “Nobody”. Hide the field to all members.”

    So this means, I presume that custom visibility is possible. Yes?

    That said, I want to use standard fields, but I want to create the list via code, and not have to do it manually. Not possible? Mind you, it could be cause I’m new to BP but I’m trying to where / how the profile definitions are stored. I presume it’s an array, or close. So I want to do that but with code.

    Thanks again

Viewing 25 results - 1 through 25 (of 93 total)
Skip to toolbar